This blog post describes how to deploy Microsoft Office 2016 using the Microsoft Office Customization Tool (OCT) and PDQ Deploy to several machines in a enterprise environment.
- While this deployment is for 32-bit Office 2016 Professional Plus, 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.
- 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 blog post be thoroughly tested in a lab environment prior to deployment in a production environment.
To deploy Microsoft 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. In my lab I use \\dc01\software$\Office 2016
- 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.
Configuring Office Setup with the OCT
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: E:\setup.exe /admin or “\\dc01\software$\Office 2016\setup.exe” /admin
This will open the Microsoft Office Customization Tool. Select the product from the list (if provided) and click OK.
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.
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. Use of an incorrect key can also cause the deployment to hang indefinitely since there is no User Interface 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
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.
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): https://technet.microsoft.com/en-us/library/cc179018.aspx
Click on the “Add” button, and add SETUP_REBOOT as the Name and Never as the Value.
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:
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.
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)
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:”
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 blog post, the saved MSP is called Office2016ProPlus32.MSP.
Install Microsoft Office Professional 2016
\\dc01\mdtbuildlab$\Applications\Office_2016\x64\setup.exe /adminfile \\dc01\mdtbuildlab$\Applications\Office_2016\x64\Office_2016.MSP