Device enrollments, assignment of email profiles to devices, and change in the device compliance status impacts Mobile Email Management (MEM). MEM configurations are assigned to devices based on the EAS profiles present on the devices. The Managed and Require ActiveSync Profile compliance policies ensures that unmanaged and manual configurations remain unpermitted.
Devices with Exchange Active Sync (EAS) profile
When a device with an EAS profile associates to a particular MEM configuration, Workspace ONE UEM sends policy updates to that MEM configuration. This feature facilitates migrations and multiple MEM configurations where one or more email environments are managed.
Regardless of the email client, all Google MEM models require an EAS profile. For new installs, associating an EAS profile to a MEM configuration is mandatory. For upgrades, an admin has to associate an EAS profile to the MEM configuration upon completion of the upgrade process.
SEG Proxy Integrated
Workspace ONE UEM sends a broadcast message to all the MEM configurations of the organization group to which the device has enrolled. This message states the compliance status of the device. When compliance changes, an updated message is sent. When the device connects to a particular SEG server, the SEG recognizes the device from the broadcast message sent earlier. The SEG Proxy then reports the device as discovered to VMware AirWatch. Workspace ONE UEM then associates the device with the MEM Configuration for SEG and displays it on the Email Dashboard.
If multiple SEG servers are load balanced, single policy broadcast messages apply to only one SEG. This includes the messages sent from the UEM Console to SEG upon enrollment, compliance violation, or correction. Use Delta Sync with a refresh interval of ten minutes to facilitate newly enrolled or compliant devices. These devices experience a waiting period of maximum ten minutes before email begins to sync.
- Updated policies from the same API source for all SEG servers.
- Smaller performance impact on API server.
- Reduced implementation or maintenance complexity compared to the SEG clustering model.
- Fewer failure points as each SEG is responsible for its own policy sets.
- Improved user experience.
SEG Clustering is also available to facilitate the sharing of single policy updates to all nodes of a SEG cluster. For information about SEG clustering for the Classic platform, see Classic Platform Clustering FAQs
PowerShell MEM configurations behave the same as SEG in terms of policy updates. For migrations to PowerShell, it is important that new profiles are associated to the PowerShell MEM configuration. Associating a new profile reduces unnecessary communication with the previous MEM configuration.
Profiles are required for this type of deployment except when integrating with Google Directory APIs. Unless the devices are provisioned with the profiles, the configured Gmail deployment does not identify or manage the device.