Mobile Access Gateway had been rebranded as AirWatch Tunnel since AirWatch 8.2. From AirWatch 8.3, the configuration settings for AirWatch Tunnel has been split into two components - Content Gateway and AirWatch Tunnel (Proxy and per-app VPN).
Content Gateway settings have been moved from the Enterprise Integration section (Settings > System > Enterprise Integration > AirWatch Tunnel) to the Content section (Setting > Content > Content Gateway) of the console. This change will help us streamline configuration in the console for Content with all Content-related settings in one place. Both these components will have separate configuration pages and an associated installer.
If AirWatch Tunnel with Content configuration were already setup in the console, then Content Gateway settings (Settings > Enterprise Integration > AirWatch Tunnel) will be automatically migrated to the new Content Gateway Configuration page (Settings > Content > Content Gateway). If Tunnel was not previously configured, make sure to click on “Enable” to enable the content gateway and to get the associated content specific settings. Also, reconfiguring the Content gateway settings is not required for this scenario.
Tunnel Only deployment - If AirWatch Tunnel is setup without the Content configuration, then the AirWatch Tunnel software can be updated by downloading & running the installer from Settings > Enterprise Integration > AirWatch Tunnel. Configuration of Content Gateway would not be required.
Content only deployment - If the setup is only for Content without the use of AirWatch Tunnel, then the Content Gateway can be upgraded by downloading & running the installer from Settings > Content > Content Gateway. Configuration of AirWatch Tunnel would not be required.
Windows Deployment upgrades - Best practices
To ensure the mapping between AirWatch Tunnel on Windows (Windows MAG) and Content Gateway to be removed correctly while performing an upgrade, make sure to upgrade Windows Mobile Access Gateway before installing the content gateway software. Please note that upgrade of Windows MAG will remove the content functionality. Content functionality would not be working for a brief amount of time until the content gateway software is installed on the server. For further queries about the upgrade process, please refer to the Windows Mobile Access Gateway installation guide available at http://resources.air-watch.com.
After the above step, click on the Windows installer link on content gateway settings and run the software on the server or servers according to the configuration type (Basic or Relay/Endpoint)
AirWatch Mobile Access Gateway and AirWatch Content Gateway should show up as independent products in the Control panel after the upgrade. Both services can be installed on the same server and would not need any additional hardware requirements. AirWatch Content Gateway can also be installed on a separate Windows server if required.
Linux Deployment upgrades - Best practices
Similar to a Windows deployment, make sure to upgrade AirWatch Tunnel on Linux before installing content gateway to remove any mapping between AirWatch Tunnel and Content Gateway. Please note that upgrade of AirWatch Tunnel will remove the content functionality. Content functionality would not be working for a brief amount of time until the content gateway software is installed on the server. For further queries about the upgrade process, please refer to the Tunnel installation guide available at http://resources.air-watch.com.
After the above step, click on the Linux installer link on content gateway settings and run the software on the Linux server or servers according to the configuration type (Basic or Relay/Endpoint)
Functionality of each of the components – per-app tunnel (Vpnd), Proxy and Content Gateway remains the same. End users should not be seeing any change in the behavior after the upgrade.
If you are using an earlier version of AirWatch Tunnel/MAG with Content functionality configured while the AirWatch Console Version is 8.3, Content gateway will be enabled automatically and Content specific settings would be migrated to the Content gateway section of the console. All services would be working as expected and would not warrant an AirWatch Tunnel or Content Gateway upgrade.