-->
Nov 07, 2015 Office Pro Plus is a volume licensed version so whatever you are downloading from wherever is at fault. If you have a volume license for Pro Plus, then you would have been provided with the MS link to install the program. Volume license editions of Office 2016 client products require activation. This download enables IT administrators to set up a Key Management Service (KMS) or configure a domain for Active Directory-Based activation. Either of these volume activation methods can locally activate all Office 2016 clients connected to an organization’s network.
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. Dead island rage mode crash fix.
- 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.
- Apr 20, 2021 Provides Office admins with an overview of Key Management Service (KMS), Multiple Activation Key (MAK), and Active Directory based activation methods for volume licensed versions of Office 2019 and Office 2016, including Project and Visio.
- All volume editions of Office 2016 client products are pre-installed with a Generic Volume License Key (GVLK) key, which supports automatic activation for both KMS and Active Directory-Based Activation, so you will not need to install a product key. This download contains an executable file that will extract and install KMS host license files.
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).
Important
- 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.
| Product | ID | PIDKEY |
|---|---|---|
| Project Standard 2016 | ProjectStdXVolume | D8NRQ-JTYM3-7J2DX-646CT-6836M |
| Project Professional 2016 | ProjectProXVolume | WGT24-HCNMF-FQ7XH-6M8K7-DRTW9 |
| Visio Standard 2016 | VisioStdXVolume | NY48V-PPYYH-3F4PX-XJRKJ-W4423 |
| Visio Professional 2016 | VisioProXVolume | 69WXN-MBYV6-22PQG-3WGHK-RM6XC |
Tip
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.
Microsoft Office 2016 Volume License Pack X64 Download
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. Pcclone ex serial key.
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.
Microsoft Office 2016 Volume License Pack Free Download
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.
Related topics
-->Applies to:Volume licensed versions of Office 2019 and Office 2016, including Project and Visio
All volume licensed versions of Office, including Project and Visio, have a Generic Volume License Key (GVLK) preinstalled. GVLKs support both Key Management Service (KMS) and Active Directory-based activation. On the KMS host computer configured to support volume activation of Office, you install and enable only one KMS host key to activate all volume licensed versions of Office.
If the KMS host computer is available and properly configured, activation of Office occurs transparently to the user. Office is activated the first time it runs, provided that there have been at least four previous activation requests to the KMS host computer. This is because the KMS host computer requires at least five requests before it begins activating clients.
You don't have to do anything else to enable activation of Office by KMS. KMS clients can locate a KMS host computer automatically by querying DNS for service (SRV) resource records (RRs) that publish the KMS service. For more information, see How DNS is used to find a KMS host computer.
If the network environment does not use SRV RRs, you can manually assign a KMS client to use a specific KMS host computer by configuring the HKEY_LOCAL_MACHINESoftwareMicrosoftOfficeSoftwareProtectionPlatform registry key on the KMS client. The KMS host computer name is specified by KeyManagementServiceName (REG_SZ), and the port is specified by KeyManagementServicePort (REG_SZ). The default port is 1688. These registry keys can also be set through by using ospp.vbs script. For more information about the ospp.vbs script, see Tools to manage volume activation of Office.
Configure KMS host caching
You can configure whether or not the last used KMS host computer is saved to the cache on the KMS client. If the KMS host computer is not cached, the KMS client will query DNS every time that activation is attempted. This means that the priority and weight parameters set for KMS host computers will be honored. If the KMS host computer is cached, the KMS client won't query DNS and instead will attempt to contact the cached KMS host computer that last resulted in successful activation.
Microsoft Office 2016 Volume License Pack
To configure KMS host caching, you can use the ospp.vbs script. For more information about the ospp.vbs script, see Tools to manage volume activation of Office.
To configure KMS host caching, open an elevated command prompt on the KMS client computer and go to the Program FilesMicrosoft OfficeOffice16 folder. If you installed the 32-bit version of Office on a 64-bit operating system, go to the Program Files (x86)Microsoft OfficeOffice16 folder.
To disable KMS host caching, type the following command, and then press ENTER:
To enable KMS host caching, type the following command, and then press ENTER:
Check the license status of Office
The following table describes the license state of the Office with respect to activation.
| License state | Description |
|---|---|
| Licensed | By default, the KMS client requests activation with the KMS host computer one time every seven days. (The number of days is configurable.) This design allows the maximum possible time for the client to be in the licensed state. After the client is successfully activated, it remains in the licensed state for 180 days. When in the licensed state, users do not see any notification dialog boxes prompting them to activate the client. After 180 days, the activation attempt process resumes. If activation is continually successful, the whole activation experience is transparent to the user. |
| Out-of-tolerance | If activation does not occur during the 180-day period, Office goes into the out-of-tolerance state for 30 days. Users then see notifications that request activation. |
| Unlicensed notification | If activation does not occur during the out-of-tolerance state, Office goes into the unlicensed notification state. Users then see notifications that request activation and a red title bar. |
You use the ospp.vbs script with the /dstatusall option to check the license state for all Office clients. Use the /dstatus option to check the status of the local client. For more information about using the ospp.vbs script, see Tools to manage volume activation of Office.