The AirWatch Managed and Personal Content repositories store content in the AirWatch database by default. However, on-premise customers have the option to use Local File Storage as an alternative to the AirWatch database. This can help address concerns about database performance. You can also use file storage to store internal apps. Customers using the software distribution feature for Windows applications must set up a file storage server.

To implement Local File Storage, meet the requirements and set the appropriate configurations in the AirWatch Console:

  1. Navigate to Groups & Settings > All Settings > Installation > File Path and scroll to the bottom of the page.
  2. Select File Storage Enabled and configure the settings.

    Setting Description
    File Storage Path Enter your path in the following format: \\{Server Name}\{Folder Name}, where Folder Name is the name of the shared folder you created 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 opposed to retrieving the file from the file storage server each time the file is requested. If you enable caching, you must allocate the amount of space needed on the server to cache these files. If you are caching internal apps, then it is recommended to size the cache for 120 percent of the cumulative size of all the apps you need to publish.

    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, see VMware AirWatch CDN Integration Guide available on AirWatch Resources.

    File Storage Impersonation Enabled Select to add a service account with the correct permissions.
    File Storage Impersonation Username Provide a valid service account with both read and write permissions to the shared storage directory.
    Password Provide a valid service account with both read and write permissions to the shared storage directory.