Certain functions in Workspace ONE UEM use a dedicated file storage service to handle processing and downloads, reducing the overall burden on the database and improving performance.
Configure file paths by navigating to .
The file path settings page contains predefined values. You should not change them unless instructed to do so byWorkspace ONE UEM.
What can you do with the Workspace ONE UEM File Path settings page?
- Connect Workspace ONE UEM to specific files and File Path folders used by Workspace ONE UEM services.
- Configure the File Storage settings which lets you access apps and content from a file storage server instead of the database to improve performance. You can enter the file server details and credentials for the Workspace ONE UEM console to authenticate with the server.
- Configure file storage manually for on-premises customers only. It is configured automatically for SaaS customers.
- Configure certain reports, internal application deployment, and Workspace ONE UEM managed content. When you enable file storage for any of these functions, 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.
Determine your Organizational group hierarchy
Before you review and modify settings, understand the two types of inheritance/override options for the organization group hierarchy available at the top and bottom of the settings page and determine your choices. For more information about these settings, see Override Versus Inherit Setting for Organization Groups.
- Current Setting – Select whether to Inherit or Override the displayed settings. Inherit means use the settings of the current organization group's parent OG, while Override enables the settings for editing so you can modify the current OG's settings directly.
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.
Workspace ONE UEM Reports
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.
Internal Applications
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 Software Distribution of Win32 Applications.
For more information about software distribution for macOS, see Software Distribution of macOS Applications.
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.
For more information about the managed content, see Introduction to Mobile Content Management.
File Storage Requirements for your Win32 Applications
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 the Console and Device Services servers.
- 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.
- 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 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, Console, and Device Services server. 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 UEM Console.
Enable File Storage for Content
You can configure the file storage to store your managed content.
- At the Global organization group level, navigate to and scroll to the bottom of the page.
- 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 disabled 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. - Select the Test Connection button to test the configuration.
