xml configuration file for ms office 2019 standard

However, it does put a bigger strain on your network since all of the install bits are coming over the internet during install. I personally like the “Light Office Install” approach the best as you get better metrics, an easier to deal with UI, and ability to put into the catalog but without having to download the “Full” content every time you want to make an update.

– Duplicate content remains on the client and takes up space (zip and extracted zip both persist in the sfd cache)

– Can use with Dell Factory Provisioning – Takes time to download the full content first, zip up everything, and then upload to our console – Can leverage our CDN integration with Akamai as well as P2P solutions such as BranchCache or Adaptiva – Cannot use with Dell Factory Provisioning Full Office Install via Software Distribution (uses WS1’s CDN, Akamai) – Gives you full control of the content and how it’s installed on client. – P2P is limited to Delivery Optimization (DO) and doesn’t leverage BranchCache or Adaptiva. – Fast! Installs download and install very quickly – Not really a con, but this will use Microsoft’s CDN network instead of Akamai – Very quick and easy to config and upload to console Light Office Install via Software Distribution (uses Microsoft’s CDN) – You don’t really manage the content as the Office will download bits as needed during the install – Can’t display in the Hub catalog for self service – You can lose some version control and app install metrics that are normally available in Software Distribution

– Fast! Installs download and install very quickly – The profile requires you to serialize the Office configuration xml and then create a “custom settings” profile in WS1. – It will automatically install the “latest” version of Office whenever the profile runs (if your config is set to that) Method Pros Cons Office CSP – You don’t have to bother with downloading content or passing the configuration.xml to setup.exe

I’ve tried to summarize the Pros and Cons in a table. VMware Workspace ONE supports many ways of deploying Office 365 on Windows 10, but it can often be confusing on which one is best.

Xml configuration file for ms office 2019 standard