In this article, we are going to show you how to deploy Office 2016 (centralized 32-bit MS Office Professional Plus 2016) by using System Center Configuration Manager 2012 R2. Let’s review the process of preparing your own MSP package with Office settings. Also we have to create a program for SCCM server and install software on the client computers.
How to deploy Office 2016 by using SCCM 2012 R2?
You should download and place the VL copy of MS Office for Windows in catalog, which will be the source for the SCCM package files (for example msk-distr01ApplicationOffice 2016).
Along with Office, Microsoft has released a new version of MS Office Deployment Tool, which allows you to create Office 2016 customized installation scenarios. This tool can help you configure settings, redefine the product settings, language settings, etc.
Note. The deployment procedure will only work for a corporate (VL) edition of Office 2016.
Firstly, you have to download Office 2016 deployment tool and run OfficeDeploymentTool.exe. Specify the directory where you want to unpack the setup and configuration files.
Run the Office Customization Tool (OCT) by typing setup.exe/admin.
Office 2016 Setup will start in a special mode in which you can define the settings that should be used if you deploy Office on users machines. The program will create the MSP file, which contains all of the settings you should store in the Updates directory.
Note. Keep in mind that the MSP file is the architecture-specific file, so x86 and x64 editions require their own MSP files.
Tip. You can also deploy MS Office 2016 by using MDT 2013, check our article here.
After that, we will create the MSP file that allows you to install Office in the automatic mode without user interaction.
Select Create a new setup customization file for following product, mark the desired product edition and click OK.
In the Install location and organization name section, specify the information about organization.
Then, in Licensing and user interface section, select Use KMS client key or manually enter the MAK key by clicking Enter another production key.
Turn on the checkbox to accept the terms of your license agreement. As a Display level, select Basic, turn on the checkbox on Suppress modal and No cancel. In these settings, users should not enter any license information and confirm the license agreement.
In Modify Setup properties section, click Add and append a SETUP_REBOOT parameter with Never value.
After that, we have to disable the users initial configuration wizard by changing Modify user settings -> Microsoft Office 2016 -> Privacy -> Trust Center. Disable Opt-in Wizard on first run parameter should be enabled.
Save the received settings (File -> Save As) in the MSP file. Office Installer automatically checks MSP file for the presence, and in case of error, it will run complete installation. After that, close the OCT utility.
The next step is SCCM application creation.
Open the SCCM console and create a new application in Software Library section.
Select Automatically detect information and specify the UNC path to the proplusww.msi file.
After that, we have to provide information about the application. In Install behavior section choose Install for system.
Open the application properties and in Deployment Types section select the MSI file. After that, go to Edit mode. On the Content tab, specify the path to the directory with Office 2016.
On the Programs tab, enter setup.exe in the Installation program. Save your changes.
We need to make sure that the application available to Distribution Point.
Open the Deploy Software Wizard and select the following values: Action – Install, Purpose – Available.
After few minutes, the application will be available on the user side.
The user can choose Microsoft Office Professional Plus 2016 in the application list and run it just by clicking the Install Selected.
You can open CCMLogsAppenforce.log on demand.
The application will be downloaded and installed on the client computer.
The installation status now will be changed to Installed. It means, that Office 2016 installed properly.
- HTTP/HTTPS Requests via Invoke-WebRequest PowerShell Cmdlet - September 25, 2021
- How to Allow Saved Credentials for RDP Connection? - September 23, 2021
- How to Convert ESD to WIM File on Windows 10? - September 17, 2021