Deploy Office 2016 using the Microsoft Office Customization Tool

4/26/2018 69983 Contributors

You wish to deploy Office 2016 using the Microsoft Office Customization Tool (OCT) and PDQ Deploy to n machines within your organization.


  • While this deployment is for 32-bit Office 2016 ProPlus, the steps can be easily modified for any Office 2016 product using the OCT for either x86 or x64 deployments.
  • This deployment is not meant for any Office 365 or Click-to-run product. For help deploying Office 365, see our Office 365 Deployment Guide.
  • These instructions are supplied for guidance only. The results have been tested on multiple machines, but every environment is different and the ability to cover all situations is not possible. It is recommended the instructions in this knowledgebase be thoroughly tested in a lab environment prior to deployment in a production environment.

To deploy Office 2016, the following tasks must be performed and conditions must be met:

  • Unpack or copy the contents of the Office 2016 ISO (or other image format) to a location on your PDQ Deploy console’s machine or on a network share.
  • The unpacked contents must contain the setup.exe Office setup executable file.
  • The unpacked contents must contain the admin directory in order to use the OCT. You can also download the latest version of the OCT from Microsoft, Office 2016 Administrative Template files (ADMX/ADML) and Office Customization Tool.

Step 1: Configuring Office Setup with the OCT

1. Drag the setup.exe to Start > Run or type the path to the setup.exe in the Office 2016 directory and append that path with /admin to invoke the OCT. For example:

c:\path\to\Officefiles\setup.exe /admin
\\myserver\myshare\Officefiles\setup.exe /admin

2. This will open the Microsoft Office Customization Tool. Select the product from the list (if provided) and click OK.

3. Select the Install location and organization name from the navigation tree. It is not advised to change the default installation path. Put in your organization name as appropriate.

4. Next, choose the following parameters:

  • licensing method from the Licensing and user interface navigation tree element. The license key must be correct. If an incorrect key is used, the deployment will fail, typically with an error code 30059 (for more information on this error, see, Use of an incorrect key can also cause the deployment to hang indefinitely since there is no UI to allow user interaction to close the window. If in doubt, test to ensure the key is correct.
  • Check the “accept the terms in the License Agreement”
  • Select a “Display level” as None
  • Ensure that “Suppress modal” is checked
  • It is not necessary to check “Completion notice” and “No cancel” since those are automatically suppressed with a None display level

5. Select Remove previous installations from the navigation tree. Select the appropriate option. Note: this will not remove Visio, SharePoint, or SharePoint Designer. That requires a separate uninstall. It will only remove the previous versions of the products listed in the Program window.

6. Next, select Modify Setup properties from the navigation tree. This step entails adding SETUP_REBOOT to a Value of Never (this doesn't prevent a reboot, it just suppresses the reboot prompt) and adding HIDEUPDATEUI to a Value of True (this hides the Check for Updates button on the completion dialog box). For more information on these setup properties, please refer to (2013 version):

Click on the “Add” button, and add SETUP_REBOOT as the Name and Never as the Value.

7. Repeat the process outlined in the previous step to add HIDEUPDATEUI as the Name and True as the Value. You should see this when both steps have been completed:

8. Under Modify user settings in the navigation tree, make the necessary changes as desired. If you have previous versions of Office installed, make sure that “Migrate user settings” is checked (default). If this is a new organizational Office installation, you can make any desired user-context changes here if the defaults are inadequate.

9. Next, set the installation state of your Office 2016 installation.

In this instance, Microsoft Office is set to "Run all from my computer"

The result will look like (minus the handy bubble dialog notes),

10. Make any additional changes to the Office setup, such as Outlook Profile, as required. For most installations the default values are sufficiently conservative to retain your existing user settings. For instance, the default Outlook profile settings is a very reasonable, “Use existing profile:”

11. Once all changes have been configured, checked, and double-checked, save the MSP. Typically, this is saved in the same directory as the Office setup.exe file. For the purposes of this article, the saved MSP is called Office2016ProPlus32.MSP.

Step 2: Configuring PDQ Deploy

You can download PDQ Deploy for free here.

1. Open PDQ Deploy and create a New Package (Ctrl+N):

  • Name the Package something meaningful. In this example, the package is named Office 2016 Pro Plus.
  • Name the Install Step something equally as meaningful.
  • Navigate to the “Install File” location, which will be the location of the setup.exe from the first step of Step 1 above.
  • Under “Parameters,” add the following: /adminfile [name of MSP file]
  • Under “Additional Files” make sure that “Include Entire Directory” is checked. If this is blank, the install will fail.

2. Once the necessary elements have been added to the deployment, a bubble/arrow-free Install Step window would look something like this (For Free Mode packages, the package is complete when correctly configured):

3. Next, set the conditions (Pro or Enterprise Mode required. You can get a free trial of Enterprise mode here) by clicking on the Conditions tab and making the appropriate selection(s). For instance, only install on certain operating systems.

And the right OS architecture for your deployment.


4. A manual reboot will likely be required on target machines once the deployment is successful (Pro or Enterprise Mode required). You can skip to the final step at this point.

For Pro and Enterprise Mode packages, a Reboot step can be added to reboot machines after the installation completes. You will want to make sure and set the conditions here as well to avoid an unintended reboot of something important.

5. Save the Office 2016 package, deploy, and enjoy.


Installation Hangs:
In certain rare cases, it might be necessary to modify the Options tab > Run As field. If your deployment times out, change the Run As from Deploy User to Deploy User (Interactive). You should only make this change if you receive time out errors or the deployment hangs indefinitely.

If the above does not resolve the issue, there might be a UAC issue where Office will run the bootstrapper, and UAC will notify the user. A customer, Ray K., came up with a solution by adding an Install Step that runs a batch file containing the following prior to the Office 2016 Install Step:

%windir%\System32\cmd.exe /k %windir%\System32\reg.exe ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLUA /t REG_DWORD /d 0 /f

This effectively disables UAC from notifying a user of changes being made to the computer. For more information on this registry setting, please see:

See Also:
Deploy Office 2013 Using the Office Customization Tool (OCT) and PDQ Deploy
Office 2016 Administrative Template files (ADMX/ADML) and Office Customization Tool