B
Bob Buckland ?:-\)
Hi Gerry,
Short version is that the 'intelligent setup', if
left on its own will generally believe that when you
update from a prior version of Office (MST files only
apply to a first install of a product) that if you/users
have set things up they probably want to continue to work
the same way, so their settings, rather than the Office
defaults, or the ones you've set as 'new user' defaults
are migrated (carried forward).
If you use the 'do not migrate' choice for an individual
element or a tree branch, or use the settings value of
NOFEATURESTATEMIGRATION =1
for the transform you're telling the installer to replace
the user's current choices, features, settings with what
you're selecting as part of standardization in the upgrade.
Another case where you may see Add/Remove programs not matching
is if your ini file mentions a different MST.
=======
OK, I've looked into it in some detail.
It turns out that Add/Remove programs was correctly finding my transform (I
can see from the log file), but for some reason the feature list in the UI
was showing Office defaults instead of those set in the transform.
I created a new transform, and this time ticked the box "Do not migrate
previous installation State" on screen 7 of 24. I then chose to apply it to
the whole tree.
Reinstalling office on the client machine, and going into "Add/Remove
Programs", now correctly shows the feature list chosen in the transform.
I don't really understand "Do not migrate previous installation State", does
it mean from a previous version of Office or a previous install of THIS
version of office? The help file seems unhelpful.
Gerry Hickman>>
--
Let us know if this helped you,
Bob Buckland ?
MS Office System Products MVP
*Courtesy is not expensive and can pay big dividends*
For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx
Short version is that the 'intelligent setup', if
left on its own will generally believe that when you
update from a prior version of Office (MST files only
apply to a first install of a product) that if you/users
have set things up they probably want to continue to work
the same way, so their settings, rather than the Office
defaults, or the ones you've set as 'new user' defaults
are migrated (carried forward).
If you use the 'do not migrate' choice for an individual
element or a tree branch, or use the settings value of
NOFEATURESTATEMIGRATION =1
for the transform you're telling the installer to replace
the user's current choices, features, settings with what
you're selecting as part of standardization in the upgrade.
Another case where you may see Add/Remove programs not matching
is if your ini file mentions a different MST.
=======
OK, I've looked into it in some detail.
It turns out that Add/Remove programs was correctly finding my transform (I
can see from the log file), but for some reason the feature list in the UI
was showing Office defaults instead of those set in the transform.
I created a new transform, and this time ticked the box "Do not migrate
previous installation State" on screen 7 of 24. I then chose to apply it to
the whole tree.
Reinstalling office on the client machine, and going into "Add/Remove
Programs", now correctly shows the feature list chosen in the transform.
I don't really understand "Do not migrate previous installation State", does
it mean from a previous version of Office or a previous install of THIS
version of office? The help file seems unhelpful.
Gerry Hickman>>
--
Let us know if this helped you,
Bob Buckland ?
MS Office System Products MVP
*Courtesy is not expensive and can pay big dividends*
For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx