xml configuration file for ms office 2019 standard

Set the share permissions appropriately, and make sure to edit the NTFS settings to allow domain users and domain computers read access.Ĭreate a text file in the share directory and name it something that makes sense, in my case it was installvisio.txt. Once complete, move the directory to a network share location. The process will download the Office 2019 packages to a directory called “data” within the ODT folder. Replace configuration.xml with the name of the XML exported earlier. Using an elevated command prompt under the ODT folder issue the following: If set to FULL the installer will be visible. The XML file I used to deploy Visio 2019 using a volume license looked like this: Export the XML file and place it in the directory where you extracted the ODT.

Set your preferences, in my case, it was a volume license MAK copy of Visio 2019. Next, use the Microsoft tool for generating an XML file HERE. Run the executable and extract the files to a directory. I hope it helps someone looking to accomplish the same thing I was.įirst off, head over to Microsoft and download the Office Deployment Tool (ODT) HERE. It took me quite a bit of research and troubleshooting to get this method to work.

There may be more than one way to accomplish GPO deployment of Office, and I do not claim to have the best method. I was tasked with coming up with a method for deploying Office via GPO in a fully automated manner. Microsoft is moving toward using SCCM or the Office Deployment tool. There is no MSI of Office, Visio, Project, etc available to download anymore. With the advent of Office 2019, Microsoft has moved away from GPO deployment via MSI.

Xml configuration file for ms office 2019 standard