Note: This method does not work with MAK versions of Project/Visio, only KMS. Microsoft is working on a fix for this.
Some folks may still need the ability to deploy the KMS version of Project and Visio alongside the Office 365 Suite. Maybe you didn’t buy licenses of Project and Visio through Office 365 because you still had KMS versions. This post will go over how to do that, as normally these two versions are not compatible.
To complete this, you will need the latest version of the Office Deployment Tool, found here: https://microsoft.com/en-us/download/details.aspx?id=49117. You do NOT need your KMS Project/Visio media.
I am going to illustrate this process with Project. The exact same process will work with Visio, just change the product ID in your configuration file. Here are the product IDs that you need, depending on the version of Project and Visio:
ProjectStdXVolume – Project Standard 2016
ProjectProXVolume – Project Pro 2016
VisioStdXVolume – Visio Standard 2016
VisioProXVolume – Visio Pro 2016
The process for using the Office Deployment Tool is the same as when you deploy the Office 365 Suite. You need to download the bits, then deploy the program. You do this as one step if everyone gets Project and Visio, or separate them out. They can use the same content download, so you only need to download that once.
I suggest making the SourcePath parameter the same directory that contains your setup.exe. Example download XML file:
You execute the download by running this command:
setup.exe /download configuration.xml
Now you can use this XML to deploy:
All of the same configurations apply. My screenshot will show all GUI’s (but not ask any questions). You change that by changing the display level line from “Full” to “None” to totally hide the GUI.
You install the products using this command line (if the name of my XML file is project.xml):
setup.exe /configure project.xml
Uninstall Configuration XML
If you need to uninstall of these products, here’s an example of an uninstall XML file:
You can execute the uninstall in the same way that you execute the install (if the name of my uninstall XML file is called uninstall-project.xml):
setup.exe /configure uninstall-project.xml
Deployment via ConfigMgr
If you don’t use ConfigMgr for software deployment, you can stop reading now. The rest of this post will detail how to create the application.
Deployment using ConfigMgr is pretty straightforward. Build an application as you normally would. Here’s what your program tab should look like:
When it gets time to add the detection method, there’s what I would use:
For the different SKU’s, change the last part of the registry key to reflect the values listed for the XML above. For example, for Visio Standard, the last part should read “VisioStdXVolume – en-us”.
Now you’re all set with the KMS version of Project and Visio.
All content provided on this blog is for information purposes only. Windows Management Experts, Inc makes no representation as to accuracy or completeness of any information on this site. Windows Management Experts, Inc will not be liable for any errors or omission in this information nor for the availability of this information. It is highly recommended that you consult one of our technical consultants, should you need any further assistance.