Office 2010 deployed, bootup shows error about config.xml
Hi
I read the sticky and will be attending the webex session at the end of the month for Office 2010 but in the meantime could anyone offer any advice on the following please?
I have used the OCT to create an MSP file and stuck it in updates. I created a package in Kaseya to simply run the command
And it all installed fine. The version is Office Professional Plus 2010. Now after a reboot the following message is displayed:
Now the Enterprise.WW folder doesn't even exist - the ProPlus.WW folder does but the config.xml file is different to the one that would be generated by the OCT I imagine?
Any thoughts? Also, as an aside to this, if anyone knows how to stop the 'auto-update' prompt appearing on first run for users that would also be very much appreciated.
Thanks for your time.
Client: Windows XP SP3
Domain: 2008 Native
Deployment: Kaseya (latest)
Edit: If I run the setup.exe locally from the command line, it works fine. Just seems to be running from Kaseya it causes issues looking for the config .xml
I read the sticky and will be attending the webex session at the end of the month for Office 2010 but in the meantime could anyone offer any advice on the following please?
I have used the OCT to create an MSP file and stuck it in updates. I created a package in Kaseya to simply run the command
\\server\share\setup.exe (and it automatically used the MSP in the /updates folder)
And it all installed fine. The version is Office Professional Plus 2010. Now after a reboot the following message is displayed:
Cannot find the specified config.xml file. \\server\share\Enterprise.WW\config.xml
Now the Enterprise.WW folder doesn't even exist - the ProPlus.WW folder does but the config.xml file is different to the one that would be generated by the OCT I imagine?
Any thoughts? Also, as an aside to this, if anyone knows how to stop the 'auto-update' prompt appearing on first run for users that would also be very much appreciated.
Thanks for your time.
Client: Windows XP SP3
Domain: 2008 Native
Deployment: Kaseya (latest)
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
yannara
13 years ago
Try this:
setup.exe /adminfile "xxx.mps"
Just place xxx.mps to the root of source directory, same location as setup.exe is.
setup.exe /adminfile "xxx.mps"
Just place xxx.mps to the root of source directory, same location as setup.exe is.
Posted by:
bennebiest
12 years ago
Create a (or edit the existing) Config.xml file, place it in the folder corresponding to the Office version you are deploying.
For example: Standard.WW for Office Standard, Enterprise.WW for Office Enterprise .. you have to use \ProPlus.WW according to your question.
Also disable the Opt-in Wizard with Office Customization Tool: Disable Opt-in Wizard on first run: Enable (to disable the Wizard)
Maybe this blog post can help: http://www.the-d-spot.org/wordpress/2010/09/09/office-2010-deployment/
For example: Standard.WW for Office Standard, Enterprise.WW for Office Enterprise .. you have to use \ProPlus.WW according to your question.
Also disable the Opt-in Wizard with Office Customization Tool: Disable Opt-in Wizard on first run: Enable (to disable the Wizard)
Maybe this blog post can help: http://www.the-d-spot.org/wordpress/2010/09/09/office-2010-deployment/
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
