How to deploy Office 365 ProPlus via the Office CSP with Workspace ONE

Starting with version 1703 (Creator’s Update), Windows 10 brings the addition of the Office CSP for easy deployment of Office 365.
  • You don’t have to fuss around with the actual files of the O365 install.
  • You only have to really manage the “config” file and windows takes care of the rest
  • You can specify install from MS’s CDN or a local file storage


  • Harder to schedule the deployment, control the version, or track number of installs.
  • Doesn’t leverage Workspace ONE’s Akamai CDN integration
  • Tracking the “Status” of the install is not easy


  1. Go to the Office Customization tool website.
  2. Built and and create your deployment configuration. Here’s what mine looks like exported:
    <Info Description=”VMware production Office 365 Pro Plus configuration.” />
    <Add OfficeClientEdition=”64″ Channel=”Monthly” AllowCdnFallback=”TRUE” ForceUpgrade=”TRUE”>
    <Product ID=”O365ProPlusRetail”>
    <Language ID=”en-us” />
    <ExcludeApp ID=”Groove” />
    <ExcludeApp ID=”Access”/>
    <Property Name=”SharedComputerLicensing” Value=”0″ />
    <Property Name=”PinIconsToTaskbar” Value=”TRUE” />
    <Property Name=”SCLCacheOverride” Value=”0″ />
    <Updates Enabled=”TRUE” />
    <RemoveMSI All=”TRUE” />
    <Setup Name=”Company” Value=”VMware” />
    <Logging Level=”Standard” Path=”%temp%\office365″ />
  3. Now you will need to take this XML and “serialize” it so that it can be read by the Office CSP.  You can go to this free web page to do so. Simply copy/paste your XML in the top box to get the serialized output.
    &lt;Info Description=&quot;VMware production Office 365 Pro Plus configuration.&quot; /&gt;
    &lt;Add OfficeClientEdition=&quot;64&quot; Channel=&quot;Monthly&quot; AllowCdnFallback=&quot;TRUE&quot; ForceUpgrade=&quot;TRUE&quot;&gt;
    &lt;Product ID=&quot;O365ProPlusRetail&quot;&gt;
    &lt;Language ID=&quot;en-us&quot; /&gt;
    &lt;ExcludeApp ID=&quot;Groove&quot; /&gt;
    &lt;ExcludeApp ID=&quot;Access&quot;/&gt;
    &lt;Property Name=&quot;SharedComputerLicensing&quot; Value=&quot;0&quot; /&gt;
    &lt;Property Name=&quot;PinIconsToTaskbar&quot; Value=&quot;TRUE&quot; /&gt;
    &lt;Property Name=&quot;SCLCacheOverride&quot; Value=&quot;0&quot; /&gt;
    &lt;Updates Enabled=&quot;TRUE&quot; /&gt;
    &lt;RemoveMSI All=&quot;TRUE&quot; /&gt;
    &lt;Setup Name=&quot;Company&quot; Value=&quot;VMware&quot; /&gt;
    &lt;Logging Level=&quot;Standard&quot; Path=&quot;%temp%\office365&quot; /&gt;
  4. Before creating a new Workspace ONE profile, we need to generate a custom XML in order to use this CSP.
  5. To do that, go to our Policy Builder tool to generate a custom XML (syncML) that we can use to deploy a Workspace ONE profile.
  6. Select the version of Windows 10 you will be deploying to. See the office Office CSP page for different features supported by MS based on the version of Windows 10.
  7. Search for the “Office” CSP
  8. Check the box next to “Office” and click configure.
  9. Expand the “Device” section and paste in your serialized XML into the “Install” node.For some reason, the DDF that is used to build out this template does not correctly update the target “LocURI” and so you will need to manually update it to the following:
  10. Click the “Copy” button.
  11. Go back to Workspace ONE console.
  12. Create a new Windows 1o profile (Windows –> Windows Desktop –> Device Profile)
  13. Go the “Custom Settings” area at the bottom. Paste the content into the top section.
  14. Add the “Uninstall” XML settings to the bottom section:
    <Format xmlns=”syncml:metinf”>chr</Format>
    <Data>&lt;Configuration&gt;&lt;Remove All=&quot;TRUE&quot;/&gt;&lt;Display Level=&quot;None&quot; AcceptEULA=&quot;TRUE&quot; /&gt;&lt;/Configuration&gt;</Data>
    TIP: Based on my testing, the system does need to reboot first before you can successfully deploy the uninstall command. Also, you can create a separate “Uninstall Microsoft Office 365” profile that has the uninstall command in the “Install Settings” are case you need to do mass uninstall.
  15. The final output should look like this:
  16. Go back to the “General” section of the profile and assign this to your test Smart Group. I’d recommend setting this to “optional” when testing. When ready to deploy, click “Save and Publish. Then on the device you want to deploy it to, browse to the device in the console, go to this profile and click “Install”.
  17. On your device you should start to see the install happening if you open up task manager. The install should complete within a few minutes. It’s a surprisingly fast install!
  18. NOTE: Since you deployed this as a “Device” profile, the end user isn’t going to be able to see progress of the install. If you want to have the user see the install, change the LocURI section to be ./User/Vendor/MSFT/Office/Installation/0AA79349-F334-4859-96E8-B4AB43E9FEA0/install (instead of ./Device/…)

This Post Has 2 Comments

  1. The embedded screenshots are not uploading to the website. could you please investigate. Thanks

    1. Photos should be fixed! It also gave me the opportunity to update the article with the latest information.

Leave a Reply