Device Enrollment Troubleshooting
2 min read
This guide provides troubleshooting steps when device enrollment into Android Edge fails. It covers common issues such as QR code scanning errors and devices not responding after enrollment.
QR Code Scanning Issues #
QR code scanner does not pop up during enrollment. #
- Ensure the device is a GMS device.
- Verify the device is running Android 7.0 or above.
Wrong QR code being scanned. #
- Confirm that you are scanning the Staging QR code, not the Enrollment ID.
Device Not Responding After Enrollment #
Device does not sync or check-in after enrollment #
- As part of Best Practices, re-enroll the device into a Staging Fleet without assigning any profiles.
- Then, allow the device to fully enroll and successfully check-in with the console before moving it into the production profile.
Remote Debugging #
If all else fails and the issue persists, please contact your support personnel. They will arrange a remote debugging session for your device.
Before the session, please prepare the following:
- Set up AnyDesk on the remote debugging laptop.
- Download Vysor on the remote debugging laptop.
- Connect the target device to the laptop:
- Ensure Developer Options and USB Debugging are turned on.
- Turn on Vysor on the laptop.
- Prepare the ADB Package on the laptop
Best Practices & Tips #
- Staging Enrollment First: Always enroll devices into a staging fleet without profiles to confirm successful enrollment before assigning production policies.
- Use the Correct QR Code: Ensure you are scanning the Staging QR code during initial setup, not the Enrollment ID.
- Use Data-Capable Cables: Avoid charge-only USB cables; always use cables that support data transfer for reliable enrollment.
- Confirm Device Compatibility: Double-check that the device is GMS-certified (for GMS enrollment)
- Re-Check After Enrollment: If a device does not sync immediately, re-enroll it into staging and confirm a successful check-in before moving it to production.
