Thanks Overworked, I used your script as a starting point for Office365 setup and ended up with this:
setlocal
REM *********************************************************************
REM Environment customization begins here. Modify variables below.
REM *********************************************************************
REM Get ProductName
set "ProductName=O365ProPlusRetail - en-us"
REM Set DeployServer to a network-accessible location containing the Office source files.
set DeployServer=\\*******\*****\*****\office15
REM Set ConfigFile to the configuration file to be used for deployment (required)
set ConfigFile=\\*******\*****\*****\office15\installconfiguration.xml
REM Set LogLocation to a central directory to collect log files.
set LogLocation=\\*******\*****\*****\office15\InstallLogFiles
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 2013 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
echo %date% %time% Deployment triggered on %computername%.>> %LogLocation%\%computername%.txt
start /wait %DeployServer%\setup.exe /configure %ConfigFile%
echo %date% %time% Setup executed and 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
Some observations from my testing and hair pulling:
1. The registry key created has spaces in the name (thanks MS), so the quotes are needed to get the check to work
2. The Office 365 setup switch is /configure - not /config (ditto)
3. It really does deploy silently. The first time I did it I thought nothing had happened and went away for 20 mins, only to find it in the start menu of the test system when I got back.
4. This will install alongside Office 2010 painlessly. Unfortunately it doesn't uninstall nicely (the uninstall message even recommends running Office 2010 repair!). You will have to repair 2010 if you uninstall 365/2013, and you may need to reactivate the 2010 installation as well.
5. Installation was approx 12 mins on a Win 7 test laptop.
It would have been nice if MS had put a suitable script in with the deployment instructions!
Regards all.
