In the PowerShell model, AirWatch adopts a PowerShell administrator role and issues commands to the Exchange ActiveSync (EAS) infrastructure to permit or deny email access based on the policies defined in the AirWatch Console. PowerShell deployments do not require a separate email proxy server and the installation process is simpler.
PowerShell deployments are for organizations using Microsoft Exchange 2010,2013,2016, or Office 365.
In the setup, where Office 365 the cloud email server is used, the AirWatch server sets up the PowerShell session directly with the email server.
In the setup, where the AirWatch server is on the cloud and the Exchange server is on premise, AirWatch server issues the PowerShell commands. The VMware Enterprise Systems Connector sets up the PowerShell session with the email server.
When both the AirWatch server and the email server are on premise, the AirWatch server sets up the PowerShell session directly with the email server. Here, there is no VMware Enterprise Systems Connector server required unless the AirWatch server cannot communicate with the email server directly.
For more information on how to configure the PowerShell Model, see PowerShell Architecture.
For assistance in choosing between the Secure Email Gateway and PowerShell deployment models, see AirWatch Recommendations.