To deploy the reports storage solution, ensure that your server meets the requirements.
Create the Shared Folder on a Server in your Internal Network
- Report storage can reside on a separate server or the same server as one of the other AirWatch application servers in your internal network. Ensure only the components that require access to the server can access the report storage server, 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 establish Domain Trust between the domains to avoid an authentication failure. If the Device Services or Console servers are not joined to any domain, then supplying the domain during service account configuration is sufficient.
Configure Reports Storage at the Global Organization Group
Configure reports storage settings at the Global organization group level in the AirWatch Console.
Create a Service Account with Correct Permissions
- Create an account with read and write permissions to the shared storage directory.
- Create the same local user and password on the Console, Device Services, and the server that is being used for report storage.
Give the local user read/write/modify permissions to the file share that is being used for the Report Storage Path.
If you give the user modify permission, AirWatch automatically deletes old reports from the storage. If you do not give the user modify permissions, consider monitoring report storage to prevent running out of space.
- Configure the Report Storage Impersonation User in AirWatch with the local user.
You can also use a domain service account instead of a local user account.
Allocate Sufficient Hard Disk Capacity
Your specific storage requirements may vary depending on how you plan to use reports storage. Ensure that the reports storage location has enough space to accommodate the reports you intend to use.
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, plan to 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. Also apply this sizing to your Console server if you enable caching.