Use the Office Deployment Tool to install volume licensed versions of Project 2016 and Visio 2016
Usually you deploy volume licensed versions of Project 2016 and Visio 2016 by using the Windows Installer (MSI) installation technology. But that won't work if you're trying to install volume licensed versions of Project 2016 and Visio 2016 on the same computer as Microsoft 365 Apps. That's because Microsoft 365 Apps uses Click-to-Run as its installation technology, and in this case, having MSI and Click-to-Run installations on the same computer isn't supported.
To help you deploy volume licensed versions of Project 2016 and Visio 2016 on the same computer as Microsoft 365 Apps, we've provided an alternative installation method: you can use the Office Deployment Tool to do the installation of Project and Visio. The Office Deployment Tool uses Click-to-Run to do the installation, instead of using Windows Installer (MSI). But, Project and Visio are still activated by volume activation methods, such as Key Management Service (KMS) or Multiple Activation Key (MAK).
- MAK keys that you use for Windows Installer (MSI) installations of Project and Visio won't work with the Office Deployment Tool. You need a different MAK key to deploy volume licensed versions of Project and Visio with the Office Deployment Tool. To get that MAK key, log into the Volume Licensing Service Center (VLSC) and use the key listed under "C2R-P for use with the Office Deployment Tool."
- These steps don't apply to volume licensed versions of Project 2019 and Visio 2019. For more information about deploying volume licensed versions of Project 2019 and Visio 2019, see Deploy Office 2019.
To begin, download the most current version of the Office Deployment Tool from the Microsoft Download Center. Then, edit the Product element in the configuration file, using the appropriate ID from the following table. To use a Generic Volume License Key (GVLK) for volume activation with KMS, use the appropriate value in the table for the PIDKEY attribute.
|Project Standard 2016
|Project Professional 2016
|Visio Standard 2016
|Visio Professional 2016
Instead of using a text editor to create your configuration file, we recommend that you use the Office Customization Tool (OCT). The OCT provides a web-based interface for making your selections and creating your configuration file to be used with the Office Deployment Tool. For more information, see Overview of the Office Customization Tool.
If you are using the Office Customization Tool or want to specify the update channel manually, you must pick the same update channel as your existing Office installation is already using. For example, if you want to add Project to devices which already have Microsoft 365 Apps installed and configured for Monthly Enterprise Channel, you need to specify the same update channel for Project 2016 in the configuration file.
You can also edit the Updates element in the configuration file to determine how the installation of Project or Visio is updated. For example, you can configure it so that updates are automatically installed from the Office Content Delivery Network (CDN) on the internet, which is the default, or from a file share on your local network.
If you're not familiar with the Office Deployment Tool, it's usually used to customize deployments of Click-to-Run versions of Office products, such as Microsoft 365 Apps. For more information, see Overview of the Office Deployment Tool.
Here's an example of a configuration file that can be used to install a 64-bit version of Visio Professional 2016 in English from the Office CDN using a GVLK.
<Configuration> <Add OfficeClientEdition="64" > <Product ID="VisioProXVolume" PIDKEY="69WXN-MBYV6-22PQG-3WGHK-RM6XC"> <Language ID="en-us" /> </Product> </Add> </Configuration>
For information about other settings, see Configuration options for the Office Deployment Tool.
Then, use the Office Deployment Tool to download and install Project or Visio.