O2k7 - Default behaviour for config.xml
I've been looking into pushing Office 2007 to a select group of users via Group Policy. (Who's godforsaken idea was it to relegate GP deployment?!)
I am stumbling when it comes to the config.xml file
Extract:
My question is: to do a complete install of all features should I set the State=Local for all components? What is the default behaviour if the component (and it's associated state) is omitted from the config.xml file?
I am stumbling when it comes to the config.xml file
Extract:
...
<OptionState Id="Access_PIA "State=Local" Children="force" />
<OptionState Id="AccessBarcodeControl "State=Local" Children="force" />
<OptionState Id="AccessHelpFiles "State=Local" Children="force" />
<OptionState Id="AccessWizards "State=Local" Children="force" />
<OptionState Id="CalendarControl "State=Local" Children="force" />
<OptionState Id="DeveloperWizards "State=Local" Children="force" />
<OptionState Id="AccessTemplatesIntl "State=Local" Children="force" />
<OptionState Id="EXCELFiles "State=Local" Children="force" />
<OptionState Id="Excel_PIA "State=Local" Children="force" />
<OptionState Id="ExcelAddinFiles "State=Local" Children="force" />
<OptionState Id="ExcelHelpFiles "State=Local" Children="force" />
<OptionState Id="ExcelSampleFiles "State=Local" Children="force" />
...
My question is: to do a complete install of all features should I set the State=Local for all components? What is the default behaviour if the component (and it's associated state) is omitted from the config.xml file?
0 Comments
[ + ] Show comments
Answers (0)
Please log in to answer
Be the first to answer this question
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.