Ever wondered how you can save time when installing a new version of Office across your organization? Well if you’ve landed on this page then you’re about to find out. This guide is particularly useful if you have to install office on multiple machines, as it means you don’t have to download it each time. And this is especially handy if you have slow internet connection. So, let’s get started…
First of all, you need to get the right Office Deployment tool for the version of Office you would like to install. Choose your preferred package below and download the deployment tool.
If you have a server, I would start off by creating a folder on the data drive to keep everything neat and tidy. Name this folder anything you would like and make sure users can access it by making it a share with ‘Everyone’ and ‘Full Control’.
Copy the deployment tool you have downloaded into this folder and run this as an Administrator. This will extract the files into the location you run the .exe so make sure it’s where you want it to be.
Once this has been extracted you will get a ‘setup.exe’ and a ‘configuration.xml’. To make life easy we are going to separate the configuration file that Microsoft provide and split this into two of our own. Delete the ‘configuration.xml’ and download the files below.
Click here to download the XML files (ConfigOffice.xml + DownloadOffice.xml)
Time to Tamper
The next step is to make sure we get the correct syntax in the xml files.
Here is a full breakdown of what each line of code will do: https://technet.microsoft.com/en-us/library/jj219426.aspx
We will start by editing the DownloadOffice.xml file and you will more than likely only need to change two variables, the ‘SourcePath’ and ‘Product ID’. I would always advise installing the 32-bit client edition and so this can be left as default.
If you are unsure which ‘Product ID’ you should be using based on your Office 365 plan, then the following table should allow you to decide:
The ‘SourcePath’ will need to be a location the users have access to and so for the purpose of the blog, mine would look something like this:
<Add SourcePath="\\KS-DC01\Office 2016" OfficeClientEdition="32" >
So, as my business uses Office 365 Enterprise E3, the Product ID syntax will look like this:
If you get really stuck, then you can use a great tool that builds the XML files for you (It even has a GUI!) http://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.html
Moving onto the ConfigOffice.xml. Try to keep everything as I left it apart from you will need to change the ‘SourcePath’ and ‘Product ID’ to match your DownloadOffice.xml.
The only thing you will need to make sure is set correctly is the ‘Property Name=’ and so for non-remote desktop installations (That’s right you can even do it on a RDS as well!) you will want it to look like this:
Non RDS Installations: <Property Name="AUTOACTIVATE"
RDS Installations: <Property Name="SharedComputerLicensing"
… and breathe. If you’re still with me then we are ready to install. Keep those fingers crosses that the XML files you have created are correct.
The Final Furlong
1. Open CMD as an Administrator
2. Change the directory to the location of the Office Deployment folder where everything is stored.
3. Run “Dir” and make sure that you see all of the relevant files and folders.
To download your Office package, use the following command: “setup.exe /download DownloadOffice.xml”
This will go to the internet and download the version of Office 365 you have specified in your XML files. When this is done the command prompt will allow you to start typing again so look out for that.
Your Office deployment folder should look a little like this:
As you can see you now have an Office folder in here, this is the downloaded Office product.
To install, follow above steps 1-3. Once you are there we will use a slightly different command to install. Type “setup.exe /configure ConfigOffice.xml” and hit enter.
If you have managed to follow this all correctly, then you will get the Office splash screen to appear.
The Easy Bit
Enjoy! Sit back, relax and make yourself a brew …
If you have any questions or need any help with any of this, drop a comment below and I will happily help you out.