In the AirWatch console, the MEM dashboard is used to identify all devices targeted under a MEM configuration, and to display whether each device has been allowed or blocked access to email. Depending on the type of MEM deployment, this page will update at different intervals. This article will describe what updates to expect for the different deployment types.
A SEG deployment will provide real-time updates as devices make email requests through the SEG server. In the MEM Advanced Configuration page on the AirWatch Console, the SEG can be configured to provide updates only for certain types of transactions. By default, the SEG will not show an update if a device performs a sync or ping, but it will send an update if the device performs any other transaction.
A PowerShell deployment will provide updates when AirWatch initiates an action against a particular device. This can include a new device being enrolled and whitelisted, or a device being marked as non-compliant and blacklisted. With this deployment, updates are not based on device requests, but rather on AirWatch-initiated PowerShell commands.
Google Apps for Work
Google Apps for Work deployments will see different behavior for the different implementations possible.
- Direct integration using password management with retention - With this deployment, the dashboard will update when devices are enrolled, or when Run Compliance is selected from the console.
- Direct integration using password management without retention - With this deployment, the dashboard will not update.
- Direct integration using directory APIs - With this deployment, the dashboard will update when devices are enrolled, when a device changes its compliance status, and when it is unenrolled.
- SEG proxy - For deployments utilizing a SEG, updates will be reported based on device traffic (see the SEG section above).