Device Enrollment Failures When SOTI.net Is Down
Summary
Related SOTI ONE Platform Products
Related Device OS
Situation
Customers may report that Android Enterprise or Work Managed device enrollments are failing across multiple device types.
Common symptoms include:
- Enrollment fails during device provisioning
- Devices remain stuck during setup
- Errors such as:
- “Failed - Resetting device”
- “Cannot download device policy”
- “Enrollment failed”
- Multiple devices impacted simultaneously
- Existing enrolled devices may continue functioning normally
This issue is commonly observed during a SOTI.net outage.
Environment
This issue may affect:
- Android Enterprise (Work Managed) enrollments
- QR code-based enrollment methods
- Stage Programmer enrollment workflows
- Any enrollment configuration using the static agent URL:
http://soti.net/apk/ae2
Affected components may include:
- SOTI MobiControl
- Android Enterprise
- SOTI Stage Programmer
- QR code enrollment configurations
Process Description
The standard static Android Enterprise agent URL: http://soti.net/apk/ae2 is hosted through SOTI.net infrastructure.
When SOTI.net is unavailable, devices cannot download the required SOTI MobiControl agent APK during enrollment. As a result, enrollment provisioning fails.
Workaround
Replace the static agent URL in the QR code configuration with a direct download link.
Example download link: https://downloads.soti.net/apk/AEAgent/GoogleMobiControl-2024.0.0.1005.apk
Steps
1. Identify the enrollment QR code configuration currently being used: http://soti.net/apk/ae2
2. Replace the agent APK URL with the download URL appropriate for the customer’s MobiControl version.
3. Regenerate the enrollment QR code if required.
4. Retry device enrollment.
5. Confirm that the device successfully downloads the agent and completes enrollment.
Verification and Validation
After applying the workaround:
- Scan the updated QR code on a test device.
- Confirm the APK downloads have been successful.
- Verify that:
- Device provisioning completes
- The device enrolls in SOTI MobiControl
- The device appears in the console
- Required Android Enterprise policies apply correctly
If enrollment succeeds using the download URL, the issue is confirmed to be related to the SOTI.net outage affecting the static agent link.
Was this helpful?
Thanks for your feedback