The WinOps Blog

Package Creation

The first thing to understand is that to update an Office installation, you need to use the OfficeC2RClient.exe program that resides on the client. This command support various command line and switches. In our example, we will use Updatetoversion to specify the version 7766.2119 (1701) and forceappshutdown to force Office applications to close.

The tricky part is that OfficeC2RClient.exe is specific to the system architecture (x86 or x64). In order to make a command line that works on both architectures, you need to use the %CommonProgramW6432% system variable that works on both x86 and x64 systems.

• In the SCCM Console, go to Software Library / Application Management / Packages
• Create a new package, name it and do not specify source file. This is because the .exe needed for Office installation is on the client computer.

• Create a Standard Program

• For the command line, find the desired Office version build number (In our case 1701 – 16.0.7766.2119). You need to add 16.0 to the build version in your command line.

• Command Line : %CommonProgramW6432%\microsoft shared\ClickToRun\OfficeC2RClient.exe” /update user updatetoversion=16.0.7766.2119 forceappshutdown=True

• In the Requirements page, click Next

• Complete the wizard

Deploy Specific Office version on a test computer

We will now deploy the 1701 version on a computer that actually has version 1705 installed. Create a test collection and send the newly created program to a test device.

The installation will start on the client computer. It will take about 10-15 minutes to complete.

Office version before installation :

Office version after installation :

Make sure to use our free Office 365 report to track your Office version.