Seamless Provisioning not triggering on first boot — firmware missing Esper Agent

Android

When a device is pre-registered in the Esper Console but the Esper Agent has not been built into the device firmware by the manufacturer, the device completes its first boot normally without entering the managed provisioning flow.

Why this happens

Seamless Provisioning depends on a copy of the Esper Agent that the device manufacturer bakes directly into the device firmware before shipment. At first boot, that pre-installed Agent detects the device's pre-registration record in the Esper Console and initiates the managed provisioning handshake automatically. If the manufacturer has not integrated the Esper Agent into the firmware, no component exists on the device at first boot to trigger this process — regardless of whether the serial number or IMEI is correctly pre-registered in the Esper Console.

Steps

1. Confirm firmware capability with your device manufacturer. Ask whether an Esper-integrated firmware build exists for your specific device model. If the manufacturer confirms no such build exists, Seamless Provisioning is not supported on that hardware and cannot be enabled after the fact.
2. Remove the pre-registration record from the Esper Console. Navigate to Devices & Groups, locate the pre-registered entry, select Actions, then select Remove Registration. This keeps your Console inventory clean before you reprovision using an alternative method.
3. Choose an alternative provisioning method and reprovision the device. Use one of the following:
   • QR Code Provisioning: Allow the device to reach the Wi-Fi setup screen during the out-of-box experience, connect to a network, then follow the QR code provisioning flow from the Esper Console under Devices & Groups → Enroll Device.
   • ADB Provisioning: Allow the device to complete standard Android setup, enable USB Debugging under Settings → Developer Options, then use the Esper Device Provisioner tool to provision the device over USB. Note that this method requires physical access to each device and is not suitable for automated at-scale deployment.

Verify: After provisioning completes, the device should appear in Devices & Groups with a status of Active or Online within 5 minutes, and the assigned Blueprint should show as applied on the device detail page.

If this doesn't resolve it

If your manufacturer confirms that an Esper-integrated firmware build does exist for your device model but Seamless Provisioning still does not trigger, collect the following before contacting support:

• Device make, model, and firmware version
• The serial number or IMEI used for pre-registration
• A screenshot of the pre-registration record in Devices & Groups
• Written confirmation from your device manufacturer that the Esper Agent is present in the firmware build installed on the device
• The Activity Feed log from the device entry, if one exists in the Esper Console

Contact Esper Support with these details so the issue can be investigated further.

Still need help?

If provisioning still isn't triggering on first boot, submit a support ticket and include your device model, firmware version, and whether the Esper Agent appears in your device's app list after boot.