Pull service based relay servers periodically contacts the AirWatch Console to check for new products, profiles, files, and actions, and applications assigned to devices under the pull relay servers purview. Configure a pull server to deliver content to devices without excessive bandwidth use.

If you make changes or additions, the server will create an outbound connection to the AirWatch Console to download the new content to the server before pushing it to its devices. Pull service is best used when traversing any NAT firewall or SaaS to on-premises hybrid environments because SaaS customers typically do not want the service to tie-up bandwidth when content is delivered from AirWatch to the store server.

To create a pull relay server, you must first have an FTP, Explicit FTPS, or SFTP server to function as the relay server. FTP(S) servers must be compliant with RFC 959 and RFC 2228 set by the Internet Engineering Task Force. The instructions below detail how to create a pull relay server from an Explicit FTP(S) server.

Important:

The ports you configure when you create your FTP, Explicit FTPS, or SFTP server must be the same ports you enter when creating a relay server in the AirWatch Console. AirWatch does not support Implicit FTPS relay servers.

This process covers the installation of one server at a time. For bulk installation, you must use a third-party application. AirWatch supports importing servers in bulk through the Bulk Import option. See Import Relay Servers in Bulk for more information.