Wondering if someone out there can help with a question regarding Office Pro upgrades.
I've created an admin image with a transform to install Office Pro 2003 or upgrade from Office XP Pro to Pro 2003.
In the transform I've specified that the Access feature not be installed or available.

When I tested the install on a machine that doesn't have Office XP on it, it performs as expected.
It installs everything but Access. However, when I push it to a workstation that has Office XP Pro
installed with access features. It upgrades my access components.

Any idea on how to avoid this?
It's not suppose to upgrade Access, but it does.
Not sure if there's more features dependant which upgrades access no matter what, unless specified elsewhere.

*shrugs* Please help.


[&o] [>:] FPTHREE
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


this looks to me like the 'MigrateFeatureStates' bit is set in the row of the upgrade table, which detects OffXP.
Please read this: http://msdn2.microsoft.com/en-us/library/aa372379.aspx
Then use ORCA to change it.
Good luck.
Regards, Nick
Answered 02/26/2007 by: nheim
Tenth Degree Black Belt

Please log in to comment