How to deploy Office 2016 using SCCM 2012 R2 In this post we will see how to deploy Office 2016 using SCCM 2012 R2. Along with Office 2016, Microsoft has released office 2016 deployment tool. The Office 2016 Deployment Tool allows the administrator to customize and manage Office 2016 Click-to-Run deployments. This tool will help administrators to manage installations sources, product or language combinations, and deployment configuration options for Office Click-to-Run. If you are confused between between Office 2016 and Office 365 here is some info about it. Microsoft Office 2016 is an Office suite that includes Microsoft Word, Excel, PowerPoint, Visual Basic for Applications, and Microsoft Query. There is a Mac version and a Windows version of Office 2016. Office 365 is the name Microsoft gives to a subscription service. Within this service various options are available depending on what you need and want to pay for. Microsoft Office 2016 for Mac and Windows are both available within an Office 365 subscription. Talking about the deployment of office 2016, I have got the Microsoft Office Professional Plus 2016 32bit volume license copy with me, we shall see how to deploy it.
How to deploy office 2016 using SCCM 2012 R2
On the Configuration Manager server run the command prompt as administrator, change the path where office 2016 setup files are located. Run the command setup.exe /admin.
Click on Licensing and user interface, choose the option Use KMS client key if you have KMS server in your organization for activating office 2016, else choose Enter another product key and enter the office 2016 key. Click on I accept the terms in the license agreement. Select the Display level as Basic, check the box for Suppress modal and No cancel.
Now click on Modify Setup properties. Click Add, provide the Name as SETUP_REBOOT and Value as Never. Click OK.
Select Modify user settings > Microsoft Office 2016 > Privacy > Trust Center. Double click the setting Disable Opt-in Wizard on first run and set the status as Enabled.
Now click on File -> Save As -> save the customization file inside Updates folder. Close the OCT tool.
Open the SCCM 2012 R2 console, under the Application Management, right click Applications and click Create Application. Choose Automatically detect information and provide the path to file proplusww.msi. Click Next.
The application information has been imported from msi file. Click Next.
You can specify a little information about this application. We will change the Installation program command later. Choose the Install behavior as Install for system. Click Next.
The Application has been created successfully. Click Close.
Right click the Office 2016 application, click on Properties. Click on Deployment Types tab, click on the msi file and click Edit. Click on Content tab, set the Content location to Office 2016 folder ( or a folder where Office 2016 installation files are present, remove proplus.ww after Office 2016 ). Click on Apply.
Click on Programs tab, change the Installation Program command to setup.exe. Click on Apply and OK.
The next step is to make the application available to DP. Right click the Office 2016 application, click on Distribute Content, choose you DP and wait until the application is available with DP. You can verify this by checking the Content Status of the Office 2016 application under Distribution Status.
Deploy the Office 2016 application to the desired collection. Right click on the Office 2016 application and click on Deploy. Choose the Device Collection and choose the Action as Install and Purpose as Available. (I haven’t covered the screenshots of deploying application as it’s simple to deploy an application to collection).
After few minutes, on the client computer we see that the application is available. Select the software and click on Install Selected.
Open Appenforce.log file in case you face issues with installation. You could also monitor the installation process.
The application is first downloaded to the client computer and then installed. We now see that the application is installed successfully.