Certain functionality in Workspace ONE UEM 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.

Internal Applications

When you enable file storage, all internal application packages that you upload through the Workspace ONE 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 Workspace ONE UEM console. This feature is called software distribution.

Workspace ONE UEM Managed Content

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.

File Storage Requirements for your Win32 Applications

If you have a lot of 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.
Important: File Storage is required for Windows Software Distribution.

Create the Shared Folder on a Server in Your Internal Network

  • 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 Device Services, Console, and API servers.
  • If the servers hosting Device Services, Console, & API servers, 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

  • If using Samba/SMB – TCP: 445, 137, 139. UDP: 137, 138
  • 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.

  • 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.
  • 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

  • Create an account in the domain of the shared storage directory.
  • Give the local user read/write/modify permissions to the file share that is being used for the File Storage Path.
  • Configure File Storage Impersonation User in Workspace ONE UEM with the domain account in the format <domain\username>.
  • 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, Device Services, Console, and API servers. In this case, supply the local user account in the format <username>.

You can also use a domain service account instead of a local user account.

Configure File Storage at the Global Organization Group

Configure file storage settings at the Global organization group level in the Workspace ONE UEM Console.

Enable File Storage for Reports

Before you can enjoy the benefits of reports file storage in Workspace ONE UEM, you must enable and configure file storage.

  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.

    When file storage is enabled, you can configure an external repository in which files are stored. A deactivated setting means that files are stored as binary large objects in the database.

    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

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

    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.