Upgrading from Office 2013 C2R to Office 2016 C2R
In Office 2016 Click to Run (further in this article mentioned as Office 2016) the installation method does not differ from Office 2013 Click to Run (further in this article mentioned as Office 2013). In both versions you download the installation sources from the internet and create a virtual package or deploy Office 2016 via SCCM to the clients. If Office 2013 has already been installed it will be upgraded automatically to Office 2016.
Download the Office Deployment Tool and deploy O365 via SCCM
- Download the Office 2016 Deployment Tool and extract the file.
- Create this download xml to download the installation sources:
- To download run the command:
"%~dp0setup.exe" /download "%~dp0download.xml"
- Create this deploy xml to deploy the downloaded Office 365 installation files:
- In this case the application is deployed via SCCM 2012 task sequence with the command:
setup.exe /configure deploy.xml
Create the policy
- Download and extract the Office 2016 Administrative Template files (ADMX/ADML) and Office Customization Tool.
- Created the policy. I used WMI filtering to make sure that the policy is only applied to the machines where Office 365 has been installed.
Select * From win32_Directory where name="c:\\Program Files\\Microsoft Office 15\\root\\office15"
- The policy as it has been created:
- Update Branch
This is a new feature which gives you the option to test the pre-releases of Office 2016. More information can be found at Overview of update branches for Office 365 ProPlus.
- The update deadline. It is in the format MM/DD/YYYY HH:MM where HH:MM is in UTC time (24 hours time):
- The target version. You can enter whatever version, even a downgrade is possible.
Testing on the client
- When using regedit you see that the correct registry settings have been set:
- Further updates will be applied automatically once available.