'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Visio 2016 Installing KMS Instead of MAK Volume License
Question details
The user needs to force the Office Deployment Tool to install the MAK volume-licensed version of Visio 2016 instead of defaulting to the KMS edition.
- Product
- Microsoft Visio 2016
- Device & OS
- not provided
- Scenario
- Deploying Visio 2016 using the Office Deployment Tool (ODT) for a volume-licensed environment.
- Observed behavior
- The installation processes the KMS edition instead of the intended volume-licensed version associated with MAK or S2R-P keys.
Ensure you have administrative privileges on the target machine and have your organization's valid Multiple Activation Key (MAK) for Visio 2016 readily available.
Update Deployment Tool and Reconfigure XML
Download the latest Office Deployment Tool and correct the configuration file to specify the proper Product ID and MAK key.
Outdated deployment tools or incorrect XML attributes often cause the installer to fall back to the default KMS client behavior. Updating the tool and explicitly setting the PIDKEY forces the MAK installation.
Visit the official Microsoft Download Center, download the latest version of the Office Deployment Tool, and extract the files to a local folder.
Uninstall any existing or failed Visio 2016 installations from the Control Panel and clear old activation data using the ospp.vbs script to prevent conflicts.
Open your configuration.xml file in a text editor like Notepad. Verify that the Product ID is set to the correct perpetual volume-licensed version, such as VisioProXVolume or VisioStdXVolume.
Add the PIDKEY attribute to the Product element in your XML file (e.g., PIDKEY="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX") using your valid MAK key.
Open Command Prompt as an administrator, navigate to the ODT folder, and run the command 'setup.exe /configure configuration.xml' to initiate the correct installation.
Diagnose Network Blocks and Review Installation Logs
If the XML configuration is correct but the issue persists, check for network interference and review the ODT log files.
Switch to WPS Office for a Hassle-Free Experience
Tired of dealing with complex deployment tools, XML configurations, and KMS/MAK activation errors? WPS Office offers a powerful, lightweight alternative that installs in seconds without the administrative overhead.
Frequently Asked Questions
Why does the Office Deployment Tool default to KMS?
By default, Microsoft configures volume-licensed versions of Office and Visio as KMS clients. To bypass this, you must explicitly provide a Multiple Activation Key (MAK) using the PIDKEY attribute in your configuration.xml file.
What is the correct Product ID for a Visio 2016 volume license?
For volume licensing deployments via ODT, you should use 'VisioProXVolume' for Visio Professional or 'VisioStdXVolume' for Visio Standard. Do not use retail product IDs like 'VisioProRetail'.
How do I clear cached Office activation data before reinstalling?
Open Command Prompt as an administrator and use the ospp.vbs script with the /unpkey parameter followed by the last 5 characters of the installed product key. This clears the cache and prevents activation conflicts.
Can I change from KMS to MAK after Visio is already installed?
Yes. If Visio accidentally installed as a KMS client, you can open the application, go to File > Account, click on 'Change Product Key', and manually enter your MAK key to switch the activation method without reinstalling.
