Consider the following when setting up load balancing for AirWatch components deployed on premises.

  • You can configure load balancers with an algorithm of your choosing. AirWatch supports simple algorithms such as Round Robins and more sophisticated ones such as Least Connections.
  • The following are some examples for configuring persistence for each of the following components:
    • Device Services: Session persistence timeout of 20 minutes is required based on the default configuration of AirWatch.

      If the Enrollment Session Timeout values are modified in AirWatch Console Settings, then you must set the Persistence Timeout values to the same value.

    • Admin Console: Session persistence timeout of one hour is required based on the default configuration of AirWatch.

      If the Idle Session Timeout values are modified in the AirWatch Console Settings, then you must set the Persistence Timeout values to the same value.

    • Secure Email Gateway: Session persistence timeout value for the Secure Email Gateway must be the same as the persistence timeout value for your Exchange ActiveSync Servers based on recommendations from the Mail Solution vendor.
    • Mail (EAS) Servers: Follow the recommendations from your load balancer and mail environment vendors to configure the load balancer in front of one or more EAS servers when using one or more SEGs. In general, AirWatch does not recommend using IP-based persistence when using one or more SEGs.
  • AirWatch recommends load balancers to redirect all HTTP requests to HTTPS.