3 Ways to Deploy Office 365 ProPlus with VMware Workspace ONE

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

MethodProsCons
Office CSP– You don’t have to bother with downloading content or passing the configuration.xml to setup.exe
– It’s simply a profile in WS1 Console
– It will automatically install the “latest” version of Office whenever the profile runs (if your config is set to that)
– 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. The UI just isn’t that great
– You can lose some version control and app install metrics that are normally available in Software Distribution
– Can’t display in the Hub catalog for self service
– P2P is limited to Delivery Optimization (DO) and doesn’t leverage BranchCache or Adaptiva.
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
– Very quick and easy to config and upload to console
– Can be made available in hub catalog
– Fast! Installs download and install very quickly
– Not really a con, but this will use Microsoft’s CDN network instead of Akamai
– P2P is limited to Delivery Optimization (DO) and doesn’t leverage BranchCache or Adaptiva.
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.
– Can leverage our CDN integration with Akamai as well as P2P solutions such as BranchCache or Adaptiva
– Can be made available in hub catalog
– Can use with Dell Factory Provisioning
– Takes time to download the full content first, zip up everything, and then upload to our console
– Duplicate content remains on the client and takes up space (zip and extracted zip both persist in the sfd cache)

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. However, it does put a bigger strain on your network since all of the install bits are coming over the internet during install.

Build your Office XML

Every method will require you to have an XML configured as this tells Office what and how to install. It defines what apps are included or excluded, which architecture to use (i.e. 32 bit or 64), and what Office update channel it’s on and how it updates.

Go to the Office Customization tool website.

Configure the Office package per your organization’s requirements. A couple of tips on this:

  • You’ll want to make one XML for the core Office install and then separate ones for Visio and Project.
  • Make sure that OneDrive(Groove) is not selected as this is the “old” Onedrive for Business client. The OneDrive Desktop is the current and recommended version by MS.
  • Adding numerous languages can dramatically increase the size of the overall install
  • If you are upgrading from the “MSI” version (i.e. the volume edition of Office 2016), then you can include this section to remove the MSI versions:
  • Under Licensing and Activation, generally you’ll want this set to “User based” as office install counts are based on user installs in your Office 365 portal. However for shared devices or virtual desktops, you may want to use “Shared Computer” licensing.

Once you’re happy with your config, click “Export”.

Here is a sample config file (Configuration.xml) for a 64 bit Office ProPlus install set to Monthly update channel.

<Configuration ID="9b0b05c4-2c13-42b1-abbd-88867f74c9d9">
  <Add OfficeClientEdition="64" Channel="Monthly">
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
      <ExcludeApp ID="Groove" />
    </Product>
  </Add>
  <Property Name="SharedComputerLicensing" Value="0" />
  <Property Name="PinIconsToTaskbar" Value="FALSE" />
  <Property Name="SCLCacheOverride" Value="0" />
  <Property Name="AUTOACTIVATE" Value="0" />
  <Property Name="FORCEAPPSHUTDOWN" Value="FALSE" />
  <Property Name="DeviceBasedLicensing" Value="0" />
  <Updates Enabled="TRUE" />
  <RemoveMSI />
  <AppSettings>
    <Setup Name="Company" Value="VMware, Inc." />
  </AppSettings>
  <Display Level="Full" AcceptEULA="TRUE" />
  <Logging Level="Standard" Path="%TEMP%" />
</Configuration>

Deploy with Office CSP

This method leverages a built-in CSP specifically made for Office installs. Workspace ONE doesn’t have a dedicated UI for this type of profile so we’ll need to create it as a custom settings profile. And in order to do that, we’ll also need to serialize the Configuration.xml file. Go to this free web page and copy/paste your XML in the top box to get the serialized output.

Copy XML into top box and ensure you select “Encode” in the radio button

This “serialized” xml (in the bottom section) essentially is what goes in between the “<data>” nodes of the custom settings profile. We’ll walk through this next.

Build Profile

Create a new profile by clicking Add > Profile from the top of the console (ensure you are at the right Organizational Group!)

Select Windows > Windows Desktop

Picking “Device” Profile will make the install fully silent. Picking “User” profile while having Display Level=”Full” in the xml is supposed to make the install visible to the end user, but I haven’t been successful at seeing it yet. If you figure out to a way to make this work, let me know!

Fill out the “General” tab according to your preference. I recommend making this profile “Optional” assignment type.

Click on Custom Settings at the bottom of left hand pane and then “Configure”

Copy and paste this basic structure:

<Exec>
<CmdID>1</CmdID>
<Item>
<Target>
<LocURI>./Vendor/MSFT/Office/Installation/0AA79349-F334-4859-96E8-B4AB43E9FEA0/install</LocURI>
</Target>
<Meta>
<Format xmlns="syncml:metinf">chr</Format>
</Meta>
<Data>[put your serialized xml here]</Data>
</Item>
</Exec>

Then copy and paste the serialized xml data from Configuration.xml in between the <Data></Data> nodes (and of course removing the “[put your serialized xml here]” text )

For the Remove Settings area, this is where you put the uninstall command if you want the ability to uninstall office when removing the profile. If you don’t care about this, just but some random text in that box. If you do want to configure it, you’ll need to build an “uninstall” xml, serialize it and then place in between the data nodes. Here is one example (make sure you make sure the Product ID name matches the one you used in the install xml):

<Configuration>
    <Remove>
        <Product ID="O365ProPlusRetail">
            <Language ID="en-us"/>
        </Product>
    </Remove>
	<Display Level="None" AcceptEULA="TRUE"/>
</Configuration>

Here is it added to my profile:

Uninstall config

You can also 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. One example:

Go ahead and “Save and Publish” this profile

Go to a device in the console and click on “Profiles” tab. Then find the Office 365 ProPlus x64 profile, select it, and click “Install”.

Push the Install

If we pop over to the device you should start to see the install happening in task manager. The install should complete within a few minutes. It’s a surprisingly fast install! Note that this is a device level install and there will be no UI for the end user to see.

The profile shows green as Office is installed

To uninstall, click the same profile and click “Remove”. The profile will be removed and Office will be uninstalled.

Deploy “Light” Office via Software Distribution

This is essentially the same thing as using the CSP but you deploy it as an “app” instead of profile. This gives you the benefits of Software Distribution, such as better reporting, availability in the Catalog, and integration with Workspace ONE Intelligence. Note that this process still uses the Microsoft CDN to download the Office bits during the install. Let’s walk through how to package this up.

First, download and run the Office Deployment Tool. Select the folder where you want the extracted files to go. I usually put them in C:\Office.

This will put a few sample xml files as well as setup.exe. Setup.exe is the main file we need.

Create a new folder (or use this one) and put the following files:

  • Setup.exe
  • Configuration.xml
  • Uninstall.xml

Select those files, right click, and click Send To > Compressed Folder (zip)

Make sure you select files and THEN add to zip. Don’t select parent folder and send to zip as you’ll create a sub-folder underneath.

I like to rename the zip file “Office.zip”

Next, we’re going to create the app in Workspace ONE. Go to Apps & Books in the Workspace ONE console and click Add Application.

Change the name of the app to be something useful like “Office 365 ProPlus x64 (light)”. I also like to put my name in “Change log” area along with the date so that other admins know who made this app and when.

Go to the Files tab, scroll to the bottom and for the “Uninstall Command” fill in: setup.exe /configure uninstall.xml

setup.exe /configure uninstall.xml

Go to “Deployment Options” tab. In the “How to Install” section, select Device or User depending on what you want. Selecting User WILL show the install UI if you have it configured in the XML. If you don’t care about that simply use Device.

For “Install Command”, put setup.exe /configure configuration.xml. Adjust other fields as necessary.

setup.exe /configure configuration.xml

Under “Identify Application By”, select “Defining Criteria” and click “Add”. Usually I keep things simple and just put “File exists”, “C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE”

Put C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE. No quotes necessary.

Note that if you deploy 32bit Office to 64bit Windows, then you’d want to put: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE

If you want it to look pretty in the console and the catalog, find a cool png logo and add it on the Images tab > Icon.

Save and Assign to your Assignment Groups. Go to a device > Apps tab and find Office 365 ProPlus x64 (light).

Click radio button and then “Install”

On the client, I can load up the registry and look at the Software Distribution queue to see that it is in progress. Additionally, I can look at the AppDeploymentCache folder and can see the app successfully exported the zip.

Loading Task Manager I can see the app is installing

Deploy Full Office via Software Distribution

This process is nearly identical as the “light” version except that you will need to pre-download the full Office content before zipping. Choose this method if you want to fully leverage the Akamai CDN (as opposed to MS’s) and also want to use it for Dell Provisioning for Workspace ONE (which requires offline install).

Load up an elevated CMD window and then change directory to C:\Office. Run the following command: setup.exe /download configuration.xml.

This will then cause all of the files to download into a subfolder (also called Office)

If you want to make a batch file where you can re-do this again later one you can use this code.

@echo off
pushd %~dp0
echo Downloading Office 365 Pro Plus Retail x64 source files
setup.exe /download configuration.xml

When you use this method, Office will install the version that is downloaded at the time it is downloaded. So this will be something that you are going to need to keep up to date over time. Now, simply follow the process as detailed in the Office “light” section for zipping and uploading the app to the Workspace ONE console. Be patient as uploading a 3gb Office app to the Workspace ONE console can take some time.

Other Tidbits

  • Don’t forget you can make xmls for Project and Visio installs and repeat the processes above to create those deployments.
  • If this is your first time deploying Office, it’s always a good idea to test out the install manually first on a VM with display level set to Full. This will show you the install progress and an errors that may popup. If it doesn’t deploy manually, it won’t deploy via one of the above methods.
  • Office does need a minimum free disk space to install so if you are getting weird failures, check free disk space (needs minimum 4GB of free space).
  • You can’t mix and match architecture types. You can’t have the core Office install be 32 bit and attempt to deploy 64bit Visio (and vice versa).
  • This page has some more useful info on troubleshooting any install failures
  • If you are curious on what is the difference between Office 365 ProPlus and Office 2019, you can check out this MS page

Summary

I’ve highlight 3 of the best ways to deploy Office 365 Pro Plus with Workspace ONE. You can use the Office CSP which enables you to simply deploy the configuration without having to fuss with files or content. The “light” Office installer method is is simple to configure and gives you the benefits of being a managed App in the console, but still requires an internet connection during client install. The “full” Office installer method requires you to pre-download all of the files ahead of time and then upload as a zip to Workspace ONE. Since this can be installed fully offline, it can be exported as PPKG and sent to Dell in the factory as part of the Dell Provisioning for Workspace ONE services. There is lots of flexibility here so choose the method that works best for you!

This Post Has 11 Comments

  1. Hassan

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

    1. Brooks Peppin

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

  2. Jon Towles

    Why would you do CSP instead of just zipping the setup.exe and configuration.xml like you do with SCCM and deploying it.

    I don’t see much value in using CSP over the standard ODT method.

    1. Brooks Peppin

      The CSP method is just one of the methods I detail. Main benefit I guess is that you don’t have to mess with any content at all, it’s just the config. Zipping up the content and deploying it is method #2 I discuss.

  3. Kurt

    Hey Brooks,
    Are there any good troubleshooting steps? We get the profile to install but the apps dont come down. These machines are co managed and then clean – meaning just enrolled in UEM

  4. Yasmin

    Thanks I am a mother and very busy! This helped me alot!

  5. Joël Brunner

    Dear Brooks,
    Really, really cool guide. Helped me a lot during preparation of the wsONE App and the golden image for factory provisioning. Thanks for sharing this.
    Keep up the good work!

    1. Brooks Peppin

      Thank you! Glad it helped.

  6. stahlbau

    Hello! Do you use Twitter? I’d like to follow you if that would be ok.
    I’m definitely enjoying your blog and look forward to new posts.

    1. Brooks Peppin

      Yes! @brookspeppin is my handle.

  7. Phil

    Thanks for the update Brooks

Leave a Reply