To deploy Win32 applications with the software distribution, use supported file types, operating systems, and platforms.

Supported Platforms

The supported platform to deploy Win32 Applications is Windows Desktop.

Supported File Types

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

CDNs and File Storage Systems

It is considered to be a best practice to use content delivery network (CDN) to deploy applications. This option has the advantage of sending content to devices in the network and to remote devices. It also offers increased download speeds and reduces bandwidth on Workspace ONE UEM servers. However, in some scenarios, a CDN is not a viable option. For these instances, use a file storage system.

Enable Software Package Deployment - SaaS Environments

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

For the Software Package Deployment option to display, Workspace ONE UEM enables the CDN for the environment. Go to Groups & Settings > All Settings >  Device & Users > Windows > Windows Desktop > App Deployments and enable Software Package Deployment.

Note: If your deployment whitelists Workspace ONE UEM IP addresses, the CDN does not work.

Enable Software Package Deployment - On-premises Environments

Software distribution is now turned on by default in the Workspace ONE UEM console for all on-premises customers. By default, customers get up to 5 GB of storage for applications in the database. For storing large Win32 applications, you can use a file storage system.

It is considered to be a best practice to use the content delivery network (CDN) to deploy applications. This option has the advantage of reducing the bandwidth on other servers.

File Storage for your Win32 Applications

Certain functionality in Workspace ONE UEM powered by AirWatch uses a dedicated file storage service to handle processing and downloads, which reduces the overall burden on the database and improves performance. Configuring file storage manually is only applicable to on-premises customers. It is configured automatically for SaaS customers. It also includes certain reports, internal application deployment, and Workspace ONE UEM-managed content. When you enable file storage for any of these functionalities, it is applied to the others automatically. Setting up file storage causes all reports, all internal applications, and all managed content to be stored there.

As of console version 9.0.2, three new reports were added that appear the same as existing reports but use a revamped back-end framework. This new framework generates reports with greater reliability and faster download times. To take advantage of these benefits, you must set up file storage.

For more information about the new reports, see Workspace ONE UEM Reports Overview.

When file storage is enabled, all internal application packages that you upload through the UEM console are stored in a file storage location.

File storage is required to deploy Win32 applications (IPA, PAK, APPX, MSI, EXE, and so on) and macOS applications (DMG, PKG, MPKG, and so on) from the Resources area of the UEM console. This feature is called software distribution.

For more information about software distribution for Win32, see Distribution of Win32 Applications.

For more information about software distribution for macOS, see Software Distribution and Management.

You can separate the managed content from the Workspace ONE UEM database by storing it in a dedicated file storage location. Uploading large amounts of managed content might cause issues with database performance. In this case, on-premises customers can free up space in the database by moving the managed content to an integrated local file storage solution.

For more information about the managed content, see AirWatch Managed Content Repository .

Configure File Storage for your internal Win32 Applications

Configure file storage for internal applications using the procedure below. This is required if you are deploying Win32 apps using software distribution, but applies to all internal applications once configured.

If you have managed content taking up space in the database, Workspace ONE UEM offers you dedicated file storage. To set up file storage, you must determine the location and storage capacity, configure network requirements, and create an impersonation account. Read through the following prerequisites before you get started:

Verify the File Storage connectivity from your servers:

  1. Make sure that the file path is reachable from all the Console and DS boxes uses the same impersonation credentials defined in the UEM console when configuring File Storage.
  2. When using DFS share, if the FS path is configured using FQDN the root must be accessible from all Console and DS nodes. For example, if the file path configured in the File Storage is //india.vmware.com/MDM/FileStorage/, make sure that the DS has access to the root//india.vmware.com/
Create the shared folder on a server in your internal network:
  1. File storage can reside on a separate server or the same server as one of the other Workspace ONE UEM application servers in your internal network. It is only accessible to components that require access to it, such as the Console and Device Services servers.
  2. If the Device Services server, Console server, and the server hosting the shared folder are not in the same domain, then supply the domain when configuring the service account in the format <domain\username>. Domain Trust can also be established to avoid an authentication failure.
Configure the network requirements:
  1. If using Samba/SMB – TCP: 445, 137, 139. UDP: 137, 138
  2. If using NFS – TCP and UDP: 111 and 2049

Allocate sufficient hard disk capacity:

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. Take into the account the following considerations.

  1. If you enable caching for internal applications or content, then a best practice is to size the Device Services server for 120 percent of the cumulative size of all the apps/content you must publish.
  2. For storing reports, your storage requirements depend on the number of devices, the daily number of reports, and the frequency with which you purge them. As a starting point, allocate at least 50 GB for deployment sizes up to 250,000 devices running about 200 daily reports. Adjust these numbers based on the actual amount you observe in your deployment. Apply this sizing to your Console server as well if you enable caching.
Create a service account with correct permissions:
  1. Create an account in the domain of the shared storage directory.
  2. Give the local user read/write/modify permissions to the file share that is being used for the File Storage Path.
  3. Configure File Storage Impersonation User in Workspace ONE UEM with the domain account in the format <domain\username>.
  4. If the shared storage directory is not on a domain, create an identical local user and password on the server being used for File Storage, Console, and Device Services server. In this case, supply the local user account in the format <username>.

Configure the file storage at the global organization group:

  1. Configure file storage settings at the Global organization group level in the UEM Console. When file storage is enabled, you can configure an external repository in which files are stored. A disabled setting means that files are stored as binary large objects in the database.
  1. At the Global organization group level, navigate to Groups & Settings > All Settings > Installation > File Path and scroll to the bottom of the page.
  2. Select the File Storage Enabled slider and configure the settings.
    Setting Description
    File Storage Path Enter the path files are to be stored in the following format: \\{Server Name}\{Folder Name}, where Folder Name is the name of the shared folder you create on the server.
    File Storage Caching Enabled

    When enabled, a local copy of files requested for download is stored on the Device Services server as a cache copy. Subsequent downloads of the same file retrieve it from the Device Services server as opposed to file storage.

    When enabled, files are cached locally on the DS server when accessed for the first time. Subsequent requests are served using the file cached on the DS server instead of streaming from the file storage location.

    If you enable caching, consider accommodating for the amount of space needed on the server.

    If you integrate with a CDN, then apps and files are distributed through the CDN provider, and a local copy is not stored on the Device Services server. For more information, refer to the VMware Workspace ONE UEM CDN Integration Guide (https://resources.air-watch.com/view/8cr52j4hm6xfvt4v2wgg/en).

    File Storage Impersonation Enabled Select to add a service account with the correct permissions.
    File Storage Impersonation Username Provide a valid service account user name to obtain both read and write permissions to the shared storage directory.
    Password Provide a valid service account password to obtain both read and write permissions to the shared storage directory.
  3. Select the Test Connection button to test the configuration.