Deploying Traditional Win32 Applications to Windows Devices: Workspace ONE Operational Tutorial

VMware Workspace ONE UEM 2011 and later

Overview

Introduction

Note: This content was created for Windows 10, but the basic principles and tasks outlined also apply to your deployment of Windows 11.

VMware provides this operational tutorial to help you with your VMware Workspace ONE® environment. This tutorial shows you how to use Workspace ONE UEM to manage Windows 10 applications through a series of exercises including managing Win32 apps, deploying Microsoft Office 365 ProPlus, the Workspace ONE applications, and reviewing additional application file samples.

This tutorial was written using Workspace ONE UEM version 2011. The version of Workspace ONE UEM you are using might be different. 

See the Workspace ONE UEM Release Notes for feature updates to the Workspace ONE UEM admin console.

Audience

This operational tutorial is intended for IT professionals and Workspace ONE UEM administrators of existing production environments.

Knowledge of additional technologies such as network, VPN configuration,  VMware Workspace ONE® Intelligence and VMware Workspace ONE® UEM is also helpful.

Getting Started with Windows 10 Software Distribution

Windows 10 Application Management Overview


Workspace ONE application export

As an organization expands and evolves, application delivery overheads increase on IT teams. You must ensure that application delivery is available anytime, while simultaneously ensuring that you are ready to deliver different types of applications, including local apps, hosted apps, SaaS apps, classic apps, or cloud apps.

Workspace ONE UEM Windows 10 Application Types

With Workspace ONE, almost any type of app can be delivered to Windows 10 devices. Use Workspace ONE UEM to push Windows public and internal applications, web apps, and SaaS applications to Windows desktop devices.

  • Universal applications
  • Cloud-based applications 
  • Hosted or remote applications 
    • Windows 10 can also remotely connect to published Remote Desktop Server Hosted (RDSH) applications residing on Horizon, XenApp, or Terminal Services servers. Many clients will continue to use older releases of Windows while they test Windows 10 on devices by configuring Windows 10 devices to access VDI-based desktops running legacy Windows (XP, 7, 8) images.
    • For more information, see VMware Docs: Setting Up Resources in Workspace ONE Access.
  • Classic Windows applications 
    • Classic Windows applications (Win32 and Win64) constitute the majority of the application portfolio that can easily migrate to Windows 10. Classic Windows applications are installed using EXEs, MSIs, batch files, and scripts.
    • This tutorial will focus on Classic Windows applications.

Importing Applications using Workspace ONE AirLift

VMware Workspace ONE® AirLiftTM is a tool that simplifies the transition from traditional PC lifecycle management to modern management with Workspace ONE UEM.

  • Workspace ONE AirLift communicates with Microsoft Active Directory for group policy rationalization and migration to modern management.
  • Workspace ONE AirLift can also interact with Microsoft Endpoint Configuration Manager (ConfigMgr) for application rationalization and migration to Workspace ONE UEM.

For more information on how to import applications from ConfigMgr (SCCM) to Workspace ONE UEM, see Modernizing Windows 10 Management: VMware Workspace ONE Operational Tutorial.

Importing Applications using Flexera AdminStudio

Flexera AdminStudio has integrated with Workspace ONE UEM for application distribution since late 2018. You can leverage their AdminStudio Catalog and export apps to Workspace ONE UEM for deployment. You can avoid repackaging apps manually and therefore save time.

For more information, see:

Software Delivery Architecture

The Workspace ONE UEM software delivery architecture is backed by a content delivery network (CDN) and peer-to-peer (P2P) technology integration.

This means that end users can get their applications installed, no matter where they are, at home or in the office, thus removing the need for complex and unnecessary infrastructure.

Software Delivery Architecture Diagram

 Software Delivery Architecture Diagram

This diagram illustrates a high-level overview of the Workspace ONE UEM architecture components.

  1. The application is configured in Workspace ONE UEM.
    • The application can be uploaded and configured manually in Workspace ONE UEM admin console, imported by Workspace ONE AirLift, using the Workspace ONE Enterprise Application Repository or Flexera AdminStudio.
  2. Workspace ONE UEM requests to install application on the device.
    • The end user can install the application from the Workspace ONE Intelligent Hub, or an administrator can silently install an application from Workspace ONE UEM.
  3. Device reaches out to peers or host for cache if configured.
    • If configured, the device can use peer-to-peer (P2P) technologies such as Adaptiva or Workspace ONE Peer Distribution. This information lives in the content manifest of the application.
  4. Device reaches out to CDN if Peer Distribution is not configured.
    • Workspace ONE uses an Akamai CDN to ensure that the applications can be installed from anywhere.
  5. Fallback to Device Services Server to obtain application if no CDN is configured.
    • By default, if the device cannot download application files from its peers or a CDN, it will fall back to the Workspace ONE UEM Device Services server.

Integrating Workspace ONE UEM with Content Delivery Network

Workspace ONE UEM SaaS environments are integrated with Akamai's CDN network by default.

On-premises customers can take advantage of this functionality by obtaining Akamai's CDN capabilities. 

A content delivery network (CDN) is a highly distributed platform of servers that responds directly to the end-user requests for the web content. Content delivery network acts as an intermediary between the Workspace ONE UEM servers and the end-user devices to mitigate the challenges of delivering the content over the Internet.

For more information, see VMware Docs : Integrate Workspace ONE UEM with Akamai CDN.

Peer-to-Peer Distribution for Windows 10

Workspace ONE UEM offers the peer distribution system as another method to deploy your Windows applications to enterprise networks. Peer distribution reduces the time to download large applications to multiple devices in deployments that use a branch office structure. Workspace ONE UEM offers two types of peer-to-peer options.

You can either use the Workspace ONE peer distribution or a peer distribution that partners with Adaptiva.

Benefits of using Peer-to-Peer Software Distribution

The peer distribution system benefits environments with specific characteristics, such as:

  • Offices in remote locations with low bandwidth.
  • Offices that have a higher latency against the content delivery network (CDN) and Device Services server.
  • Enterprises that use branch office hierarchies.
  • Enterprises that have multiple branch offices with many devices.

For more information, see VMware Docs: Introduction to Peer-to-Peer Distribution for Windows 10.

Increasing File Storage and Enabling Software Distribution

This section covers various options to increase file storage and how to enable software distribution.

File Storage for Workspace ONE UEM

Workspace ONE UEM functionality uses a dedicated file storage service to handle processing and downloads, which reduces the overall burden on your Workspace ONE UEM database and increases its performance. Configuring file storage manually is only applicable to on-premises customers. It is automatically configured for SaaS customers.

Effective December 1, 2020, the default storage capacity for Workspace ONE Advanced, Workspace ONE Enterprise, Workspace ONE Enterprise for VDI, and Workspace ONE Modern Management Essentials licenses will increase from 50 GB to 500 GB.

For details, see VMware Knowledge Base article: Workspace ONE Storage Pricing and Packaging Updates (81399).

Increase Storage Size for Workspace ONE UEM Cloud

Depending on the edition of Workspace ONE, your storage will either be 25 GB, 50 GB, or 500 GB by default. Additional storage can be purchased for Workspace ONE UEM SaaS environments. 

Contact your VMware account representative for additional storage.

Enable File Storage for Workspace ONE UEM On-Prem

Configure file storage for Windows applications with the following settings. This is required if you are deploying Win32 apps using software distribution, but applies to all internal applications after they are configured.

Ensure that all prerequisites are met. For details, see VMware Docs: Configure File Storage for your internal Win32 Applications.

Note: You must log in to the Workspace ONE UEM admin console at the Global level and have the correct admin permissions. If your admin account does not have the right permissions, you will not see the Installation option in the settings.

 Storage for Workspace ONE UEM On-Prem
  1. In the Workspace ONE UEM console, navigate to Settings > All Settings and select the Installation tab.
  2. Select File Path.
  3. Scroll down to the bottom of the page.
  4. Ensure that File Storage Enabled is set to Enabled.
  5. Enter the File Storage Path in the following format: \\{Server Name}\{Folder Name}, where Folder Name is the name of the shared folder you create on the server.
  6. Select File Storage Impersonation Enabled and enter the File Storage Impersonation Username and Password.
  7. Click Test Connection to test the configuration.
  8. After the test is successful, click Save.

Increase Default Storage Size for Workspace ONE UEM On-Premises

Your specific storage requirements can vary depending on how you plan to use file storage. The file storage location must have enough space to accommodate the internal applications, managed content, or reports you intend to use.

By default the storage in Workspace ONE UEM can be 25 GB. To increase the default size, follow the next steps.

Note: You must log in to the Workspace ONE UEM admin console at the Global level and have the correct admin permissions. If your admin account does not have the right permissions, you will not see the Installation option in the settings.

 Increasing Default Storage Size for Workspace ONE UEM On-Prem
  1. In the Workspace ONE UEM console, navigate to Settings > All Settings and select the Admin tab.
  2. Select Storage to configure the file server.
  3. To edit a specific Organizational Group setting, select the edit arrow for that Organizational Group.
  4. To edit the Default Settings, click Edit Defaults.
 Increasing Default Storage Size for Workspace ONE UEM On-Prem

After the edit option has been selected:

  1. Ensure that the Inherit or Override settings are correct. You must Override these settings if changed at an Organizational Group level.
  2. Under Apps and Books, change the Capacity of applications. Enter this value in MB.
    • This is the total file storage for applications.
  3. Under Apps and Books, change the Maximum File Size of Applications. Enter this value in MB.
    • This is the maximum file size for an application to be uploaded.

Enable Software Package Deployment for Workspace ONE UEM

Configure Workspace ONE UEM to recognize the deployment of Win32 applications through the software distribution method.

For Workspace ONE UEM SaaS customers, this is done automatically for you. Follow the next steps to confirm this option is enabled.

For  Workspace ONE UEM on-premises customers, follow the next steps.

Enable Software Package Deployment for Workspace ONE UEM On-Premises

 Enabling Software Distribution for Workspace ONE UEM On-Prem

Note: You must log in to the Workspace ONE UEM admin console with the correct admin permissions. If your admin account does not have the correct permissions, you will not see the App Deployments option in the settings. This applies only to on-premises environments.

In the Workspace ONE UEM admin console:

  1. Navigate to Groups & Settings > All Settings > Device & Users > Windows > Windows Desktop > App Deployments.
  2. Select Override.
  3. Ensure that Software Package Deployment is Enabled.
  4. Select Save.

Confirm that Software Package Deployment is Enabled for Workspace ONE UEM Cloud

If Software Package Deployment has not been enabled, when uploading applications, you will not see the Deployment Options tab. The Deployment Options tab will only display after the Software Package Deployment feature has been enabled.

 Confirming Software Package Deployment Enabled for Workspace ONE UEM Cloud
  1. The Deployment Options tab is displayed if Software Package Deployment is Enabled.
  2. Software Package Deployment is Disabled so the Deployment Options tab is not shown.

The following screenshot depicts an example of the application Details screen when Software Package Deployment is disabled.

 Confirming Software Package Deployment Enabled for Workspace ONE UEM Cloud
  1. When Software Package Deployment is disabled, under the Details tab, you can see the Installer Package Deployment option. This is where you enter the command line options for the MSI installation process.

Creating Application Assignment Groups

Assignment groups consist of elements such as organization groups, smart groups, and user groups and can be used to assign applications to user devices. Assignment groups enable an administrator to manage these three grouping structures from a single location. For Windows 10 devices, assignment groups can also contain the make and model of the Windows device.

Workspace ONE Smart Group Creation

In the Workspace ONE UEM admin console, navigate to Groups & Settings > Groups > Assignment Groups and click Create Smart Group.

To select the make and model of a device:

  1. Select Windows Desktop under Platform and Operating System.
  2. Select OEM Make and Model.
  3. Select OEM, for example, Dell Inc.
  4. Select Model of the machine.
  5. Select Enabled for Device Preview to show a list of enrolled devices that meet this criteria.  
  6. Click Save.

Setting Up the Application Terms Of Use

You can create application-based terms of use (ToU) to notify end users when a specific application collects data, when it imposes restrictions to the machine, or when it needs network access to the corporate network for example.

When users install applications that require ToU from your enterprise app catalog, they must accept the agreement to access the application.

You can set ToU for app versions, make language-specific ToU, and remove apps if the ToU is not accepted.

Configure Terms Of Use for Applications

During the application configuration, you can add the Terms of Use for the application.

 Configuring Terms Of Use

When editing the Application Deployment configurations:

  1. Select the Terms Of Use tab.
  2. Select terms of use from the drop-down menu.
  3. If no Terms of Use are set up, click Manage Terms Of Use. This will automatically open the Terms of Use page in the next step.

Create Applications Terms Of Use

 Adding Terms Of Use

In the Workspace ONE UEM Console, navigate to Settings > All Settings.

  1. Select System.
  2. Select Terms Of Use.
  3. Click Add Terms Of Use.
 Adding Terms Of Use
  1. Enter a Name for the Terms of Use, for example, Application Terms of Use.
  2. For Type, select Application.
  3. Enter the Grace Period for acceptance in day(s).
  4. Add Terms Of Use in the text box.
  5. Click Save.

Review the Applications Terms Of Use

 Adding Terms Of Use
  1. Select the Terms Of Use tab.
  2. Click the drop-down menu to select the Terms of Use.
  3. Select the Terms Of Use you want to apply to the application.

Note: It is best practice to have the terms of use configured before you add any applications. If you add an application and then select Manage Terms of Use, you will be taken to away from the application deployment configuration page to Create a Terms of Use.

If Terms Of Use does not show in the drop-down menu, ensure that the Terms Of Use has been created and saved, and refresh your browser.

Understanding application configuration options and types

Understanding Application Installation Behavior

When deploying numerous apps to end-user devices, it can take some time to install all the device applications. After device on-boarding completes, apps queue up for the device to install per Windows operating system specifications, configured timeout values and retry logic. Dependency files are installed prior to the main application.

Installation Behavior Variables

A few variables impact the way applications distributed from the Workspace ONE UEM Console install on devices.

  • Context - Applications can install to the device or the user context.
  • Privileges - Applications may allow user privileges or require administrative privileges.
  • User Type - Users can have either admin or standard permissions.

The following table outlines how these variables impact installation behavior.

Workspace ONE UEM Settings Windows 10 Device Behaviour
Install Context Settings In the Workspace ONE UEM console
Install with Admin Privileges in the Workspace ONE UEM console
End User Type
Installation Behavior
Device Yes Admin User The installation completes without prompt
Standard User The installation completes without prompt
No Admin User The installation completes without prompt
Standard User The installation completes without prompt
User
Yes Admin User The installation completes without prompt
Standard User
The installation completes without prompt
No Admin User
The installation completes with prompt
Standard User
The installation completes without prompt

Application Sampling Schedule

The Applications sampling is performed by the Intelligent Hub on the Windows 10 device.

1. Review the Intelligent Hub Data Sample Interval

Configure the Workspace ONE Intelligent Hub settings so that the Workspace ONE Intelligent Hub transmits the required data to the Workspace ONE UEM Console. To find the Windows Intelligent Hub sample interval, in the Workspace ONE UEM console:

  1. Navigate to Settings > All Settings > Devices & Users > Windows > Windows Desktop > Intelligent Hub Settings.
  2. Review the Data Sample Interval. Note: We do not recommend changing this from the default setting.

2. Review Device Last Scan Schedule

When reviewing the Devices details tabs, you can see when the latest information was received from the device.

  1. Select Apps.
  2. Review the Last Scan data.
  3. To refresh the data, click Query; this will query the device for the latest data.

3. Query Device for Information

  1. Click More Actions.
  2. Select the appropriate category to query.

4. Confirm Device Query

After a device query command has been sent, on the device details screen:

  1. Navigate to the Troubleshooting.
  2. Select Commands.
  3. Review any pending commands to the device. In this example, we are waiting on the app list sample to return.
  4. After the commands have been processed, they will appear in the Event Log section.

Retrieving Application Installation/Uninstall Parameters

There are a few of ways to get the installation/uninstall data. Note that every app can be different.

The following is a quick summary of ways to get the install and uninstall commands. The rest of this section will expand points 2, 3, and 4.


  1. The application vendors documentation.
    • A good practice is to always refer to the vendors documentation on how to install the application. Generally speaking, the command lines that are used for ConfigMgr (SCCM) can be used for Workspace ONE UEM because they are standard msiexec commands.
  2. Retrieve install commands using the Windows command line.
    • In a command-line session, enter setup.exe /?. If the EXE contains an underlying MSI, use the msiexec uninstall command: msiexec /x setup.exe.
    • A list of standard command line options can be found in Microsoft Docs: Command-Line Options.
  3. Retrieve uninstall command using the device registry settings.
    1. Install the app on a reference device.
    2. When installation completes, look at the HKEYs on the device’s listed registries.
      • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall
      • HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\
      • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall
      • HKCU\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\
  4. Retrieve application GUID with gwmi win32_product.
    • Open PowerShell and run gwmi win32_product to find the applications IdentifyingNumber.

1. Retrieve Install Commands Using Windows Command Line

In this example, we use the Horizon Client to get the installation parameters.

 Retrieve uninstall command via the Command Line

Select the application that you want to install. Select the application install file then:

  1. Hold SHIFT and while you right-click,
  2. Select Copy as Path.

You can also drag the file into a command prompt session.

 Retrieve uninstall command via the Command Line
  1. Open Command Prompt as admin and paste the copied path.
  2. Append /? or /help to the end and press the Enter key.
 Retrieve uninstall command via the Command Line
  1. The application should give you a list of supported command line properties for installing and uninstalling the application.
  2. Depending on the application, you might have some custom properties to configure the application.

2. Retrieve Uninstall Command Using The Device Registry Settings

 Retrieve uninstall command via the The Device Registry Settings

Using one of the Registry locations listed in the introduction, find the application.

  1. Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall.
  2. Find the Application GUID.
  3. To find the correct application GUID, check the DisplayName value.
  4. Find UninstallString and double-click it.
  5. This displays the uninstall parameters you can use for the application.

In this example, the silent uninstall is:

 "%SystemRoot%\System32\msiexec.exe" /X {73499771-35D2-4F4E-AC1B-8417816D6F6A} /qn

3. Retrieve Application GUID with gwmi win32_product

In this example, the VMware Horizon Client is installed on a reference machine and we will run the gwmi win32_product command to obtain the ApplicationIdentifier.

Retrieve Application GUID with gwmi win32_product

On a Windows computer with the application already installed, open PowerShell as admin and run gwmi win32_product.

  1. Find the Application.
  2. You can find the Application by checking the Application Name value or the Application Caption value.
  3. Note the IdenifyingNumber value.

In this example, the silent uninstall command is:

 "%SystemRoot%\System32\msiexec.exe" /X {73499771-35D2-4F4E-AC1B-8417816D6F6A} /qn

How To Get the Exit Code

In this exercise, determine the exit codes you might use if you select Using Custom Script on the Deployment Options tab.

Use the environmental variable %errorlevel% to get exit codes. Use it in conjunction with built-in DOS commands like ECHO, IF, and SET to preserve the existing %errorlevel% value.

  1. In a command-line session, run the install command for the Win32 application.
  2. Run ECHO %errorlevel%.
  3. If the Win32 application requires a reboot for installation, the variable returns the reboot exit code.

Working with ZIP/EXE Files

If you are using a ZIP file, compress application packages that are 4 GB or larger using 7-Zip. Workspace ONE UEM does not decompress ZIP packages containing application packages of 4 GB or larger when compressed using the native Windows ZIP compressor.

1. Create Zip package - Example Office 365 (Online Installer)

In this example, we create a ZIP file for Office 365 deployment. We use the native Windows compressor because the file is less than 4 GB (online installer version).

Create Office Zip package
  1. Select the individual files you want to place in the ZIP.  In this example, we select: 
    • Configuration.xml
    • uninstall.xml
    • setup.exe
  2. Send the files to a ZIP folder. 
  3. Name the file, for example, Office.

Tip: Make sure you select the individual files and then add to ZIP. Do not put all the files in one folder and ZIP that one folder.

Note: If you use Office 365 Offline Installer—for example for use with Workspace ONE Factory Provisioning—if the files are over 4 GB, use 7-Zip to compress the files.

Working with MST and MSPs

Uploading applications into Workspace ONE UEM

Prerequisites

In this section of the tutorial, we will delve deeper into the configuration options for Win32 application distribution available in Workspace ONE UEM.

Important: The information in this tutorial is based on a Workspace ONE UEM 2011 environment. Depending on your version of UEM, your configuration options might differ.

Confirm Checklist

Before you can perform the steps in this exercise, you must satisfy the following requirements:

  • Ensure that Software Distribution is enabled (for apps other than MSIs).
  • Ensure that you have enough storage space to upload applications.
  • Set up integration with CDN (for on-premises).
  • Select apps for Applications Distribution (peer-to-peer method).

Uploading Application Files

In this exercise, we upload the application files into Workspace ONE UEM and modify some of the configurations for deployment.

1. Add Internal Application File

 In the Workspace ONE UEM Admin Console

In the Workspace ONE UEM admin console, navigate to Resources > Apps > Native.

  1. Select Internal.
  2. Click Add.
  3. Select Application File.

2. Configure Add Application

 Add Application
  1. Click Upload to select the file.

Supported File Types

  • MSI
  • EXE
  • ZIP
  • Note: If you are using a ZIP file, compress application packages that are 4 GB or larger using 7-Zip. Workspace ONE UEM does not decompress ZIP packages containing application packages of 4 GB or larger when compressed using the native Windows zip compressor.
  • See Create Zip package - Example Office.

3. Select Application File

 Upload Application File
  1. Select type Local File.
  2. Click Choose file and browse to choose the file.
  3. Indicates how much storage you have used.
  4. Indicates the amount of storage you have available.

Note: The maximum file upload size is 200 MB by default. To increase this, contact your VMware representative. See How to Increase File Storage and Enable Software Distribution for more information.

4. Select If App Is a Dependency

 Select if App is a dependency
  1. Select if file is a dependency application.
    • Examples of dependency applications are libraries and frameworks.
  2. Click Continue
    • This will take you to the Application Details for configuration.

Configuring the Application Details Tab

The Details tab configures and sets details of the application that an end user will see in their Workspace ONE Intelligent Hub application catalog.

Configure the Application Details

 Configuring the Application Details
  1. Enter a Name - This is the name that users will see in the Intelligent Hub.
  2. Configure/View any other details such as:
    • Managed By
    • Application ID
    • Actual File Version
    • Build Version
    • Version
    • Supported Processor Architecture
    • Is Beta    
    • Change Log
  3. Scroll Down.
 Configuring the Application Details
  1. Configure any additional fields such as:
    • Categories
    • Minimum OS
    • Supported Models
    • Default Scheme
    • Description
    • Keywords
    • URL
    • Support Email
    • Support Phone
  2. Scroll Down.
 Configuring the Application Details
  1. Configure any additional fields such as:
    • Internal ID
    • Copyright
    • Developer Information
      • Developer
      • Developer email
      • Developer Phone
    • Application Cost Information
      • Cost Center
      • Cost
      • Currency

Application View in End Users Catalog

 Application view in End Users Catalog

This is the end users view of the application in the Workspace ONE Intelligent Hub. This image depicts the Intelligent Hub 2010 release.

Configuring the Application Files Tab

The Applications Files tab shows the application file and allows administrators to configure any additional files such as MSP, MST, and Uninstall Commands.

Confirm Application Files Name

 Application Files Overview
  1. Select Files.
  2. Note the Application File name - This is in handy if you need it for the install command.

Configure App Dependencies

Dependency files in the software distribution are applications that are necessary for a Win32 application to function. Examples include framework packages and libraries. Although you upload them like a file and you can view them in the List View, they have reduced features.

Select the App Dependency

 Selecting the App Dependency
  1. Click inside the Select Dependent Applications search box.
  2. Select the application dependency.
    • Note: For a dependency to appear, you must upload the installer files in Workspace ONE UEM as a dependency file.

Review the Application Dependency

 Reviewing the Application Dependency
  1. Review all application dependencies.

Ensure that the dependencies are listed in the correct order to be installed. The system works from top to bottom.

For more information, see VMware Docs: Working with Win32 App Dependency Files

Configure App Transforms

An MST file or transform file, is a settings file used by the Microsoft Windows Installer (msiexec.exe), a component of the Windows operating system that enables software installations. A transform is a collection of changes applied to an installation. By applying a transform to a base installation package, the installer can add or replace data in the installation database. The installer can only apply transforms during an installation.

MST files are used in conjunction with Microsoft Windows installer packages (MSI files). Their settings can be included with an installation package at the command line using the following syntax:

installer.msi TRANSFORMS=transforms.mst 

Note: Workspace ONE MST files are adding during assignment of the application. There is no need to add them in the install command.

For more information on Transform files, see Microsoft Docs: About Transforms.

Add App Transforms

 Adding App Transforms
  1. Click Add and add MST files.

1. Deliver App Transforms

  1. When assigning the application, you can select the Application Transform to apply.
    • This means you can apply different transforms to different device/user groups.
    • If the transform file selection is changed after the app is installed, the update does not get applied on the devices. Only the newly added devices which do not have the app installed receives the updated transform.

Configure App Patches

A Windows Installer patch (.msp file) is a file used to deliver updates to Windows Installer applications. The patch is a self-contained package that contains all the information required to update the application. A patch package (.msp file) can be much smaller than the Windows Installer package (.msi file) for the entire updated application. For more information about delivering smaller updates to applications, see Reducing Patch Size.

Source: Microsoft Docs: Patch Packages

*.msp files can be:

  1. Cumulative Patches - 
    • If your patch file is inclusive of all the changes from previous patches.
  2. Additive Patches
    • If your patch file is not inclusive of all the changes from previous patches and if the patch file has to be applied in addition to previous patch files.

Add Application Patches - MSP Files

 App Patches
  1. Click Add.
 App Patches
  1. Adding Cumulative Patches
    • If your patch file is inclusive of all the changes from previous patches.
  2. Adding Additive Patches
    • If your patch file is not inclusive of all the changes from previous patches and if the patch file has to be applied in addition to previous patch files.
  3. Click Choose File. Browse to upload the patch file.
  4. Click Save.

Review Application Patches - MSP Files

 Reviewing Application Patches - MSP Files

In this example, we have uploaded 2 files. One file called MSP Example 1 and the other is MSP Example 2. Notice that MSP Example 1.msp is marked as a Cumulative Patch and MSP Example 2.msp as an Additive Patch.

Configure App Uninstall Process

These scripts instruct the system to uninstall an application under specific circumstances. MSI installers will use their uninstall command. For ZIP and EXE files, you must add in how the application uninstalls. Customized scripts are optional for MSI files.

1. Custom Script Type - Input

 App Uninstall Process
  1. Select Use Custom Script for MSI.
  2. Select Custom Script Type - Input.
  3. Enter the Uninstall command.

Note: MSI apps are uninstalled by product code. You must add uninstall criteria for scripted installs (ZIP files and EXE files).

Custom Script Type - Upload

 Custom Script Type - Upload

You can also uninstall apps by uploading custom scripts. For ZIP file scripted installers, if multiple applications are installed, then you add a custom uninstall script.

  1. Select Upload.
  2. To upload the script, click Upload.

Allowed scripts and file extensions are:

  1. Javascript : *.js, *.jse
  2. Powershell : *.ps1, *.ps1xml, *.psc1, *.psd1, *.psm1, *.pssc, *.cdxml
  3. VBScript : *.vbs, *.vbe, *.wsf, *.wsc

Configuring Application Deployment Options Tab

In this section, we configure the installation parameters in Workspace ONE UEM to install applications.

1. Configure When To Install

 When to Install

The When To Install section instructs the system to install the application with specific criteria. The system can parse information for MSI files. However, for EXE and ZIP files, the system requires you to enter this information.

Configure any minimum requirements for the following:

  1. Ensure you are on the Deployment options tab.
  2. Data Contingencies - Use where criteria type needs to check for existing/non-existing Applications, Files, or Registry Keys.
    • For more information on Data Contingencies see Configuring Data Contingencies.
  3. Disk Space Required - Which specifies the amount of disk space the device must have available to install the application.
  4. Device Power Required - Which specifies the battery power, in percentage, that the device must have to install the application.
  5. RAM Required - Which specifies the amount of RAM the device must have to install the application.

1.1. Configuring Data Contingencies

Set contingencies for instruction and completion scenarios.

  • Instruction – Contingencies instruct the system to install applications when the device meets specific criteria.
  • Completion – Contingencies identify when an installation is complete.

1.1.1. Criteria Type - App exists/App does not exist

 Criteria Type - App Exists/App does not exist

Workspace ONE UEM checks for the existence of the application but it does not deploy the application to devices.

  1. Criteria Type
    • App Exists.
    • App does not exist.
  2. Application Identifier
    • Enter the application identifier so the system can recognize the existence or non-existence of the auxiliary application. This value is also known as the product code of the application.
  3. Version
    • Enter the specific version.

1.1.2. Criteria Type - File exists/File does not exist

 Criteria Type - File Exists/File does not exist

Configure the system to install the application when a specific file is or is not on devices.

  1. Criteria Type
    • File exists.
    • File does not exist.
  2. Path
    • Enter the path on the device where you want the system to look for the file and include the filename.
  3. Version
    • Enter the specific version.
  4. Modified On
    • Enter the date the file was last modified

1.1.3. Criteria Type - Registry exists/Registry does not exist

 Criteria Type - Registry Exists/Registry does not exist

Configure the system to install the application when a specific registry is or is not on devices.

  1. Criteria Type
    • Registry exists.
    • Registry does not exist.
  2. Path
    • Enter the path on the device where the system can find the keys and values. Include the entire path, beginning with HKLM\ or HKCU\.
    • For example, HKLM\Software\.. or HKCU\Software\.. or HKEY_LOCAL_MACHINE\Software.. or HKEY_CURRENT_USER\Software..
    • Enter the registry path using the abbreviated or complete name for the top level registry hive.
  3. Configure Registry Values
    • Leave this deselected to verify only the existence of path.
  4. Value Name
    • Enter the name of the key. This container object stores the value and it displays in the file structure of the device.
  5. Value Type
    • Select the type of key displayed in the file structure of the device. Value types can be
      • String
      • DWORD (32 Bit)
      • QWORD (64 Bit)
      • Multi-String
      • Expandable String
  6. Configure Registry Data
    • Select to check for a specific registry value.
  7. Value Data
    • Enter the value of key. The name-data pairs stored in the key display in the file structure of the device.

1.1.4. Add Additional Data Contingencies

 Adding additional Data Contingencies
  1. Click Add to add additional dependencies.
  2. Select the drop-down menu to change the data contingencies operator to AND or OR.

2. How To Install

 How To Install
  1. Install Context - Select how the system applies the installation.
    • DEVICE - Define the installation by the device and all the users of that device.
    • USER - Define the installation by particular user accounts (enrolled).
  2. Install Command - Enter a command to control the installation of the application.
    • MSI- The system automatically populates the installation commands, and the commands include patches and transforms.
    • Patches (MSP) To update the order in which the patches install on devices, update their listed order in the install command.
    • Transforms (MST) The order in which the system applies transforms is set when you assign the application. You see a placeholder name for the transform until you associate the transform during the assignment process.
    • EXE and ZIP- Populate the install command and specify the patch names and their order of application in the command. You must also enter the install command that triggers the installation of the Win32 application.
    • If you do not package the patches and transforms in the EXE or ZIP file and you add them separately, ensure to add the patch filenames and the transform lookup text boxes in the install command.
  3. Admin Privileges -Set the installation to bypass admin privilege requirements.
  4. Device Restart 
    • Do not restart - If you choose not to restart.
    • Force restart - Force the device to restart.
    • User-engaged restart - Options for Win32 applications allow the user to defer the device reboot for "x" days with a maximum limit of 7 days.
  5. Retry Count - Enter the number of times the system attempts to install the application after an unsuccessful attempt.
  6. Retry Interval - Enter the time, in minutes, the system waits before it tries to install the application after an unsuccessful attempt.
  7. Install Timeout - Enter the maximum time, in minutes, the system allows the installation process to run without success.
  8. Installer Reboot Exit Code - Enter the code the installer outputs to identify a reboot action.
  9. Installer Success Exit Code - Enter the code the installer outputs to identify a successful installation.

3. Configure When To Call Install Complete Options

Configure Workspace ONE UEM to identify the successful installation of Win32 applications. The system requires this information for EXE and ZIP files.

3.1. Identify Application By Defining Criteria

 Identify Application By Defining Criteria
  1. Select Defining Criteria.
  2. Click Add to add criteria.
    • Criteria can include data such as:
      • App Exists
      • App does not exist
      • File exists
      • File does not exist
      • Registry Exists
      • Registry does not Exist

For more information on configuring this data, see Configuring Data Contingencies.

3.2. Identify Application By Using Custom Script

 Identify Application By Using Custom Script
  1. For Identify Application By, select Using Custom Script.
  2. Script Types supported are:
    • JScript 
    • PowerShell 
    • VBScript 
  3. Enter the Command to Run the Script.
  4. Click Upload to upload the Custom Script File.
  5. Success Exit Code - Enter the code that the script outputs to identify the successful installation.
  1. After an application has been deployed, you can edit When to Call Install Complete.
    • Enter the Admin PIN to complete the action. If you change the criteria to a value that is invalid, the app will be removed from all the systems where it is deployed. Be cautious when editing the When To Call Installation Complete criteria.

Adding Images to Applications Tab

You can add images to  Windows applications to achieve the same look and feel as a traditional app store.

Allowed file types are: JPG, JPEG, PNG, GIF, BMP.

1. Add Images to Applications

 Adding Images to Applications
  1. Navigate to the Images tab.
  2. Select Mobile Images.
    • Add any images here for mobile devices
  3. Select Tablet Images.
    • Add any image here for tablet devices
  4. Select Icon.
    • Add the icon here. PNG is best, especially if you customize the branding of your application catalog.
 Adding Images to Applications

After screenshots and icons are added the app catalog, it will look similar to the example shown.

Configuring Application Distribution Options

1. Configure Application Distribution Settings

 Application Distribution Settings
  1. Ensure that you are on the Distribution tab.
  2. Name - Enter the assignment name.
  3. Description - Enter the assignment description.
  4. Assignment Groups - Enter a smart group name to select the groups of devices to receive the assignment.
  5. Deployment Begins - Set a day of the month and a time of day for the deployment to start.
    • The time zone currently displayed is the time zone for your admin account.
  6. App Delivery Method 
    • Auto
      • Deploys content to a catalog or other deployment Hub on a device upon enrollment. After the device enrolls, the system prompts users to install the content on their devices.
      • This option is the best choice for content that is critical to your organization and its mobile users
    • On Demand
      • Deploys content to a catalog or other deployment agent and lets the device user decide if and when to install the content.
      • This option is the best choice for content that is not critical to the organization. Allowing users to download the content when they want helps conserve the bandwidth and limits unnecessary traffic.
  7. Hide Installation Notifications 
    • Enable this setting to prevent install and uninstall notifications from appearing for this application. This only applies to Auto deployed applications.
  8. Allow User Install Deferral 
  9. Use UEM or Custom Notifications - Enable to allow the user to defer installation of this application
    • UEM Notifications - Coming soon.
    • Custom Notifications - Custom notifications and installation deferrals require the application to be zipped up with the PowerShell App Deployment Toolkit (PSADT). You can find the PSADT here PSAppDeployToolkit.
  10. Installer Deferral Interval 
    • Specify the deferral time frame. Time frames are 2 hours, 4 hours, 8 hours, 12 hours and 24 hours.
  11. Installer Deferral Exit Code 
    • Specify the integer code returned by the installer to indicate that the app installation has been deferred. This will allow the app installation to be retried at the next installation interval.
  12. Display in App Catalog
    • Use this feature to hide applications in the app catalog you do not want users to access.

Note: The Windows Application Transforms option is visible when your app has transform files associated. Select the transform file that must be used on the devices selected in the Distribution section.

2. Review Application Restrictions

 Application Restrictions
  1. Ensure that you are on the Restrictions tab.
  2. Make App MDM Managed if User Installed 
    • Assume management of applications previously installed by users on their Windows Desktop.
  3. Desired State Management
    • Only applicable to MDM managed apps deployed using the Auto delivery method. When enabled, the application will be automatically re-installed when an uninstall is detected. When disabled, the application will not be re-installed when uninstall is detected.

3. Review Application Assignments

Review Application Assignments
  1. Ensure that you are on the Assignments tab.
  2. Review any applications Assignments.
  3. Add any Exclusions if necessary.
  4. Click Save.

Using the Enterprise Application Repository

Adding Applications from Enterprise Application Repository

Workspace ONE introduced a new Enterprise App Repository starting with Workspace ONE UEM 2007. This repository is built for admins and will serve as a one-stop-shop to procure 100s of commonly used, prepackaged, and preconfigured apps that IT can instantly deploy to end-users Workspace ONE Intelligent Hub catalog. Furthermore, the apps in the repository are kept up to date and pretested across the last three OS builds, ensuring a guaranteed installation.

 Adding Applications from Enterprise Application Repository

The Enterprise App Repository is updated every 24 hours with any newly available applications.


To stay updated on the latest applications in Enterprise Application Repository, follow Enterprise App Repository (@EntAppRepo) on Twitter.

Or, click the following link.

1. Add Applications from Enterprise Application Repository

In the Workspace ONE UEM admin console, navigate to Resources > Apps > Native.

  1. Select Internal.
  2. Click Add.
  3. Select From Enterprise App Repository.

1.1. Search Repository of Applications

  1. You can Search for an application, this searches the Name field.
  2. You can also perform a Sort in the columns:
    • Language - Click the filter icon, start typing the Language and press enter.
    • Architecture - Click the filter icon and select x86 or x64.
    • Platform - Click the filter icon and select Windows Desktop.

In this example, we use MS Edge for Business.

  1. Enter edge and press Enter.
  2. This application is available for x64 and x86 architectures. Select the appropriate architecture.
  3. Click Next.

1.2. Configure Application Details

  1. Enter an application Name, for example, Microsoft Edge for Business.
    • This name will appear in the app catalog as this name.
  2. For Managed By, select the Organization Group that manages this application.
  3. Click Next.

1.3. Confirm Summary

  1. Review the summary.
  2. Click Save.

App manifest data such as app name, version, download URL, icon image URL, language, vendor, and deployment options (when to install, how to install, and when to call install complete) are stored in the Enterprise App Repository catalog service. The catalog service is updated with new apps, versions, and languages after validations are completed by our R&D team. Therefore, what you see today can change tomorrow. This also means that irrespective of your Workspace ONE UEM console version (if you are on version 20.07+), you will see the latest apps available for deployment when accessing the Enterprise App Repository.

The Enterprise App Repository is solely responsible for providing the Workspace ONE UEM console with the required app metadata required to add the app. It is important to note that the catalog service will return the download URL, and then this third-party download URL is used to download the app binaries, which then gets uploaded to your Workspace ONE UEM console. This is the reason for a warning on the summary page when adding a new app, as shown in the previous screenshot.

1.4. Review the Application Details

In the Workspace ONE UEM Console:

  1. Search for the app.
  2. Click the edit icon.
  1. Select the tabs to see detailed information about the application. Change any values that you want - however, because the information has been pulled from the repository, you probably will not need to make changes.
  2. Review information such as Install command.

Tip: Ensure that you Assign the Application after adding the application.

1.5. If the Applications Already Exist

If the application already exists, you will see the following error: 

Application version already exists at Organization Group. The app can not be uploaded if it already exists in an active, retired or inactive state in the applications list. You can re-activate the existing records or delete them and try to re-upload.

You can add this application at another organizational group, or check if this application exists in the Workspace ONE UEM console and delete it if necessary. The application might be in an active, retired, or inactive state.

2. How to Request Additional Applications or Languages

You can send an email to EARrequests@vmware.com. Provide as much detail as possible, including the current use case and deployment sizes, which might help us prioritize.


To stay updated on the latest applications in Enterprise Application Repository, follow Enterprise App Repository (@EntAppRepo) on Twitter.

Or, click the following link.

Latest Enterprise Application Respository Updates

Follow Enterprise App Repository ON twitter - @EntAppRepo
Provides app notifications for @WorkspaceONE Enterprise App Repository! Follow to stay up-to-date on latest apps. 
Unofficial bot, not supported by @VMware. Built by VMware Workspace ONE Experts!

Recommended configurations for VMware Applications

Overview

Workspace ONE provides a suite of applications available for Windows 10 devices. These applications include:

This section provides details about these applications' capabilities.

Workspace ONE Intelligent Hub for Windows 10

 Workspace ONE Intelligent Hub for Windows 10

The Workspace ONE Intelligent Hub app is the single destination where employees can have an enhanced user experience with unified onboarding, catalog, and access to services such as People, Notifications, and Home.

  • Stay Secure, Stay Connected - Workspace ONE Intelligent Hub extends mobile device management (MDM) and mobile app management (MAM) capabilities and enables your company to keep your device secure, compliant, and connected. You can also view device details, messages from IT, and verify compliance status, and request support from your IT administrator.
  • App Catalog, People, Notifications, and Home in a Single App - Single catalog experience with optional services such as People, Notifications, and Home. You can now favorite apps and websites that you need quick access to, rate apps, use the search function in the Catalog, get recommended & popular apps, access corporate resources and home page, and much more.
  • The Entire Company in Your Pocket - Easily search through your corporate directory by first name, last name, or email address and view employee details such as photos, titles, email addresses, phone numbers, office location, and reporting structures. You can call, text, or email easily from within the app.
  • Stay on Top of Company Notifications - Improve productivity wherever you are and get notified with app notifications and custom notifications. Custom notifications can be notification alerts, downtimes, and participation in surveys.

Workspace ONE Tunnel Client for Windows 10

 Workspace ONE Tunnel Client for Windows 10

Enable your workforce with seamless and secure access to their work resources. Workspace ONE Tunnel connects users to their applications, sites, and files while maintaining privacy and minimizing user interaction. You can configure Tunnel per-application for your favorite browser, store app, or internally developed app.

Workspace ONE Assist for Windows 10

 Workspace ONE Assist for Windows 10

Workspace ONE Assist is a remote management service that provides IT and Help Desk personnel with the ability to remotely troubleshoot, support, maintain, and provide training on mobile and desktop devices, without requiring physical access to the device.

  • Workspace ONE Assist provides several tools to enable IT to troubleshoot and resolve various classes of device issues across the various platforms. Workspace ONE Assist includes Remote View/Control, File Manager, Command Line/Shell, and Registry Editor.
  • Workspace ONE Assist eliminates end-user downtime, lost productivity, device returns, visits to help desks, and site visits by IT. Workspace ONE Assist is an add-on product offered with Workspace ONE and was previously called VMware Advanced Remote Management.

For more information, see the VMware Workspace ONE Assist product page.

Workspace ONE Horizon Client for Windows 10

 Workspace ONE Horizon Client for Windows 10

VMware Horizon Clients for Windows, Mac, iOS, Linux, Chrome, and Android allow you to connect to your VMware Horizon virtual desktop from your device of choice giving you on-the-go access from any location.

Refer to the VMware Compatibility Guide for a list of certified thin clients, zero clients, and other partner solutions for VMware Horizon.

How to Download VMware Applications

To download the Workspace ONE Intelligent Hub for Windows 10, Workspace ONE Tunnel Client for Windows 10, or Workspace ONE Assist for Windows 10, you must log in to My Workspace ONE (https://my.workspaceone.com/) with your myVMware credentials.

You will find the Workspace ONE Horizon Client for Windows 10 at https://my.vmware.com/ under the downloads section.

Before You Download Applications

Before you download applications:

  • You can save time if you have all installation files pre-downloaded on your local machine to upload into Workspace ONE UEM.
    To improve user experience, ensure that you have the application icons and screenshots of the application available for the Application catalog.
  • Check with the software vendor for any requirements that the software might have.

1. Download Workspace ONE Applications

In this example, we download the Workspace ONE Assist application. We always recommend downloading the latest versions.

Download the Workspace ONE Assist Windows MSI Installer

To download the Workspace ONE Assist MSI installer file.

  1. Navigate to https://my.workspaceone.com/ and log in with your MyVMware credentials.
  2. Navigate to Software.
  3. Click All Software.
Download the Workspace ONE Assist Windows MSI Installer
  1. Search for Windows 10 Assist.
  2. Ensure that the software is for Windows 10 and click the link to begin download.
Download the Workspace ONE Assist Windows MSI Installer
  1. Acknowledge that you have Read and Accepted the Terms and Conditions.
  2. Click Accept.
Download the Workspace ONE Assist Windows MSI Installer

After you have accepted the terms, the download should begin immediately.

If the download does not begin:

  1. Click Download Resource.
Download the Workspace ONE Assist Windows MSI Installer

Extract the ZIP folder to find the following files:

  1. Workspace ONE Assist Windows 10 Read Me document.
  2. Workspace ONE Assist MSI Installer file.
  3. Workspace ONE Assist Icon for App Catalog.

2. Download the Horizon Client EXE Installer


 Download the Horizon Client exe Installer

To download the Horizon Client for Windows 10 EXE installer file:

  1. Navigate to https://my.vmware.com/en/web/vmware/downloads/info/slug/desktop_end_user_computing/vmware_horizon_clients/5_0 and log in with your MyVMware credentials.
  2. Navigate to VMware Horizon Client for Windows.
  3. Click Go To Downloads.
 Download the Horizon Client exe Installer
  1. Click Select Version to choose the version of the Horizon Client.
  2. Click Download Now.

Distributing Workspace ONE Intelligent Hub for Windows 10

This section helps you to distribute Workspace ONE Intelligent Hub for Windows 10.

1. Enroll Windows 10 Using Command-Line Enrollment

You have several options when using command-line enrollment. This includes staged provisioning, onboarding with a PC Lifecycle Management (PCLM) solution such as ConfigMgr using Workspace ONE AirLift, and deploying a script via a group policy object (GPO), such as a login script.

All of these options have one thing in common: using the command-line parameters supported with the Workspace ONE Intelligent Hub, which streamlines enrollment.

For more information, see Onboarding Windows 10 Using Command-Line Enrollment: VMware Workspace ONE Operational Tutorial.

2. Download the Workspace ONE Intelligent Hub

The Workspace ONE Intelligent Hub for Windows 10 is available for download in the following locations.

  • GetWSOne Public Website
    • On a Windows 10 device, navigate to https://getwsone.com/ and select Download Hub for Windows 10.
    • End users can manually install this application if they have admin rights on their machine and onboard themselves.
  • Using Workspace ONE AirLift
  • Workspace ONE UEM Console 
  • my Workspace ONE Downloads
    • You can find the download binaries on the Workspace ONE Intelligent Hub product page on My Workspace ONE.

3. Auto-Deploy and Auto-Update Workspace ONE Intelligent Hub for Windows 10

You can configure the Workspace ONE Intelligent Hub for Windows 10 to automatically deploy if the device is enrolled via the OMA-DM channel. The main use case is if a device is enrolled when signing in using Azure Autopilot or Out Of Box Experience (OOBE), this setting ensures that the Workspace ONE Intelligent Hub will be installed on the device.

 Auto-Deploy and Update the Intelligent Hub

In the Workspace ONE UEM admin console, navigate to Groups and Settings > All Settings:

  1. Navigate to Devices & Users > Windows > Windows Desktop> Intelligent Hub Application.
  2. Select the check box Publish Workspace ONE Intelligent Hub.
    • Now if a Device enrolls through the OMA-DM Channel with Windows, Workspace ONE will install the Intelligent Hub for Windows automatically to the device.
  3. Select the Device Ownership Type when publishing Workspace ONE Intelligent Hub.
  4. Select the Intelligent Hub Automatic Updates check box.
    • Select this option to keep devices up to date with the latest Intelligent Hub version. The Intelligent Hub version should match the version of Workspace ONE UEM.
    • For example, Workspace ONE UEM version 2010 will have the Intelligent Hub for Windows version 2010 and so on.
    • If you have a device that has the Intelligent Hub for Windows version 2008 and Intelligent Hub Automatic Updates is selected, the Hub will be upgraded to the latest version for that UEM console release.

4. Confirm the Installation of the Workspace ONE Intelligent Hub

To confirm that the Intelligent Hub has been installed, navigate to the device and view its applications in the Workspace ONE UEM admin console.

 Confirming the Installation of the Intelligent Hub
  1. Confirm that you can see the Workspace ONE Intelligent Hub Installer.
    • Also, check that the version is the latest. In this example, the version is 2010.
  2. Confirm that you can see the App Deployment Agent x64.
    • This application will be installed with the Intelligent Hub Installer. This application looks after the software delivery mechanism within Workspace ONE UEM.

Distributing Workspace ONE Tunnel Client for Windows 10

In this activity, you deploy the Workspace ONE Tunnel desktop application on Windows 10 devices.

Note: The Per-App VPN profile should already be configured as part of the prerequisites.

Important: A VPN tunnel must be set up before you begin adding it as an application. For more information, see Configuring the VMware Tunnel Edge Service: VMware Workspace ONE Operational Tutorial.

1. VMware Tunnel Installer Requirements

In this example, we will use the Workspace ONE Tunnel EXE Installer.

Review the requirements in Supported Platforms for VMware Workspace ONE Tunnel.

2. Download the Workspace ONE Tunnel EXE Installer

Ensure that you download the latest version of VMware Tunnel.

To download the VMware Tunnel application, go to https://my.workspaceone.com/products/Workspace-ONE-Tunnel.

Also, see Downloading VMware Applications for more information on other available Workspace ONE applications.

3. VMware Tunnel Application ID

The following table lists the VMware Tunnel Application ID values. Use the uninstall string for the matching version of the application.

Alternatively, retrieve this ID with the next steps: 

  1. Install the application and navigate to the corresponding registry key.
  2. Run gwmi win32_product in PowerShell and find the IdenifyingNumber on a machine that has the application installed. 

See How to find application installation/uninstall parameters for more information.

These details were obtained in the registry location:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{INSERT-APP-ID}.

Replace {INSERT-APP-ID} with the IdentifyingNumber value in the following table.

Version

IdenifyingNumber

Uninstall String
2.0.2.5
{D350D08C-7CB7-42AF-A9E9-2A1E6F590FC8}
"%SystemRoot%\System32\msiexec.exe" /X {D350D08C-7CB7-42AF-A9E9-2A1E6F590FC8} /qn
2.0.3.9
{88B0F264-8934-44BA-BE46-570D048B6180}
"%SystemRoot%\System32\msiexec.exe" /X {88B0F264-8934-44BA-BE46-570D048B6180} /qn
2.1.1 {09941862-4753-407F-B7AD-7B2314641BF4}
"%SystemRoot%\System32\msiexec.exe" /X {09941862-4753-407F-B7AD-7B2314641BF4} /qn
2.1.2

{68E9E950-DF9B-4DF1-9A45-810650A75613}

"%SystemRoot%\System32\msiexec.exe" /X {68E9E950-DF9B-4DF1-9A45-810650A75613} /qn

4. Upload Tunnel Application into Workspace ONE UEM

Upload Application into Workspace ONE UEM

In the Workspace ONE UEM admin console:

  1. Click Apps and Books.
  2. Select Internal Application.
  3. Click Add Application and Upload.
  4. Browse for the Workspace ONE Tunnel EXE installer file and click Save.
  5. Select No for Is this a dependency app?.
  6. Click Continue.

4.1. Configure the Details Tab


Configure the Details Tab
  1. Ensure the Details tab is selected.
  2. Enter a Name, for example, Workspace ONE Tunnel.

4.2. Configure the Files Tab


Configure the Files Tab
  1. Select the Files tab.
  2. Scroll down to find the App Uninstall Process section. For VMware Tunnel, enter VMware Workspace ONE Tunnel 1.2 for Win10_Desktop.exe /uninstall /Passive as the Uninstall Command.

You can also enter "%SystemRoot%\System32\msiexec.exe" /X{INSERT-APP-ID}/qn as the uninstall command. See How to find install/uninstall parameters for more information on finding the uninstall commands for EXE installers.

4.3. Configure the Deployment Options Tab

In this section, define settings in the Deployment Options tab.

4.3.1. Define When to Install


Deployment options: When to Install
  1. Select the Deployment Options tab.
  2. Locate the When to Install section.
  3. Configure any minimum requirements for the following:
    • Data Contingencies - Use where criteria type needs to check for existing/non-existing Applications, Files, or Registry Keys.
    • Disk Space Required - Specifies the amount of disk space the device must have available to install the application.
    • Device Power Required - Specifies the battery power, in percentage, that the device must have to install the application.
    • RAM Required - Specifies the amount of RAM the device must have to install the application.

4.3.2. Find the Install Command Options

Some application installers may contain help options. Find help options by running the application file and adding /help or /? to the end of the file. This should show a dialog box to show supported installation commands.

Workspace ONE Tunnel Install parameters

4.3.3. Define How to Install


Define How to Install
  1. Select Deployment Options.
  2. Scroll down to find the How To Install section.
  3. For the Install Command, enter VMware Workspace ONE Tunnel 1.2 for Win10_Desktop.exe /Install /Passive.
  4. Ensure Admin Privileges is set to Yes.
  5. Change Device Restart if required. This example uses User Engaged Restart. This allows the user to reboot the machine to complete the install when the user is ready.
  6. For Installer Reboot Exit Code, the supported values are 3010 and 1641.
  7. For Installer Success Exit Code, the supported values are 0 and 3010.
Error code
Value
Description
ERROR_SUCCESS
0 The action completed successfully.
ERROR_SUCCESS_REBOOT_INITIATED
1641 The installer has initiated a restart. This message is indicative of a successful action.
ERROR_SUCCESS_REBOOT_REQUIRED
3010
A restart is required to complete the install. This message is indicative of a successful action. This does not include installs where the ForceReboot action is run.

For more information on Installer codes, see Microsoft Docs: MsiExec.exe and InstMsi.exe Error Messages.

4.3.4. Define When To Call Install Complete


Define When To Call Install Complete
  1. Click Add.
  2. Select File Exists for the Criteria Type.
  3. Enter C:\Program Files\VMware\Workspace ONE Tunnel\VMwareTunnel.exe for the Path.
  4. Click Add.

4.4. Add the Application Icon

You can download this icon to use in your environment.

 Add the Application Icon
Add the Application Icon
  1. Select the Images tab.
  2. Select the Icon tab.
  3. Click the area labeled Click or drag files here.
  4. Navigate to the folder containing the Application logo, or download the provided image to use.

Your icon should now be uploaded.

4.5. Set Terms of Use

Set Terms of Use
  1. Select the Terms of Use tab.
  2. If you decide to have a Terms of Use that your users must accept before installing applications, you can configure that here. For this exercise, select None.
  3. Click Save & Assign.

4.6. Add Assignment

  1. Select Assignments.
  2. Click Add Assignment.

4.7. Configure Assignment

In this section, configure the assignment details.

4.7.1. Create Application Assignment

 Creating Application Assignment
  1. Select Add Assignment.

4.7.2. Define Application Distribution Settings

 Application Distribution Settings
  1. Enter a name for the application distribution. For example, ACME Corp.
  2. Select the Assignment Groups search box and select an Assignment group. In this example, we are using Acme Corp(Acme Corp).
  3. Select On-Demand for the App Delivery Method.
  4. Select Show for Display in App Catalog.
  5. Navigate to the Restrictions tab.

4.7.3. Define Application Restriction Settings

 Application Restriction Settings
  1. Enable for Make App MDM Managed if User Installed.
  2. Click Save then click Save and Publish.

5. Confirm that the Application Appears in List View

 Confirm the Application Appears in the List View

On the Internal applications List View page, confirm that the Workspace ONE Tunnel desktop application is displayed.

6. Confirm that the Application Installed in Workspace ONE UEM

In the Device details page of the Workspace ONE UEM Console:

  1. Navigate to the Applications tab.
  2. Search for Tunnel.
  3. Note the Tunnel Application. This was the EXE installer configured in Workspace ONE.
  4. Note the Workspace ONE Tunnel application. This is the application found on the device.

Note that there are 2 versions of Workspace ONE Tunnel listed in the applications. As EXE files can contain many applications, Workspace ONE UEM will report them separately. It is important to use the correct When to call install complete criteria to ensure any updates to applications have been applied.

You have successfully added the Workspace ONE Tunnel desktop application to Workspace ONE UEM for deployment.  

Distributing the Workspace ONE Assist Client for Windows 10

In this activity, you deploy the Workspace ONE Assist application on Windows 10 devices.

Note: Before you begin, ensure that you have a Workspace ONE Assist environment.

1. Workspace ONE Assist Installer Requirements

In this example, we will use the Workspace ONE Assist MSI installer.

The minimum requirements for Workspace ONE can be found in the Word document located in the ZIP file of contents.

  • Win 10 Anniversary Edition or later (Enterprise and Pro).
  • NVIDIA and Intel Graphic chipsets, 64-bit processors.
  • Workspace ONE Intelligent Hub 1907.
  • Workspace ONE UEM 1907.
  • Latest versions of Chrome, Edge, Firefox, or Safari.

1.1. Find the Installation Parameters

Tip: Not all applications will support command msiexec command-line parameters. 

Always check with the application vendors' documentation for command-line parameter support.


MSI exec command line options

Note the following items in this screenshot.

  1. File location of the MSI.
  2. Help command /? or /help
  3. Dialog box with supported msiexec commands.

To review the msiexec options, perform the following:

  • Hold shift + right-clicking the MSI file.
  • Select Copy As Path.
  • Paste into a command prompt window following command /? or /Help

2. Download the Workspace ONE Assist Installer

Ensure that you download the latest version of Workspace ONE Assist.

See Downloading VMware Applications for more information on other available Workspace ONE applications.

3. Extract the Installer from the ZIP file

Download the Workspace ONE Assist Windows MSI Installer

Extract the ZIP folder to find the following files:

  1. Workspace ONE Assist Windows 10 Read Me document.
  2. Workspace ONE Assist MSI Installer file.
  3. Workspace ONE Assist Icon for App Catalog.

4. Upload Application into Workspace ONE UEM

Upload Application into Workspace ONE UEM
  1. In the Workspace ONE UEM admin console, select Apps & Books.
  2. Select Internal application.
  3. Click Add Application and Upload.
  4. Browse for the MSI Installer file and click Save.
  5. Select No for Is this a dependency app?.
  6. Click Continue.

4.1. Configure the Details Tab


Configure the Details Tab
  1. Ensure the Details tab is selected.
  2. Enter Workspace ONE Assist for the Name.
  3. Select 64-bit for the Supported Processor Architecture. Verify which processor architecture is relevant for your device.

Note: When uploading MSI files, all possible fields are automatically pre-populated with all of the metadata. In the previous screenshot, see the "Version" field.

4.2. Configure the Files Tab

Configure the Files Tab
  1. Navigate to the Files tab.
  2. Scroll down to find the App Uninstall Process section.

Note: MSI Installers will generally contain the uninstall instructions for the applications. You can add custom uninstall commands and scripts if necessary.

4.3. Configure the Deployment Options Tab

In this section, configure options on the Deployment tab.

4.3.1. Define When to Install

Deployment options: When to Install

Configure details about what requirements must be met to install the application.

  1. Select the Deployment Options tab.
  2. Scroll to the When to Install section.
  3. Configure any minimum requirements for
    • Data Contingencies - Use where criteria type needs to check for existing/non-existing Applications, Files, or Registry Keys.
    • Disk Space Required - Specifies the amount of disk space the device must have available to install the application.
    • Device Power Required - Specifies the battery power, in percentage, that the device must have to install the application.
    • RAM Required - Specifies the amount of RAM the device must have to install the application.

4.3.2. Define How to Install


Define How to Install
  1. Scroll down to the How To Install section.
  2. Leave Install Context set to Device.
  3. Notice that the Install Command has already been pre-populated with the metadata from the MSI file.
  4. Leave Admin Privileges as Yes.
  5. Change Device Restart to specified settings. Change the settings to Restart If Required.
  6. Note that the Retry Count, Retry Interval, Install Timeout, Installer Reboot Exit Code, and Installer Success Exit Code all have values. This is Workspace ONE UEM extracting metadata from the MSI file.
  7. You can specify any additional criteria for When To Call Application Complete if necessary. For this exercise, we will leave the default values.

4.4. Add the Application Icon

Add the Application Icon
  1. Select the Images tab.
  2. Select the Icon tab.
  3. Click the area labeled Click or drag files here.
  4. Navigate to the folder containing the Workspace ONE Assist logo and/or screenshot(s) files and select the file(s).

Your icon should be uploaded as per the screenshot.

4.5. Set Terms of Use

Set Terms of Use
  1. Select the Terms of Use tab.
  2. If you decide to have a Terms of Use that your users must accept before installing applications, you can configure that here. For this exercise, select None.
  3. Click Save & Assign.

4.6. Assign & Publish Application

 Assign & Publish
  1. Select Assignments.
  2. Click Add Assignment.
 Assign & Publish
  1. Enter a name. For example, Assist - All Devices.   
  2. Select the Assignment Groups search box and select All Devices or the Assignment Groups you want to deploy to.
  3. Select Automatic for the App Delivery Method. We want this application to auto-install to devices.
  4. Review configurations and click Save.

5. Confirm that the Application Appears in List View

 Confirm the Application Appears in the List View

On the Internal applications List View page, confirm that the Workspace ONE Assist application is displayed.  

  1. Navigate to Resources > Apps > Native and Internal.
  2. Search for Assist in the search box.
  3. Confirm the Workspace ONE Assist application and Windows Platform.

6. Confirm that the Application Installed in Workspace ONE UEM

 Confirm the Application Installed in Workspace ONE UEM

In the Device details page of the Workspace ONE UEM admin console:

  1. Navigate to the Applications tab.
  2. Search for Assist.
  3. Because Workspace ONE Assist is an MSI installer, one record shows in the applications.

You have successfully distributed the Workspace ONE Assist client to Windows 10 devices using Worksapce ONE UEM.

7. Summary

You can deploy MSI applications using software distribution.

The VMware Workspace ONE application life cycle flow, also known as software distribution,  exists for all internal applications. Use software distribution to deliver Win32 applications, track installation statuses, keep  application versions current, and delete old applications.

Note: VMware software distribution supports MSI, EXE and ZIP files. The required application details vary by application and  file type.

Distributing the Workspace ONE Horizon Client for Windows 10

In this activity, you deploy the Horizon Client on Windows 10 devices.

Important: A Horizon environment must be set up to connect to. For more information, see Quick-Start Tutorial for VMware Horizon 7.

1. Horizon Client Installer Requirements

In this example, we use the Horizon Client EXE Installer.

Review the requirements for specific Horizon Client versions in System Requirements for Windows Client Systems.

2. Download the Horizon Client EXE Installer

Ensure that you download the latest version of the Horizon Client EXE Installer.

See Downloading VMware Applications for more information on other available Workspace ONE applications.


 Download the Horizon Client exe Installer
  1. Navigate to https://my.vmware.com/web/vmware/downloads/info/slug/desktop_end_user_computing/vmware_horizon_clients/horizon_8 and log in with your MyVMware credentials.
  2. Navigate to VMware Horizon Client for Windows.
  3. Click Go To Downloads.
 Download the Horizon Client exe Installer
  1. Select the version of the Horizon Client from the drop-down menu.
  2. Click Download Now.

3. Horizon Client Application ID

The following table lists the Horizon Client Application ID values. Use the Uninstall string for the matching version of the application.

Alternatively, retrieve this ID with the next steps: 

  1. Install the application and navigate to the corresponding registry key. See How to find application installation/uninstall Parameters.
  2. Run gwmi win32_product in PowerShell and find the IdenifyingNumber on a machine that has the application installed. See How to find application installation/uninstall Parameters for more information.

These details were obtained in the registry location Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{INSERT-APP-ID}

Replace {INSERT-APP-ID} with the IdentifyingNumber value in the following table.

Version

IdenifyingNumber

Uninstall String
5 {7CE636E2-F0C3-4AED-A087-AF6644343D00}
"%SystemRoot%\System32\msiexec.exe" /X {7CE636E2-F0C3-4AED-A087-AF6644343D00} /qn
5.1 {C7130443-13FF-4BAC-A4E4-50F891FE122F}
"%SystemRoot%\System32\msiexec.exe" /X {C7130443-13FF-4BAC-A4E4-50F891FE122F} /qn
5.2 {E6D407E4-66C9-4D6A-89DD-9A53FCF57BC7}
"%SystemRoot%\System32\msiexec.exe" /X {E6D407E4-66C9-4D6A-89DD-9A53FCF57BC7} /qn
5.3 {6D3FF39C-B5B6-4C3F-B0E0-55297C00D512}
"%SystemRoot%\System32\msiexec.exe" /X {6D3FF39C-B5B6-4C3F-B0E0-55297C00D512} /qn
5.4 {CD5FD442-ED2C-4BE0-8D97-A4705121898F}
"%SystemRoot%\System32\msiexec.exe" /X {CD5FD442-ED2C-4BE0-8D97-A4705121898F} /qn
5.4.2 {0771AA0E-A472-4FCE-A700-EA2982AE1139}
"%SystemRoot%\System32\msiexec.exe" /X {0771AA0E-A472-4FCE-A700-EA2982AE1139} /qn
5.4.2 {73499771-35D2-4F4E-AC1B-8417816D6F6A}
"%SystemRoot%\System32\msiexec.exe" /X {73499771-35D2-4F4E-AC1B-8417816D6F6A} /qn
5.4.3 {B9990DBC-8E5E-46D5-93C2-1C68E5AC5587}
"%SystemRoot%\System32\msiexec.exe" /X {B9990DBC-8E5E-46D5-93C2-1C68E5AC5587} /qn
2006 {51693296-051E-4316-AC92-78A0E980E4AC}
"%SystemRoot%\System32\msiexec.exe" /X {51693296-051E-4316-AC92-78A0E980E4AC} /qn

4. Upload Application into Workspace ONE UEM

 Upload Application into Workspace ONE UEM
  1. In the Workspace ONE UEM admin console, click Resources.
  2. Under Apps, click Native.
  3. Select Internal application.
  4. Click Add Application and Upload.
  5. Browse for the EXE Installer file and click Save.
  6. Select No for Is this a dependency app?.
  7. Click Continue.

4.1. Configure the Details Tab

 Configure the Details Tab
  1. Ensure the Details tab is selected.
  2. Enter a Name, for example, Horizon Client.

4.2. Configure the Files Tab

 Configure the Files Tab
  1. Select the Files tab.
  2. Scroll down to find the App Uninstall Process section. For the Horizon Client version 2006, enter "%SystemRoot%\System32\msiexec.exe" /X {51693296-051E-4316-AC92-78A0E980E4AC} /qn as the Uninstall Command.

4.3. Configure the Deployment Options Tab

In this section, define the Deployment Options for the Horizon Client application.

4.3.1. Define How to Install

 Define How to Install
  1. Select the Deployment Options tab.
  2. Scroll down to the How To Install section.
  3. For the Install Command, enter VMware-Horizon-Client-2006-8.0.0-16531419.exe /silent /install
  4. Leave Admin Privileges as Yes.
  5. Navigate to the When To Call Install Complete section.
  6. Select File Exists for the Criteria Type. Enter File exists - C:\Program Files (x86)\VMware\VMware Horizon View Client\vmware-view.exe for the Path.

4.4. Add the Application Icon

You can download the following icon to use.

Vmware Horizon Application Icon
 Add the Application Icon
  1. Select the Images tab.
  2. Select the Icon tab.
  3. Click the area labeled Click or drag files here.
  4. Navigate to the folder containing the application logo, or download the provided image to use.

Your icon should now be uploaded.

4.5. Set Terms of Use

Set Terms of Use
  1. Select the Terms of Use tab.
  2. If you decide to have a Terms of Use that your users must accept before installing applications, you can configure that here. For this exercise, select None.
  3. Click Save & Assign.

4.6. Add Assignment

 Assign & Publish
  1. Select Assignments.
  2. Click Add Assignment.
 Assign & Publish
  1. Enter a name for the application assignment. For example, horizon.
  2. Click the Assignment Groups search box and select an assignment group. For example (All Corporate Dedicated Devices).
  3. Select On-Demand for the App Delivery Method.
  4. Select Show for Display in App Catalog.
  5. Click Save.

5. Confirm that the Application Appears in List View

On the Internal applications List View page, confirm that the Horizon Client application is displayed.  

  1. Navigate to Resources > Apps > Native and select Internal.
  2. Search for Horizon in the search box.
  3. Confirm that you can see the Horizon Application and Windows Platform.

5.1. Confirm that the Application Installed in Workspace ONE UEM

 Confirm the Application Installed in Workspace ONE UEM

On the Device details page of the Workspace ONE UEM admin console:

  1. Select the Apps tab.
  2. Search for Horizon in the search box.
  3. Note the Horizon Client application. This was the EXE installer configured in Workspace ONE.
  4. Note the VMware Horizon Client application. This is the application found on the device.

In this example, there are 2 versions of Horizon Client listed in the applications. As EXE files can contain many applications, Workspace ONE UEM will report them separately. It is important to use the correct When to call install complete criteria to ensure that any updates to applications have been applied.

You have successfully added the Horizon Client application to Workspace ONE UEM for deployment.  

DEM client

Carbon Black

Recommended configurations for Third-Party Applications

Configuring Third-Party Applications Overview

Workspace ONE UEM supports the upload and deployment of MSIs, EXEs, and packaged apps. In this exercise, review additional examples of the supported application types, and their required Workspace ONE UEM configurations.

Refer to the VMware Knowledge Base article Software Distribution: Tips and Troubleshooting (2960987) for a list of validated use cases and instructions on retrieving required application information.

Prerequisites

Before you can perform the steps in this exercise, you must install and configure the following components:

  • Latest Workspace ONE UEM console
    • Ensure that you have enough application storage
    • Enable Software Distribution
  • Windows 10 device that meets the following specifications:
    • Enroll the device in Workspace ONE UEM
    • A virtual machine or spare Windows device
    • Windows 10 with the latest updates installed
    • Install Workspace ONE application on the Windows 10 device
    • Enable administrative rights (for troubleshooting if required)

Deploying Office 365 with Workspace ONE UEM (Scripted Install)

This exercise helps you configure and assign Microsoft Office 365 Pro Plus with a configuration file for click-to-run delivery. The procedures are sequential and build upon one another, so make sure that  you complete each section in order for the specific use case you require.

With Workspace ONE UEM, there are 3 different ways Office 365 can be installed.

  1. Deploy Office 365 Click to Run Installer (Online).
  2. Deploy Office 365 Click to Run Installer (Offline).
  3. Office Deployment via MDM Policy.

The following table lists pros and cons of each approach.  

Deployment Method Pros Cons
Deploy Office 365 Click to Run Installer (Online) 
  • Uses Microsoft Content Delivery Network for downloading files.
  • Can be made available in the Workspace ONE Intelligent Hub app catalog.
  • Quick and simple set up with a couple of XML files for configuration.
Deploy Office 365 Click to Run Installer (Offline) 
  • Can leverage Peer Distribution integrations like Workspace ONE Peer Distribution (Branch cache) or Adaptiva as all the files are in the ZIP.
  • Can be made available in the Workspace ONE Intelligent Hub app catalog.
  • Works perfectly with Workspace ONE Factory Provisioning.
  • Configuration not as simple as the online version.
  • Need to maintain different versions of the Office installers.
  • Software cache on the client will also hold these files taking up storage.
Office Deployment via MDM Policy
  • Configured by MDM Policy. Can also track OOBE status.
  • Uses Microsoft Content Delivery Network for downloading files.
  • Even simpler set up with a conversion of an XML file.


  • Policy is a custom policy and data needs to be serialized so the operating system can read it.
  • Does not leverage Peer Distribution integrations like Workspace ONE Peer Distribution (Branch cache) or Adaptiva.
  • Can not be made available in the Workspace ONE Intelligent Hub catalog.

1. Create Configuration.xml File using the Office Customization Tool

For more information on the Office Customization Tool, see Overview of the Office Customization Tool.

1.1. Create a New Configuration

Create Configuration.xml file using the Office Customization Tool
  1. Go to config.office.com.
  2. Click Create under Create a new configuration.
Create Configuration.xml file using the Office Customization Tool
  1. Configure the Office deployment settings.
  2. Click Export to export the XML.
Create Configuration.xml file using the Office Customization Tool
Create Configuration.xml file using the Office Customization Tool
  1. Select file format - Keep Current Settings.
  2. Click Ok.
  3. Read the license terms and select the check box to Accept the license agreement.
  4. Ensure that File Name is configuration.xml.

1.2. Create the Uninstall.xml

Recommended: If you want to have an uninstall command in the Workspace ONE UEM console, create an uninstall.xml file. Copy and paste the following text into Notepad and name the file  uninstall.xml.

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

Note: This XML will uninstall Office Pro Plus Retail. You might need to change the product ID.

For more information, see Microsoft Docs: Overview of the Office Deployment Tool.

1.3. Office Customization Tool Tips

Using the Office Customization Tool, you can customize your installation of Office to meet the organization's needs.

You can:

  • Select which Office Edition to install.
  • Configure Specific Office Applications to install:
    • For example, Outlook, Word, Excel, PowerPoint, Teams.
  • Configure how Office receives Updates.
  • Configure Languages and more.
Configure Office Edition
Configure Office Applications
Configure Office Updates

For more information on the Office Customization Tool, see Overview of the Office Customization Tool.

1.4. Example Office XML Files

In this example XML, we are deploying the 64bit version of Office and have subscribed to the monthly enterprise channel for updates. Note in the XML I have excluded apps from being installed, these are Access, Groove, Lync, Publisher, and Teams. Teams has a standalone MSI that can be used for installing.

Review the following XML. You can also save this and select Import in the Office Customization Tool.

<Configuration ID="9ff04252-3f65-4869-a869-8694e8755570">
  <Add OfficeClientEdition="64" Channel="MonthlyEnterprise">
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
      <ExcludeApp ID="Access" />
      <ExcludeApp ID="Groove" />
      <ExcludeApp ID="Lync" />
      <ExcludeApp ID="Publisher" />
      <ExcludeApp ID="Teams" />
    </Product>
  </Add>
  <Property Name="SharedComputerLicensing" Value="0" />
  <Property Name="PinIconsToTaskbar" Value="TRUE" />
  <Property Name="SCLCacheOverride" Value="0" />
  <Property Name="AUTOACTIVATE" Value="0" />
  <Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />
  <Property Name="DeviceBasedLicensing" Value="0" />
  <Updates Enabled="TRUE" />
  <RemoveMSI />
  <AppSettings>
    <Setup Name="Company" Value="VMware EUC TechZone" />
  </AppSettings>
  <Display Level="Full" AcceptEULA="TRUE" />
  <Logging Level="Standard" Path="" />
</Configuration>

2. Office 365 Click to Run Installer (Online vs Offline)

In these next steps, we will use the XML files previously created to create an installer package for Office. We will do this for the online version and the offline version.

If you are using Workspace ONE Factory Provisioning, we recommend the offline deployment model. This means that users have the full Office suite installed as soon as they log in to their desktop for the first time.

For more information see Factory Provisioning: VMware Workspace ONE Operational Tutorial.

2.1. Download the Office Deployment Tool

Download the Office Deployment tool
  1. Download the Office Deployment Tool.
  2. Run the EXE file.
  3. Export the files to a location for later use. Create a folder called Office on the C: Drive or Desktop if required.

2.2. Create Office ZIP Package (Online)

Create Office Zip package
  1. Select Configuration.xml created from the Office Customization Tool, the uninstall.xml (as created previously or newly created if required), and setup.exe.
  2. Right-click each file (individually) and send them to a ZIP folder. 
  3. Name the file, for example, Office.

Next, follow the steps to upload application files into Workspace ONE UEM for delivery.

2.3. Create Office ZIP Package (Offline)

Download the Office Deployment tool
  1. Download the Office Deployment Tool.
  2. Run the EXE file.
  3. Export the files to a location for later use. Create a folder called Office on the C: Drive or Desktop if required.
command prompt download office
  1. Open Command Prompt as an administrator.
dowload office files
  1. Change the directory to the location of the Office files.
  2. Run setupodt.exe /download configuration.xml. In older versions of the Office Deployment Tool, the command would be setup.exe /download configuration.xml.
  3. This will create a folder called Office in the directory and start downloading all the files. Downloading the files may take some time depending on your internet connection.

Office Offline File Size
  1. Right-click the Office folder where the files are downloading. The file size should be almost 3 GB depending on how many applications you are installing.
zip up the office offline folders
  1. Select Configuration.xml created from the Office Customization Tool, the uninstall.xml (as created previously, or newly created if required), setupodt.exe, and the Office folder that was created.
  2. Select the files individually and send them to a ZIP folder. 
  3. Name the file. For example, Office (offline).

Next, follow the steps to upload application files into Workspace ONE UEM for delivery.

3. Upload Application Files to Workspace ONE UEM

Upload Application into Workspace ONE UEM
  1. In the Workspace ONE UEM admin console, select Apps & Books.
  2. Select Internal application.
  3. Click Add Application and Upload.
  4. Browse for the Office.zip file and click Save.
  5. Select No for Is this a dependency app?.
  6. Click Continue.

3.1. Configure the Details Tab

Configure the Office 365 Details Tab
  1. Ensure the Details tab is selected.
  2. Enter a Name, for example, Office 365.
  3. Select 64-bit for the Supported Processor Architecture. Verify the relevant processor architecture for your device.

Note: When uploading MSI files all possible fields are automatically pre-populated with all of the metadata. However, for ZIP packages you must generate a Name as well as some of the Deployment options.

3.2. Configure the Files Tab

Configure the Files Tab for Office 365
  1. Navigate to the Files tab.
  2. Scroll down to find the App Uninstall Process section.
  3. Select Input for the Custom Script Type.
  4. Enter setup.exe /CONFIGURE uninstall.xml in the Uninstall Command text box.

3.3. Configure the Deployment Options Tab

In this section, define the application deployment options.

3.3.1. Define When to Install

Configure the Deployment settings for Office 365
  1. Select the Deployment Options tab.
  2. Navigate to the When to Install section.
  3. Enter 3 for the Disk Space Required. This value specifies the amount of disk space the device must have available to install the application.
  4. Select GB for the units of the Disk Space Required.
  5. Enter 50  for the Device Power Required which specifies the battery power, in percentage, that the device must have to install the application.
  6. Enter 500 for the RAM Required. This value specifies the amount of RAM the device must have to install the application.
  7. Enter MB for the units of the RAM Required.

3.3.2. Define How to Install

Define Install commands for Office 365
  1. Scroll down to the How To Install section.
  2. Leave Install Context to Device.
  3. Enter setup.exe /configure configuration.xml or setupodt.exe /configure configuration.xml (depending on the version of the Office Deployment tool you have downloaded) for the Install Command.
  4. Leave Admin Privileges as Yes.
  5. Change Device Restart to specified settings. In this example, we are using Restart If Required.
  6. Enter 3 for the Retry Count, which specifies the number of times the system attempts to install the application after an unsuccessful attempt.
  7. Enter 5  for the Retry Interval, which specifies the time (in minutes) the system waits when it tries to install the application after an unsuccessful attempt.
  8. Enter 60 for the Install  Timeout, which specifies the time (in minutes) the system allows the installation process to run without success.
  9. Enter 1614 for the Installer Reboot Exit Code, which specifies the code the installer outputs to identify a reboot action.
  10. Enter 0 for the Installer Success Exit Code, which specifies the code the installer outputs to identify a successful installation.

3.3.3. Define When To Call Install Complete

Define When To Call Install Complete
  1. Scroll down to the When To Call Install Complete section.
  2. Select Defining Criteria for Identity Application By.
  3. Select Add.
Define When To Call Install Complete
  1. In the Criteria Type drop-down menu, select File Exists.
  2. Enter the Path C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE.

Note: There are multiple Criteria Types to choose from,  allowing flexibility in determining if your deployment was successful. You can also add multiple Criteria configurations and link them together logically to cover complex deployments.

3.4. Add the Application Icon

Add the Application Icon
  1. Select the Images tab.
  2. Select the Icon tab.
  3. Click the area labeled Click or drag files here.
  4. Navigate to the folder containing the Office365 files and select the file.

Your icon should be uploaded as per the following screenshot.

Add the Application Icon

3.5. Set Terms of Use

Set Terms of Use
  1. Select the Terms of Use tab.
  2. If you decide to have a Terms of Use that your users must accept before installing applications, you can configure that here. For this exercise, select None.
  3. Click Save & Assign.

3.6. Assign & Publish Application

 Assign & Publish
  1. Select Assignments.
  2. Click Add Assignment.
 Assign & Publish
  1. Enter a name for the Distribution. For example, Office (Online Installer).
  2. Select the appropriate Assignment Groups.
  3. Click Create.
 Assign & Publish
  1. Review the application deployment.
  2. Select Save.

4. Confirm that the Application Appears in the List View

Confirm the Application Appears in the List Vie

On the Internal applications List View page, confirm that the Office 365 Pro Plus application is displayed.  

You have successfully added the Office 365 ProPlus app to Workspace ONE UEM for deployment.  

5. Office Deployment using MDM Policy

The Microsoft Office Suite can also be deployed using MDM policy if you prefer not to deploy it using Workspace ONE UEM application distribution. This section details how to do this in Workspace ONE UEM.

5.1. Convert Customization.xml File

<Configuration ID="66a3e43a-b85d-43fe-98a1-6fa3b22a9da1">
  <Add OfficeClientEdition="64" Channel="Current">
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
      <ExcludeApp ID="Access" />
      <ExcludeApp ID="Groove" />
      <ExcludeApp ID="Lync" />
      <ExcludeApp ID="Publisher" />
      <ExcludeApp ID="Teams" />
    </Product>
  </Add>
  <Property Name="SharedComputerLicensing" Value="0" />
  <Property Name="PinIconsToTaskbar" Value="TRUE" />
  <Property Name="SCLCacheOverride" Value="0" />
  <Property Name="AUTOACTIVATE" Value="0" />
  <Property Name="FORCEAPPSHUTDOWN" Value="FALSE" />
  <Property Name="DeviceBasedLicensing" Value="0" />
  <Updates Enabled="TRUE" />
  <RemoveMSI />
  <Display Level="Full" AcceptEULA="TRUE" />
</Configuration>
Convert Customization.xml file

The previous image depicts the conversion using http://coderstoolbox.net/.

  1. Paste the Configuration.xml file into the editor.
  2. Your results should look similar to the previous screenshots. Save this output, as we will put it into a policy.

5.2. Convert Uninstall.xml File

<Configuration>
<Remove>
<Product ID=”O365ProPlusRetail”>
<Language ID=”en-us”/>
</Product>
</Remove>
<Display Level=”None” AcceptEULA=”TRUE”/>
</Configuration>
 Convert Uninstall.xml file

The previous image depicts the conversion using http://coderstoolbox.net/.

  1. Paste the Uninstall.xml file into the editor.
  2. Your results should look similar to the previous screenshots. Keep this window open, as we will now put the result into a policy.

5.3. Create Custom Profile in Workspace ONE UEM

 Creating Custom Profile in Workspace ONE UEM
 Creating Custom Profile in Workspace ONE UEM
 Creating Custom Profile in Workspace ONE UEM
 Creating Custom Profile in Workspace ONE UEM

In the Workspace ONE UEM admin console:

  1. On the shortcut menu, click Add and select Profile.
  2. Select Windows as the platform.
  3. Select Windows Desktop for Device Type.
  4. Select Device Profile.

 

 Creating Custom Profile in Workspace ONE UEM
  1. Enter a Name, for example, Office Deployment.
  2. Enter a profile Description.
  3. In this example, Assignment Type is set to optional so this can be manually pushed to the device.
  4. Select the target Smart Groups for deployment.
  5. Scroll down to Custom Settings.
 Creating Custom Profile in Workspace ONE UEM

In this step, we will use the Office configuration.xml that has been converted for the Install command, and the Uninstall.xml data that has been converted in the Remove Settings sections of the profile.

  1. Ensure you are on the Custom Settings tab.
  2. Navigate to Install Settings. Copy the Install Office XML (see Install Office CSP) into the Install Settings section.
  3. Navigate to the YOUR INSTALL TEXT GOES HERE between the <DATA> tags and copy in the converted configuration XML data.
  4. Navigate to Remove Settings. Copy the Uninstall XML into the Remove Settings section.
  5. Navigate to the YOUR UNINSTALL TEXT GOES HERE  between the <DATA> tags and copy in the converted configuration XML data.
  6. Click Save and Publish.

5.3.1. Install Office CSP

Following is an example of the Office CSP. You can also find examples here Microsoft Docs - Office CSP.

Replace the YOUR INSTALL TEXT GOES HERE with the Configuration XML data we previously converted.

<SyncML xmlns="SYNCML:SYNCML1.2">
  <SyncBody>
    <Exec>
      <CmdID>7</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>YOUR INSTALL TEXT GOES HERE</Data>
        </Item>
    </Exec>
    <Final/>
  </SyncBody>
</SyncML>

5.3.2. Remove Office CSP

Following is an example of the Remove Office CSP. You can also find these examples here Microsoft Docs - Office CSP.

Replace the YOUR UNINSTALL TEXT GOES HERE with the Uninstall XML data we previously converted.

<SyncML xmlns="SYNCML:SYNCML1.2">
  <SyncBody>
    <Exec>
      <CmdID>7</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>YOUR UNINSTALL TEXT GOES HERE</Data>
        </Item>
    </Exec>
    <Final/>
  </SyncBody>
</SyncML>

5.3.3. Confirm Profile Installation in Workspace ONE UEM

 Confirm Profile Installation in Workspace ONE UEM

In the Workspace ONE UEM Console, navigate to the Device Details page.

  1. Select the Profiles tab.
  2. Select the Office Deployment Profile.
  3. Click Install. 
 Confirm Profile Installation in Workspace ONE UEM
  1. After the policy has been installed, the status turns green. Office will shortly be installed on the device.

6. Summary

You can deploy Office 365 ProPlus in 3 different ways with Workspace ONE UEM.

The following use case explains deploying Office 365 ProPlus as an online installer and offline installer, and deploying Office via MDM Policy. The use case covers prerequisites such as using the Office Customization Tool to ensure only Outlook, Word, Excel, PowerPoint, and Teams are installed; Creating an Office.zip file for scripted install; and then uploading and configuring the deployment settings with Workspace ONE UEM

The VMware Workspace ONE application life cycle flow, also known as software distribution, exists for all internal applications. Use software distribution to deliver Win32 applications, track installation statuses, keep application versions current, and delete old applications.

Notepad Plus Plus (EXE Installer)

Notepad++ is a text and source code editor for use with Microsoft Windows.

For more information on Notepad ++, see https://notepad-plus-plus.org/.

Note: This application is also available as part of the Workspace ONE UEM Enterprise Application Repository.

Deployment Configuration Settings

Workspace ONE UEM Application Settings
Value
Files Tab
Uninstall Command "%ProgramFiles%\Notepad++\Uninstall.exe" /S
Deployment Options Tab
How To Install
Install Context User
Install Command "npp.7.9.1.Installer.x64.exe" /S
Admin Privileges Yes
Device Restart Optional
Retry Count 3
Retry Interval 5
Install Timeout 15
Installer Reboot Exit Code n/a
Installer Success Exit Code n/a
When To Call Install Complete
Identify Application By If File exists:
C:\Program Files\Notepad++\notepad++.exe
Images
Icon See the vendor website: Notepad++ (notepad-plus-plus.org)
Mobile Images See the vendor website: Notepad++ (notepad-plus-plus.org)
Tablet Images See the vendor website: Notepad++ (notepad-plus-plus.org)

Google Chrome (MSI Installer)

Google Chrome Enterprise unlocks the business capabilities of Chrome OS, Chrome Browser, and Chrome devices, freeing IT to power your cloud workforce. Click here to Download Chrome browser for enterprise.

Tip: For Windows policy configuration, see Understanding Windows 10 Group Policies: VMware Workspace ONE Operational Tutorial.

Chrome Enterprise has ADMX settings that can be delivered via Workspace ONE UEM. See Set Chrome Browser policies on managed PCs. To convert the GPOs to MDM Policies, we recommend t use Workspace ONE Airlift. 

For more information on Workspace ONE AirLift, see Modernizing Windows 10 Management: VMware Workspace ONE Operational Tutorial.

Deployment Configuration Settings

Workspace ONE UEM Application Settings
Value
Files Tab
Uninstall Command Uploaded as part of MSI installer
Deployment Options Tab
How To Install
Install Context Device
Install Command msiexec /i "GoogleChromeStandaloneEnterprise64.msi" /qn
Admin Privileges Yes
Device Restart Optional
Retry Count 3
Retry Interval 5
Install Timeout 15
Installer Reboot Exit Code N/A
Installer Success Exit Code N/A
When To Call Install Complete
Identify Application By Uploaded as part of MSI installer
Images
Icon See the vendor website: Chrome browser for enterprise
Mobile Images See the vendor website: Chrome browser for enterprise
Tablet Images See the vendor website: Chrome browser for enterprise

Mozilla Firefox Enterprise (EXE Installer)

Mozilla Firefox, or simply Firefox, is a free and open-source web browser developed by the Mozilla Foundation and its subsidiary, the Mozilla Corporation. Firefox uses the Gecko layout engine to render web pages, which implements current and anticipated web standards.

Download Firefox Extended Support Release (ESR) for Enterprise from the Mozilla website. For more information on Firefox, see https://www.mozilla.org/en-US/firefox/enterprise/.

Note: This application is also available as part of the Workspace ONE UEM Enterprise Application Repository.

Tip: For Windows policy configuration, see Understanding Windows 10 Group Policies: VMware Workspace ONE Operational Tutorial.

Firefox has ADMX settings that can be delivered via Workspace ONE UEM. See Customizing Firefox Using Group Policy (Windows). To convert the GPOs to MDM Policies, we recommend t use Workspace ONE Airlift. 

For more information on Workspace AirLift, see Modernizing Windows 10 Management: VMware Workspace ONE Operational Tutorial.

Deployment Configuration Settings

Workspace ONE UEM Application Settings
Value
Files Tab
Uninstall Command "%ProgramFiles%\Mozilla Firefox\uninstall\helper.exe" -ms
Deployment Options Tab
How To Install
Install Context Device
Install Command "Firefox Setup 78.5.0esr.exe" -ms
Admin Privileges Yes
Device Restart No
Retry Count 3 (default)
Retry Interval 5 (default)
Install Timeout 60 (default)
Installer Reboot Exit Code NA
Installer Success Exit Code NA
When To Call Install Complete
Identify Application By

File exists - %ProgramFiles%\Mozilla Firefox\firefox.exe

Images
Icon See the vendor website:
https://www.mozilla.org/en-US/firefox/enterprise/
Mobile Images See the vendor website:
https://www.mozilla.org/en-US/firefox/enterprise/
Tablet Images See the vendor website:
https://www.mozilla.org/en-US/firefox/enterprise/

7-Zip (MSI Installer)

7-Zip is free software with open source. Most of the code is under the GNU LGPL license.

For more information on 7-Zip, see https://www.7-zip.org/.

Note: This application is also available as part of the Workspace ONE UEM Enterprise Application Repository.

Deployment Configuration Settings

Workspace ONE UEM Application Settings
Value
Files Tab
Uninstall Command Uploaded as part of the MSI
Deployment Options Tab
How To Install
Install Context Device
Install Command msiexec /i "7z1700-x64.msi" /qn
Admin Privileges No
Device Restart No
Retry Count 3 (default)
Retry Interval 5 (default)
Install Timeout 60 (default)
Installer Reboot Exit Code N/A
Installer Success Exit Code N/A
When To Call Install Complete
Identify Application By Uploaded as part of the MSI
Images
Icon See the vendor website:
https://www.7-zip.org/
Mobile Images See the vendor website:
https://www.7-zip.org/
Tablet Images See the vendor website:
https://www.7-zip.org/

Global Protect VPN (MSI Installer)

GlobalProtect is an VPN application that runs on the Windows 10 endpoint to connect to internal resources.

Deployment Configuration Settings

Workspace ONE UEM Application Settings
Value
Files Tab
Uninstall Command Uploaded as part of MSI
Deployment Options Tab
How To Install
Install Context Device
Install Command msiexec /i "GlobalProtect64.msi" /qn
Admin Privileges Yes
Device Restart Optional  
Retry Count 3 (default)
Retry Interval 5 (default)
Install Timeout 60 (default)
Installer Reboot Exit Code 1641
Installer Success Exit Code 0
When To Call Install Complete
Identify Application By Uploaded as part of MSI
Images
Icon See the vendor website
Mobile Images See the vendor website
Tablet Images See the vendor website

Summary and Additional Resources

Conclusion

This tutorial shows you how to use Workspace ONE UEM to manage Windows 10 applications through a series of exercises including finding the install/uninstall commands, deploying applications such as Microsoft Office, Workspace ONE clients, and third-party applications.

Additional Resources

For more information about Workspace ONE, explore the VMware Workspace ONE Activity Path. The activity path provides step-by-step guidance to help you level up in your Workspace ONE knowledge. You will find everything from beginner to advanced curated assets in the form of articles, videos, and labs.

For information about deployment, see Deploying Workspace ONE Intelligence and VMware Carbon Black Cloud: Workspace ONE Operational Tutorial.

Additionally, you can check out the VMware Workspace ONE and VMware Horizon Reference Architecture which provides a framework and guidance for architecting an integrated digital workspace using VMware Workspace ONE and VMware Horizon. 

For more information on Managing Windows 10 Devices with Workspace ONE, see the Understanding Windows 10 Management activity path. The content in this path helps you establish a basic understanding of Windows 10 management in the following categories:

Podcast

Spotify - Digital Workspace TechZone Podcast

Apple Podcasts

Change Log

The following updates were made to this guide.
 

Date Description of Changes
2021-02-11
  • Updated Understanding Application Installation behavior
  • Included information on Enterprise App Repo Twitter Bot - @EntAppRepo 
2020-12-15
  • Added information on enterprise app repository.
  • Added more information on application distribution and architecture.
  • Added Workspace ONE application distribution instructions.
  • Added some third-party application distribution instructions.

About the Authors

This tutorial was written by:

  • Josué Negrón, EUC Staff Architect, End-User-Computing Technical Marketing, VMware.
  • Darren Weatherly, Senior Architect, End-User-Computing Technical Marketing, VMware.
  • Hannah Jernigan, Technical Writer, End-User-Computing Technical Marketing, VMware.

With significant contribution from:

Feedback

Your feedback is valuable. 

To comment on this tutorial, contact VMware End-User-Computing Technical Marketing at euc_tech_content_feedback@vmware.com.

Filter Tags

Workspace ONE Workspace ONE Productivity Apps Workspace ONE UEM Document Operational Tutorial Advanced Windows 10 Deploy Business Continuity Modern Management Office365