Microsoft Office 2016

[DSAGEY]

Hi,

 

I'm getting a bit confused with this whole no MSI business for Microsodft Office 2016.

 

I want to rule it out to all machines, but there is no MSI package with it - how do I go about doing this without having to do them manually.

 

Thanks

[sted]

only way is to script it theres been no msi for years

 

something like

 

if exist "c:\Program Files (x86)\Microsoft Office\Office16\WINWORD.EXE" goto end

\\server\share\office2016\setup.exe /s

 

:end

 

would need testing i cant remember the silent switch i do it as part of my mdt process so i want to see the screen

[sparkeh]

Hi,

 

I'm getting a bit confused with this whole no MSI business for Microsodft Office 2016.

 

I want to rule it out to all machines, but there is no MSI package with it - how do I go about doing this without having to do them manually.

 

Thanks

Which version are you using? Volume licencing? Click to run (ie Office 365 ProPlus)?

 

What tools are you using to roll it out? SCCM? Group Policy? Another tool?

 

There are many options with different workflows

[3s-gtech]

You create an install config XML file using the Customisation Tool (which is pretty good and clear). You then place this with your install files on a deployment share, and run a startup script which references the config and the installer setup.exe.

Example startup 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 "office16." as a prefix. 
set ProductName=Office16.PROPLUS

REM Set DeployServer to a network-accessible location containing the Office source files.
set DeployServer=\\server\share\install$\Office2016

REM Set ConfigFile to the configuration file to be used for deployment (required)
set ConfigFile=\\server\share\install$\Office2016\ProPlus.WW\config.xml

REM Set LogLocation to a central directory to collect log files.
set LogLocation=\\server\share\install$\Office2016\Office2013LogFiles

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 2016 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
REM Remove Office 2013 if installed
start /wait \\server\share\install$\office2013\setup.exe /uninstall ProPlus /config \\server\share\install$\office2013\ProPlus.WW\UninstallConfig.xml
REM Install Office 2016
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

[mavhc]

MS would like you to buy InTune or SCCM, but they do have scripts on their website to do it, very inefficient. Weird when it's easier to install LibreOffice on Windows than MS Office

 

https://github.com/OfficeDev/Office-IT-Pro-Deployment-Scripts/wiki

[DJ-1701]

Well, you have a couple of options above now... but what I find more shocking is this is posted in the Windows Server 2008 Thread. Please tell me you are moving away from that before the 14th of January 2020.

[DSAGEY]

Well, you have a couple of options above now... but what I find more shocking is this is posted in the Windows Server 2008 Thread. Please tell me you are moving away from that before the 14th of January 2020.

 

We are planning to move to a newer version, it's just the budget side of things that needs sorting. It doesn't look like it will be upgraded before January 2020.

 

- - - Updated - - -

 

Thanks everyone for your help