I have been trying to grasp why I cannot install Office 2010 using OCT process using a startup script for the computer side policy. The steps in the MS TechNet articles were followed to build the BAT file (This is confirmed working when a local administrator
account or domain administrator account is logged onto the computer and the .bat file is run).
When a domain user logs onto the system (No administration rights whatsoever) the installation will not start. The startup script is supposed to run as the system account but it does not run. Ever. I have tried this in both a production environment and
a freshly created domain with 4 test workstations both XP and Windows 7.
Run as a startup Script link:
http://technet.microsoft.com/en-US/library/cc754995.aspx
Microsoft BAT file:
http://technet.microsoft.com/en-us/library/ff602181(v=office.14).aspx
The OCT tool (setup.exe /admin) generates an MSP file and the .bat file makes reference to the setup.exe file in the folder that is shared out for the Office installation on a file server. I don't see an MSI download option anywhere and the documentation for this subject is quite difficult to follow for some reason.
I understand there are multiple MSI's to install Office for language packs etc but why isn't there a straight forward installation process documented to install Office 2010 to multiple computers? Why would Microsoft release a OCT tool if it cannot be used to deploy office through Group Policy?
I need to install office on 115 workstations at the rate of roughly 10 workstations at a time across a medium sized network. I would like to find an answer to meet the client needs.
I also posted in the scripting forums and they diverted me to the Group Policy forums. (Here is my post in the scripting forums)
http://social.technet.microsoft.com/Forums/scriptcenter/en-US/55673763-1776-4b4f-8a9b-e5cc4a35b03a/office-2010-will-not-deploy-with-startup-bat-file-msp-configuration-correctly#c04fe41c-447e-4e57-9116-d5dc7daf5a3a
I'm hoping I'm just doing something wrong and someone knows the answer to this. Certainly someone has installed Office 2010 using this OCT deployment configuration with a startup script? Even stripping down the scripts to a bare minimum do not work for me.
IE a bat file containing:
\\servername\share\office14\setup.exe /adminfile\\servername\share\Office2010.msp
Never executes for me either.