The Mobile Email Management (MEM) server manages the enrolled devices that are assigned to the configured Mobile Email Management (MEM) environments. Devices with Exchange Active Sync (EAS) profile are automatically assigned to MEM configurations and those without EAS profiles are assigned by AirWatch using the auto discovery process.
Devices with Exchange Active Sync (EAS) profile
The already enrolled devices are automatically assigned to a specific Mobile Email Management (MEM) deployment based on the EAS profile. The MEM server then starts managing these assigned devices. When a new device enrolls with an EAS profile, AirWatch sends a policy update to the configured MEM to start managing the device. AirWatch then displays the memconfigID for this device on the Email Dashboard.
Regardless of the email client, all Gmail models require an EAS profile. For new installs, associating an EAS profile is mandatory. For upgrades, an admin has to associate an EAS profile to the MEM configuration upon completion of the upgrade process.
Devices without Exchange Active Sync (EAS) Profile
When a new device enrolls without having an EAS profile associated to it, the assignment of Mobile Email Management (MEM) for this device happens based on the auto discovery process, in which AirWatch attempts to discover a MEM deployment for the device. For each integration type, this assignment varies.
Device Assignment for SEG Proxy Configuration
After a device enrolls to an organization group, AirWatch sends a broadcast message to all the configured Secure Email Gateway Proxy servers of the organization group. This message states that a device has enrolled. When the device connects to a particular SEG server, the SEG recognizes the device and reports the device as discovered to AirWatch. The SEG Proxy then reports the device as discovered to AirWatch. AirWatch then associates the enrolled device to that memConfigID 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 AirWatch 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 up to ten minutes before email begins to sync. Benefits of this approach include:
- 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 more information on how to configure SEG clustering for the Classic platform, see Classic Platform Clustering FAQs
Device Assignment for PowerShell Configuration
AirWatch sends an 'Allow' command to all the PowerShell integrated environments. AirWatch automatically associates the device to the corresponding memConfigID for the environment that the command succeeds against.
Device Assignment for Gmail Configuration
Profiles are required for this type of deployment except when integrating with Directory APIs. Unless the devices are provisioned with the profiles, the configured Gmail deployment cannot identify and manage the device.