Installing via self-enrollment domains in the Play Store does not sync to my MDM solution
Article ID: 185976
Updated On:
Products
Endpoint Protection Mobile
Issue/Introduction
You have a Mobile Device Management(MDM) solution integrated with SEP Mobile and have allowed users to install via the Play Store with self-enroll domains. But after you successfully install SEP Mobile, the device entry does not appear sync-ed to your MDM solution.
Cause
Sometimes two devices entries are created:
One device entry will install fine but not be sync-ed with the MDM. The 2nd device entry will be sync-ed with the MDM solution but showing installation health errors.
Resolution
Please review tech doc Self-enrollment scenarios, relevancy, configurations, and implications
Installing via the play store is considered an enrollment for an "unmanaged device". You have to enroll the device via the MDM solution to have a "managed device" enrollment process. That is why once a MDM solution is integration to the SEP Mobile console, administrators have the option to turn off enrollments via the play store.
As the two device entries are considered two separate devices at this point in time, merging the devices is not a solution. Users/Admins must delete these two entries and push the app via the MDM for a proper Managed Device enrollment process.
Installing via the play store is considered an enrollment for an "unmanaged device". You have to enroll the device via the MDM solution to have a "managed device" enrollment process. That is why once a MDM solution is integration to the SEP Mobile console, administrators have the option to turn off enrollments via the play store.
As the two device entries are considered two separate devices at this point in time, merging the devices is not a solution. Users/Admins must delete these two entries and push the app via the MDM for a proper Managed Device enrollment process.
Feedback
Yes
No
Powered by
