Guest strangiato2112 Posted December 18, 2011 Share Posted December 18, 2011 Hi folks, I have been attempting to install Office 2010 Pro Plus (from Office 365) via a GPO Shutdown Script. I have been having multiple issues in the process with pieces not working as advertised. My script and my config.xml are provided below, as are my MSP file settings. Here are the issues that I have been having: [ ]Anything that I add in the OCT as an additional installation, does not install. I have tried intalling Lync via the .exe with the /Install /Silent switches. I have also tried installing Microsoft Online Services Sign-In Assistant via the .msi. I have tried them with both options - before and after the Office product is installed. It seems that if I include the MOSSIA msi before the Office install, then the entire install fails; not even Office 2010 installs. The log file shows error code 91, which doesn't seem to actually exist according to Microsoft online documentation. According to the OCT dialog, exe, cmd, bat, scr, and msi files are all supported, but when you browse for the install file, it will not recognize msi files. I had to type the full path to the msi. Yes, I double-, triple-, and quadruple-checked that the path was correct. [ ]The Office install will reboot whether I want it to or not. I have added SETUP_REBOOT=Never to both the config.xml and the msp file through the OCT. Neither method has any affect. I have named the msp file beginning with a "1" as recommended so that it is first in the sort order of the Updates folder. In the OCT documentation, it states that if you add any additional installations that need a reboot, any other additional installs that come after that in the list will not happen. It seems that the Office install itself needs to reboot and therefore negates anything set to install after it, including any office updates via msp files. I have added all of the msp files from SP1 to the Updates folder and through many attempts, they have yet to install. Here is my script: setlocal REM REM Environment customization begins here. Modify variables below. REM REM Get ProductName from the Office product's core Setup.xml file, and then add "office14." as a prefix. set ProductName=Office14.PROPLUSSUB REM Set DeployServer to a network-accessible location containing the Office source files. set DeployServer=\\server\install\Office365\install\ REM Set ConfigFile to the configuration file to be used for deployment (required) set ConfigFile=\\server\install\Office365\Install\ProPlusSub.WW\config.xml REM Set LogLocation to a central directory to collect log files. set LogLocation=\\server\install\Office365\Install\install_logs\ REM REM Deployment code begins here. Do not modify anything below this line. REM IF NOT "%ProgramFiles(x86)%"=="" (goto ARP64) else (goto ARP86) REM Operating system is X64. Check for 32 bit Office in emulated Wow6432 uninstall key :ARP64 reg query HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName% if NOT %errorlevel%==1 (goto End) REM Check for 32 and 64 bit versions of Office 2010 in regular uninstall key.(Office 64bit would also appear here on a 64bit OS) :ARP86 reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName% if %errorlevel%==1 (goto DeployOffice) else (goto End) REM If 1 returned, the product was not found. Run setup here. :DeployOffice start /wait %DeployServer%\setup.exe /config %ConfigFile% echo %date% %time% Setup ended with error code %errorlevel%. >> %LogLocation%\%computername%.txt REM If 0 or other was returned, the product was found or another error occurred. Do nothing. :End Endlocal Here is my config.xml: <Configuration Product="ProPlusSub"> <!-- <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> --> <!-- <Logging Type="standard" Path="\\server\install\Office365\Install\install_logs" Template="Microsoft Office Professional Plus Setup( ).txt" /> --> <!-- <LIS CACHEACTION="CacheOnly" /> --> <!-- <LIS SOURCELIST="\\server1\share\Office;\\server2\share\Office" /> --> <!-- <DistributionPoint Location="\\server\share\Office" /> --> <!-- <OptionState Id="OptionID" State="absent" Children="force" /> --> <!-- <Command Path="%windir%\system32\msiexec.exe" Args="/i \\server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" /> --> <!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> --> <!-- <USERNAME Value="" /> --> <!-- <COMPANYNAME Value="" /> --> <Setting Id="SETUP_REBOOT" Value="Never" /> <SetupUpdates CheckForSUpdates="Yes" SUpdateLocation="\\server\install\Office365\Install\Updates" /> </Configuration> In my msp setup customization file, I have set the following options: [ ]Organization name is set to my comapny name [ ]Use KMS Key (install is from Office 365, so there is no key needed) [ ]EULA is accepted [ ]Diplay Level is set to None. Completion message is on (and never seen), Supress modal is on. No cancel is off. [ ]Added installation: \\server\Install\Office365\Lync\i386\LyncSetup.exe /Install /Silent [ ]Set feature installation states set to install all to Run all from MY Computer [ ]Configure shortcuts is set to add shortcuts to Word, Excel, and Oultook to the desktop. I am extremely frustrated with this stuff and at this point, I may just install the MOSSIA msi via a Software installation in the GPO, and add a startup script to install Lync if Office 2010 exists on the machine. Any insights into what I am doing wrong would be greatly appreciated. Thanks all! -tim Continue reading... Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.