Once trial versions expire, they will revert back to reduced functionality, essentially becoming file viewers.However, before you proceed, bear the following points in mind: If the user hit Cancel, the deployment will return an error in SCCM reports.We've rechecked all the links as of the time of publishing this update to ensure that they're fully working.One prompt for the user to know upgrade is coming.Suggestion : Allow users to run the program independently of assignments will allow more flexibility for your users to upgrade.Deploy the package/program just as any other packages.This is to help interaction with opened Office applications Check Allow user to view and interact with the program installation.Command Line : setup.exe /configure configuration.xml.The source folder must be the folder with the Setup.exe, Configuration.xml and Office folder downloaded in previous step.Create a standard package for Office 365 2016.It will contain the Office 365 2016 bits for offline installation

This will create an Office folder under the running path.

Open a command prompt, browse to your office directory and launch : setup.exe /download download.xml.

First, we need to download the latest Office 365 2016 version.

We will now create a standard package for the upgrade.įor a more detailed version of How-to deploy Office 365 2016, please see our previous post here You can find more details about XML files for Office 365 here Create Office 365 2016 Package It will know it’s upgrading from 2013 automatically. Otherwise, the XML as no specific configuration related to upgrade.

Modify the language that you need using.

This will allow user to see a prompt when the upgrade starts if any Office application is open and allow time to save files.This will allow user to interact with the install, in order to see the prompt to close open application if needed.The configuration.xml has more details in it : The download.xml specify the Channel to be used, the product and language : We will create and use one XML file to download the Office 365 bits for an offline installation/upgrade and another XML for the configuration. Office 365 Click-to-run installations, are controlled by XML files. 2117 from January 2017 was used for this postĬreate Download.xml and Configuration.xml File This post will cover everything you need to know to upgrade Office 365 2013 to Office 365 2016 with SCCM. Those posts applies to the 2016 version of Office 365. In previous posts, we covered how to manage updates for Office 365 2016 with SCCM and describe the Office 365 dashboard. With the end of support for Office 365 2013 on Febuary 28 2017, administrators must take action to upgrade Office 365 2013 to Office 365 2016.

Can you upgrade office 2013 to 2016