This issue affects on-premise environments that have enabled File Storage in the AirWatch Console.AirWatch application servers (such as the Console and Device Services) are unable to authenticate against the File Storage server using Windows authentication if it is on a separate domain or if the AirWatch application servers are not on a domain. For example, if the AirWatch Device Services server is in the DMZ with no domain, and the File Storage server is in an internal server on domain, the DS server will not be able to authenticate properly.
This can lead to functionality issues in the Console or with devices where File Storage is used. For example, if a DS server is unable to authenticate to File Storage, then devices will not be able to successfully install internal applications that have been deployed. Likewise, if the Console cannot authenticate to File Storage, then administrators will not be able to successfully run reports.
This has been resolved in AirWatch 9.1.