Troubleshooting Devices Stuck in "Enrollment in Progress"
Summary
Related SOTI ONE Platform Products
Related Device OS
Issue Description
When attempting to enroll a device as Work Managed after a factory reset, the enrollment process gets stuck at the "Enrollment in Progress" stage after entering the enrollment ID. The new device appears in the web console but remains offline, and the device agent fails to connect.
Additionally, the device logs display the error: "Enrollment Failed to Generate MGPA Token for AE Device".
Symptoms
- After entering the enrollment ID, the device remains stuck at the "Enrollment in Progress" stage.
- The newly enrolled device shows up in the web console but remains in an offline state.
- The device does not proceed beyond the enrollment screen, preventing successful configuration.
Cause
Note: This article is specific to the following scenario.
If the same Google binding account is linked to multiple SOTI MobiControl instances, conflicts occur when generating the Managed Google Play Account (MGPA) token. This prevents the device from enrolling properly, leading to the "Failed to generate MGPA token for AE device" error
Issue Resolution
To successfully enroll the device:
1. Unbind the Google binding account from multiple instances.
2. Link the Google binding account to only one instance, or create a new enterprise binding.
3. Update the existing enrollment policy or create a new one, selecting the newly created binding under Work Managed.
4. Retry enrollment to resolve the issue.
Note: If the issue is not resolved, contact SOTI support.
Workarounds
As a workaround:
1. Edit the existing enrollment policy in SOTI MobiControl and navigate to the Enterprise Binding section.
2. Set Enterprise Binding to "None"
3. Save the changes to complete the enrollment policy configuration.
With this setting, the device is able to successfully enroll as a Work Managed device. With this workaround, the binding will need to be reset via device action to assign a Google binding post enrollment.
Note: This serves as a temporary solution until you can properly unbind the Google binding account from other instances or create a new enterprise binding for a permanent fix.
Was this helpful?
Thanks for your feedback