Deploy apps, manage devices, and enroll at scale after provisioning

Android

After provisioning a device with Esper, you can deploy apps, push configuration changes, and control devices remotely — all without physical access to the hardware.

Why this works

Once provisioning completes, the Esper Agent maintains a persistent connection to the Esper Console. Any app deployment, Blueprint assignment, or policy change is delivered over that connection automatically. Devices do not need to be on a specific network or VPN — as long as they have internet access, changes are queued and applied as soon as the device is reachable.

Deploy an app to a provisioned device

1. Confirm the target device is online. Navigate to Devices & Groups and verify the device shows a green active status indicator. If the device is offline, the deployment will queue and execute automatically when it reconnects.
2. Navigate to Apps & Configuration → Apps in the Esper Console.
3. Locate the app you want to deploy and select it.
4. Click Deploy, then select the target device or device group from the list.
5. Confirm the deployment. The Esper Agent downloads and installs the app silently in the background — no user interaction is required on the device.

Verify: Navigate to Devices & Groups → [Device Name] → Apps. The app should appear in the installed apps list within 5 minutes on an active connection.

Push a Blueprint or configuration change

1. Navigate to Blueprints in the Esper Console.
2. Open the blueprint you want to modify.
3. Make your required changes — kiosk settings, managed configurations, compliance policies, or restrictions.
4. Click Publish. The updated blueprint is pushed automatically to every device assigned to it. You do not need to redeploy to individual devices.

Verify: Navigate to Devices & Groups → [Device Name] and check the Blueprint compliance status. It should show as Compliant or In Sync within 10 minutes on an active connection.

Set up zero-touch enrollment for new devices

Zero-touch enrollment lets you provision devices at scale during first boot, without QR codes or manual setup steps. Choose the method that matches your device type and supply chain.

• Google Zero-Touch Enrollment (ZTE): Contact your device reseller and request that device IMEIs are registered in your Google Zero-Touch portal. Link the portal to your Esper tenant. When a device powers on for the first time, it enrolls automatically into Esper without any manual interaction.
• Knox Mobile Enrollment (KME): For Samsung devices, ask your reseller to add device IMEIs to your Samsung KME portal. The enrollment behavior is identical to ZTE — devices auto-enroll on first boot.
• Seamless Provisioning: This method requires the Esper Agent to be embedded in the device firmware at the manufacturing level by the OEM. Contact your Esper account team to discuss OEM partnerships before selecting this method.

Verify: Power on a newly enrolled test device. It should appear automatically in Devices & Groups within a few minutes of completing the out-of-box setup flow, without any QR code scan or manual provisioning step.

Use Remote Viewer or Remote Control

1. Navigate to Devices & Groups in the Esper Console.
2. Select the target device.
3. Choose the appropriate remote access mode:
   • Remote Viewer — view the live device screen without interacting with it. Use this to observe device state or diagnose a reported issue.
   • Remote Control — interact with the device screen directly. Availability depends on the device's hardware and Android version.
4. A live screen session opens in your browser. No additional software is required.

Verify: The live device screen renders in the Esper Console browser window within 30 seconds. If the session does not start, confirm the device is online in Devices & Groups and that Remote Control is supported by the device's Android version and hardware.

Troubleshooting

App is not installing

• Check the device status in Devices & Groups. A grey or offline status means the deployment command is queued and will execute when the device reconnects — no action is required.
• Confirm the correct app version is published and available in Apps & Configuration → Apps.
• Check the Activity Feed for the device to see whether the install command was received and whether any error was returned.

Blueprint is not converging

• Navigate to Devices & Groups → [Device Name] and confirm the correct blueprint is assigned to the device.
• Check the Activity Feed for any compliance errors or failed commands that may be blocking convergence.
• If the blueprint was recently published, allow up to 10 minutes for full convergence on devices with intermittent connectivity.

If this doesn't resolve it

Before contacting support, collect the following information:

• Device name and serial number from Devices & Groups → [Device Name] → Device Info
• A screenshot of the Activity Feed showing any failed commands or error codes
• The name of the blueprint assigned to the device and the timestamp of the last publish action
• For zero-touch enrollment issues: confirmation of whether the IMEI appears in your ZTE or KME portal

Contact Esper Support with this information so the team can investigate without delay.

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.