After configuring the PowerShell on AirWatch server, enable PowerShell integration through MEM on the AirWatch Console to control and manage a remote Exchange instance.
To enable PowerShell integration:
- Navigate to Email > Settings in the AirWatch Console and select Configure. The Add Email Configuration wizard form displays.
In the Platform wizard form:
- Select Direct as the Deployment Model.
- Select Exchange as the Email Type and Exchange 2010/2013/2016 or Office 365 as the Exchange Version. Select Next.
- In the Deployment wizard form:
|Friendly name||Enter a friendly name for the PowerShell deployment. This name gets displayed on the MEM dashboard screen for devices managed by PowerShell.|
|PowerShell URL||Enter the PowerShell URL which is the PowerShell instance on the email server in relation to the AirWatch Server. Typically, the PowerShell URL is in the form of https://<emailserver>/powershell.|
|Ignore SSL errors between AirWatch and Exchange server||
Select Enable to Ignore SSL Errors to allow devices to ignore Secure Socket Layer (SSL) certificate errors between AirWatch and Exchange server.
AirWatch recommends that a valid SSL trust should always be established between AirWatch and Exchange server using valid certificates.
|Use Service Account Credentials||Select Enable to to use the credentials from the Cloud Connector Application Pool as the Service Account for PowerShell connections.|
Select the authentication type based on the Exchange Server settings. The options available are:
Enter the username of the PowerShell Service Account if the Use Service Account Credentials option is not enabled.
|Admin Password||Enter the password of the PowerShell Service Account if the Use Service Account Credentials option is not enabled.|
|One time sync after configuration||Select Enable to enable this option to sync with PowerShell soon after configuration.|
|Limit sync results by||
You may restrict the sync action to certain filtered groups by choosing the options:
- Select Next. The Profiles wizard form displays.
- This is an optional step. If you plan to migrate the users from an existing MEM configuration then associate a profile with the MEMconfiguration.
- Select Next. The MEM Config Summary form provides a quick overview of the basic configuration you have just created for the PowerShell deployment. Save the settings.
- You may select the Add option from the Mobile Email Management Configuration main page to configure more deployments.
- Optionally, you can configure the Advanced Settings. To do this, navigate to Email > Settings page and then select the icon.
Setting Description PowerShell Sync Batch Size
The batch size determines the number of CasMailbox and ActiveSyncDevice/MobileDevice objects returned per PowerShell session when using the Sync Mailboxes or Run Compliance features.
The batch size depends on whether VMware Enterprise Systems Connector or Enterprise Integration Service (EIS) is being used. For VMware Enterprise Systems Connector and direct connection AirWatch recommends 25000 devices and for EIS 2500 devices. The PowerShell MEM config detects these conditions and sets the batch size accordingly.
Manage Active Sync for Mailbox
Select to enable control of Active Sync at the Mailbox Identity level.
In proper deployments, this is not necessary as a Global Access State of Block or Quarantine is in use.
Remove ActiveSync Partnership on Unenroll
Select to remove partnership of the unenrolled device from Exchange.
This will remove unenrolled devices from Exchange when they are removed from AirWatch.
Sync with entire forest in AD
Select to add the viewEntireForest option to the PowerShell session.
This may be helpful depending on how your company’s Organization Groups are structured.