Deploy apps and manage provisioned devices remotely — Esper setup guide

Android

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

Why this works

Once a device is provisioned, the Esper Agent maintains a persistent connection to the Esper Console. Any app deployment, Blueprint change, or policy update is delivered over the air as soon as the device is online. Zero-Touch Enrollment (ZTE) and Knox Mobile Enrollment (KME) extend this to first-boot provisioning, so devices enroll automatically without manual setup at the device.

Deploy an app to a provisioned device

1. Confirm the target device is online. Open Devices & Groups in the Esper Console and check that the device shows a green active status. Deployments to offline devices are queued and execute automatically when the device reconnects.
2. Navigate to Apps & Configuration in the Esper Console.
3. Select the app you want to deploy.
4. Click Deploy and choose the target device or device group.
5. The Esper Agent downloads and installs the app automatically. No action is required on the device.

Verify: Go to Devices & Groups → [Device Name] → Apps. The app should appear in the installed app list within 5 minutes of the device being online.

Push a Blueprint change to provisioned devices

1. Navigate to Blueprints in the Esper Console.
2. Open the blueprint you want to update.
3. Make your required changes — kiosk settings, managed configurations, policies, or restrictions.
4. Click Publish. The updated blueprint is pushed to all devices assigned to it. Esper Agent applies the changes automatically; no manual action is needed on the device.

Verify: Go to Devices & Groups → [Device Name] and check the Blueprint compliance status. The device should show Compliant within 5 minutes of being online.

Set up Zero-Touch Enrollment for new devices

Zero-touch methods let devices enroll into your Esper tenant automatically at first boot, without scanning a QR code. Choose the method that matches your device supplier and hardware.

• Google Zero-Touch Enrollment (ZTE): Contact your device reseller and request that your device IMEIs are registered in your Google Zero-Touch portal. When a device powers on for the first time, it auto-enrolls into your Esper tenant.
• Knox Mobile Enrollment (KME): For Samsung devices, have your reseller add devices to your KME portal. Devices auto-enroll the same way as ZTE during first-boot setup.
• Seamless Provisioning: Requires Esper to be embedded in the device firmware by the OEM before manufacturing. Contact your Esper account team to discuss OEM partnerships if this method is required.

1. Work with your reseller to register device IMEIs in the appropriate portal (Google ZTE or KME) and link that portal to your Esper tenant.
2. Power on a test device without performing any manual setup steps.
3. The device should connect to Wi-Fi, detect the enrollment configuration, and begin provisioning automatically.

Verify: Open Devices & Groups in the Esper Console. The test device should appear and show an active status within a few minutes of first boot, without any manual QR code scanning.

Access a provisioned device remotely

1. Navigate to Devices & Groups in the Esper Console.
2. Select the target device.
3. Choose the appropriate remote access mode:
   • Remote Viewer — view-only access to the device screen.
   • Remote Control — interactive control of the device screen. Availability depends on device hardware and Android version.
4. A live screen session opens in your browser. No additional software is required on your computer.

Verify: The device screen appears in the Esper Console browser window within 30 seconds. If the session does not load, confirm the device is online and that Remote Control is supported for that device model.

Troubleshooting

App not installing

1. Go to Devices & Groups → [Device Name] and confirm the device shows an active (green) status. If the device is offline, the installation will complete automatically when it reconnects.
2. Go to Apps & Configuration and confirm the deployment was submitted to the correct device or group.
3. Check Activity Feed on the device detail page for any installation error codes and use those to identify the specific failure.

Blueprint not converging

1. Go to Devices & Groups → [Device Name] and confirm the correct blueprint is assigned to the device.
2. Check Activity Feed for convergence errors or policy conflicts.
3. If the device has been offline for an extended period, allow up to 10 minutes after it reconnects for convergence to complete.

Zero-Touch Enrollment device not appearing in console

1. Confirm the device IMEI is registered in the correct portal (Google ZTE or KME) and that the portal is linked to your Esper tenant.
2. Confirm the device connected to Wi-Fi during first-boot setup before the enrollment screen appeared.
3. Factory reset the device and repeat the first-boot process to retry enrollment.

If this doesn't resolve it

Contact Esper Support and include the following information to speed up resolution:

• Device serial number or IMEI
• Esper tenant name
• Screenshot of the device status in Devices & Groups
• Any error codes shown in Activity Feed
• For ZTE/KME issues: confirmation of whether the IMEI appears in the enrollment portal

Still need help?

If you're still encountering issues with app deployment or device provisioning, submit a support ticket and include your device serial numbers, the apps you're attempting to deploy, and any error messages from the Esper console.