At first, I thought deploying Office 2019 the “new way” was daunting and it seemed like it was going to be a pain to deploy. It really isn’t. Even if you haven’t done it before. Here’s the basic process of it. There are tons of things you can do with it but this grazes the top to get you moving along with a quick deployment.
So the following will guide you through installing Office 365 for use on machines with Terminal Services deployed. You can of course remove the property to enable this if you wish.
Step 1 – Download the tool
Obtain the office deployment tool:
Of course you can Google Office Deployment Tool as well. Microsoft has a thing for moving stuff around more than I’d like them to.
Step 2 – Run and extract the goodies (for the lesser experienced, don’t stop now, the rest is easy!)
Run the tool, extract to a location of your choosing. Once complete, open Powershell and navigate to the folder. IE:
Step 3 – Configure the config XML file
You’ll notice they’ve included some pre-configured answer/ config files for us to use. Let’s open either the 64 or 32 bit version in a text editor like Notepad. Make sure to add the following “SharedComputerLicensing” property if you are using terminal services (Remote Desktop Deployments).
Be sure to modify things like the product id as needed. Here is a link with a list of IDs:
Here’s a list of IDs that could be used in case Microsoft moves their page….. (the first 3 are the Office 365 Editions):
<Configuration> <Product ID="O365ProPlusRetail"> <Language ID="en-us" /> </Product> </Add> <Display Level="None" AcceptEULA="TRUE" /> <Property Name="SharedComputerLicensing" Value="1" /> <Updates Enabled="TRUE" Channel="Monthly" /> </Configuration>
Google is your friend when you don’t know one of these properties. 🙂
Step 4 – Run it!!
Run it, deploy it, download it, whatever you want! Both commands are shown below. Download is good for network deployment. Run is great for a local install.
.\setup.exe /configure configFileName.xmlOR
.\setup.exe /download configFileName.xml