T
theaussie05
I am in the process of deploying Windows XP. I am also deploying all apps via
GPO (if possible).
Office XP has been deployed to all my XP users with an MST that works
perfectly.
Windows 200 domain single site.
I still have about 40 XP users to go (out of 60 - so the bulk of them).
We currently use an alternative email program and Outlook was set to
Unavailable in the original MST file.
We are now looking at going to Outlook for compatibility reasons and I was
wondering.
Can I adjust the original MST file to deploy Outlook on the newer builds -
without affecting the existing Office XP users. ie Without altering the
Office XP package at all.
And then use the Custom Maintenance Wizard to fix the existing 20 users.
All the documentation (ORK and W2KRK) states that
"an MST file is only used during installation" which infers that I can
change the original MST for new installs and "you must use the Custom
Maintenance Wizard to alter existing Office installations". I've tried this
with other packages (admittedly the didn't have MST files) and the package
doesn't seem to change.
Another vexing question for me with software deployment via GPO is exactly
how it works! With upgrades, updates to packages. Does AD store the original
info somewhere and continue using that ie. The MST file or MSI info or does
AD point to the installation point etc.
Can someone point me to a detailed explanation of how the .. it all hangs
together. I'm no dunce - MCSE + 15 yrs IT experience, consulting and all so a
detailed explanation is not daunting at all.
Thanks
GPO (if possible).
Office XP has been deployed to all my XP users with an MST that works
perfectly.
Windows 200 domain single site.
I still have about 40 XP users to go (out of 60 - so the bulk of them).
We currently use an alternative email program and Outlook was set to
Unavailable in the original MST file.
We are now looking at going to Outlook for compatibility reasons and I was
wondering.
Can I adjust the original MST file to deploy Outlook on the newer builds -
without affecting the existing Office XP users. ie Without altering the
Office XP package at all.
And then use the Custom Maintenance Wizard to fix the existing 20 users.
All the documentation (ORK and W2KRK) states that
"an MST file is only used during installation" which infers that I can
change the original MST for new installs and "you must use the Custom
Maintenance Wizard to alter existing Office installations". I've tried this
with other packages (admittedly the didn't have MST files) and the package
doesn't seem to change.
Another vexing question for me with software deployment via GPO is exactly
how it works! With upgrades, updates to packages. Does AD store the original
info somewhere and continue using that ie. The MST file or MSI info or does
AD point to the installation point etc.
Can someone point me to a detailed explanation of how the .. it all hangs
together. I'm no dunce - MCSE + 15 yrs IT experience, consulting and all so a
detailed explanation is not daunting at all.
Thanks