Seamless Provisioning Stalls on "Configuring System" Screen: Remove Applications from Blueprint to Unblock Enrollment

Android

Improved Title: Provisioning stalls on "Configuring system" screen — remove apps from Blueprint

---

When a device is provisioned using Seamless Provisioning (Android Enterprise Device Owner or EMM token method) and the assigned Blueprint includes applications, the device may download and install the Esper Agent but then freeze on the Configuring system screen and never appear as enrolled in the Esper Console.

Why this happens

During Seamless Provisioning, the device must complete application installation as part of the enrollment handshake. If any application in the Blueprint fails to download or install — due to network conditions, an incompatible APK, or a timing issue in the provisioning flow — the device stalls waiting for that step to complete and enrollment never finalises.

Step 1: Create an empty Blueprint

1. Open the Esper Console and navigate to Blueprints → Create New Blueprint.
2. Set the mode to Multi App Mode.
3. Do not add any applications to this blueprint. Removing apps eliminates the installation step that is blocking enrollment.
4. Save the blueprint.

Step 2: Assign the empty Blueprint and re-provision

1. Assign the empty blueprint to the provisioning template or device group you are using for this device. This ensures the next provisioning attempt uses the app-free configuration.
2. Factory reset the device to clear any incomplete enrollment state.
3. Re-initiate provisioning using the QR code or EMM token linked to the empty blueprint.

Verify: The device should pass through the Configuring system screen without stalling and appear as Online under Devices & Groups within a few minutes of completing provisioning.

Step 3: Apply your production Blueprint after enrollment

Once the device is enrolled and showing as online, add your applications back through a Blueprint update rather than during provisioning.

1. Navigate to Devices & Groups → [Device Name] → Blueprints.
2. Select your production blueprint — the one that includes all required applications.
3. Apply the blueprint and monitor the device under Activity Feed to confirm all applications install successfully.

If this doesn't resolve it

If the device still stalls on Configuring system after provisioning with an empty blueprint, the issue is likely at the firmware or GMS certification level rather than in the Blueprint configuration. Take the following steps before contacting support:

• Capture a bug report from the device immediately after the stall occurs. The Esper Agent logs captured at that moment are critical for diagnosis. For instructions, see Capturing Bug Reports.
• Confirm with your device OEM that the specific firmware build is GMS-certified and fully supports Android Enterprise Device Owner enrollment.
• Ask your OEM whether preloading the Esper Agent is a supported alternative enrollment path for non-GMS images.

If you have completed all steps above and the device still will not enroll, contact Esper Support and attach the bug report so the team can analyse the Esper Agent logs directly.

Still need help?

If your devices continue to stall on the "Configuring System" screen after removing applications from your Blueprint, submit a support ticket and include your Blueprint configuration, the list of applications you removed, and your device logs from the enrollment attempt.