Software Deployment Question

Upgrading to Office 2016

05/12/2016 10898 views

We are currently having Office 365 with the 2013 version of Office.
We are planning to upgrade to Office 2016. When we try to install Office 2016 it fails with the below error: Upgrade failed with error code 17004
Uninstalling the 2013 version and then installing the 2016 version works fine.
We would like to configure a single deployment to uninstall 2013 version and install 2016 version via SCCM.
Any ideas implementing the above.
0 Comments   [ + ] Show comments


Community Chosen Answer

The Microsoft Office customization tool will allow you not only to install 2016 silently but also remove all previous versions before installing.  We had some issues with MAK activation but found an easy fix for it without much trouble.  Other than that, the customization tool worked wonders.  Run the setup.exe with an /admin switch to get to the configuration tool. 
Answered 05/12/2016 by: Bsickinger
Yellow Belt

All Answers

I had to removeOffice (2010), then run the O365 setup.exe with a config XML



To remove the entire office 2010 x86 suite:

"%~dp0\setup.exe" /config "%~dp0\Uninstall.xml"/Uninstall ProPlus



- <ConfigurationProduct="ProPlus">

  <Display Level="none" CompletionNotice="NO" SuppressModal="yes" AcceptEula="yes" />

  <Logging Type="standard" Path="%temp%" Template="Microsoft OfficeProfessional Plus Setup(*).txt" />

  <Setting Id="Reboot" Value="Never" />

  <Setting Id="SETUP_REBOOT" Value="NEVER" />

  <OptionState Id="ProductFiles" State="Local" Children="force" />




Command line to install O365ProPlus:

setup /configure DesktopInst3.xml


 XML file:

- <Configuration>

- <AddOfficeClientEdition="32" Channel="Deferred">

- <Product ID="O365ProPlusRetail">

  <LanguageID="en-us" />

  <ExcludeAppID="Access" />



  <UpdatesEnabled="FALSE" />

  <DisplayLevel="None" AcceptEULA="TRUE"/>

  <LoggingLevel="Standard" Path="D:\_Cache\Log"/>

  <PropertyName="AUTOACTIVATE" Value="0" />

  <PropertyName="FORCEAPPSHUTDOWN" Value="TRUE"/>

  <PropertyName="SharedComputerLicensing" Value="0" />

  <PropertyName="PinIconsToTaskbar" Value="FALSE"/>


Answered 05/10/2017 by: Womain
Senior White Belt

This content is currently hidden from public view.
Reason: Removed by member request For more information, visit our FAQ's.
We use the configuration tool to create an MSP with our custom settings that remove 2013 but also run the 2013 uninstaller first. We found that when we moved from 2010 to 2013 the 2013 installer did not remove all of the 2010 components. Running the uninstaller resolved that issue. Here is our current script that does this.

if exist "C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\" GOTO 64BIT
copy 2013uninstall.xml "C:\Program Files\Common Files\microsoft shared\OFFICE15\Office Setup Controller\2013uninstall.xml"
"C:\Program Files\Common Files\microsoft shared\OFFICE15\Office Setup Controller\setup.exe" /uninstall PROPLUS /dll OSETUP.DLL /config 2013uninstall.xml
copy 2013uninstall.xml "C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\2013uninstall.xml"
"C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\setup.exe" /uninstall PROPLUS /dll OSETUP.DLL /config 2013uninstall.xml
setup.exe /adminfile FullInstallRemovePrevious.msp
The uninstall.xml file looks like this:
<Configuration Product="ProPlus">
<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> 
<Setting Id="SETUP_REBOOT" Value="Never" />
Everything is zipped up into an archive and uploaded to the K1000. The nice thing about this method is that we actually include a few different MSP and script files for different types of installations, silent vs quiet and keep 2013 vs remove. We can then create several managed installs that call the appropriate script for the situation.

Answered 05/12/2016 by: chucksteel
Red Belt

Pretty much answered your own question?

Why don't you create a Application Deployment to remove Office 2013.

Then create a Application Deployment for Office 2016 with the criteria that Office 2013 must not be on the machine?

Or you can do it the ugly way - not recommended. So shove all of the above into one Application Deployment type, so you have a script that you run that removes and then installs Office.
Answered 05/12/2016 by: rileyz
Red Belt

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ