You may be realizing that you need to change some of your practices if you’ve adopted Office 365. Microsoft has changed the way they are digitally packaging your software and they don’t mix well (at all). In the past you would typically have a volume license and an installer (bunch of files)…Everything is in a new format called click to run and if you’ve tried to install Office 365 or the Visio volume license before or after each other, the installation will fail showing something like this
To solve for this, it’s important to note that you are going to have to make some changes to the way you are managing your packages, and now is the perfect time to learn the Office deployment tool and use click to run which we will attempt to take you through.
Office Deployment Tool
The first thing to take note of is you will not be using your old downloaded files so you can park them. We will be using the Office Deployment tool to download and store the required files, then we will be using those files and configuration to setup the installation and specify parameters and requirements.
The first thing to do is download the Office Deployment Tool and extract it. You can download it here.
Once you extract it, you will have two files setup.exe and configuration.xml. These files are not useful yet, and I recommend that you store them in a location that makes sense. You will likely end up with multiple versions of the xml file referring to different installations with different options. The first thing to do is configure your XML file. In my configuration I set
- The location where I want files to be installed from.
- What version/edition I wanted
- The Product ID which specifies that I want the Volume license version
- the PIDKey which specifies my install key
- Display level to install
- and logging level
There are some other options in there that are less important. You can get a list of Product ID’s for Volume licenses here.
My Config file looks like this
Now to download the files, you will simply need to call the setup.exe with a switch download and refer to the XML so it puts the files in the right place. It should look like this. Note this is done through command line or PowerShell.
\\path\folder\setup.exe /download \\patch\folder\Visio2016.xml
Once completed, you might end up with a bunch of files that look like the following
The important ones to note are of course the setup.exe and Visio2016.xml. The configuartion.xml I always leave alone in it’s original format. Once it downloads the files you will have the VisioPro2016 folder that you should leave and you should create a folder called logs to store your log files.
After testing this, I found with others that I had to download the 32-bit version, which you can use this blog to practice with. I can’t stress enough how important it is to keep a logs folder…after awhile you’ll get something that looks like this so you can track how your CTR apps are doing and trend any potential failures.