In AirWatch 9.0.3, the Secure Email Gateway will now be available in a new platform leveraging the AirWatch REST API, in addition to the existing platform leveraging the AirWatch SOAP API. This new "V2 platform" allows for significant performance improvements over the existing application.
This first release of the SEG V2 platform can be easily deployed on an existing SEG server, and can support an existing MEM deployment without any end-user interaction. For information about migrating to the SEG V2 platform, see the Migration section of the Secure Email Gateway guide.
AirWatch recommends migrating to the SEG V2 platform as soon as possible to take advantage of the new improvements, as well as continued improvements over future releases.
Please see the updated Secure Email Gateway guide for more details on upgrade requirements.
Frequently Asked Questions
Q: Will I need a new server for the SEG V2 platform?
A: No, the SEG V2 platform can installed on an existing SEG server with minimal downtime. Please see the Migration section of the Secure Email Gateway guide for details.
Q: Do I need to update any profiles when upgrading to the SEG V2 platform?
A: No profile changes are required.
Q: Is there any end user interaction required after upgrading to the SEG V2 platform?
A: No end user interaction is required.
Q: Does the SEG V2 platform have complete feature parity to the existing SEG Classic platform?
A: Currently a few use-cases are not supported:
- Sync Filter Policy
- Email Classification Security
- Certificate Authentication with KCD
- Google EAS Proxy
For more information, please refer to the complete comparison matrix in the SEG guide.
Q: Can I stay on the existing SEG Classic platform?
A: In AirWatch 9.0.3, the SOAP API SEG application is still available and fully supported. However, AirWatch will primarily focus future improvements into the SEG V2 platform, and we recommend migrating to the new platform as soon as possible.