Managed Google Play app installs fail on a single device: factory reset and reprovision to complete EMM enrollment

Android

If app installations fail on a single device with an error about Managed Google Play policy updates, the device's Enterprise Mobility Management (EMM) enrollment did not complete during provisioning. This guide walks you through factory resetting and reprovisioning the device to complete EMM enrollment.

Before you begin

Verify that the issue affects only one device and that your enterprise's Managed Google Play binding is active. Navigate to Enterprise Settings → Managed Google Play and confirm the binding is not expired.

If multiple devices on the same network are experiencing this issue simultaneously, or if the managed Google Play binding appears inactive, contact Esper Support before proceeding.

How to identify incomplete EMM enrollment

In the Esper Console, navigate to Devices & Groups → [Device Name].
On the device itself, open the Play Store and look for a "Managed by [Enterprise]" label or managed account badge. If no managed account exists, EMM enrollment did not complete.
If you see an error like The Google Play install command failed to update the policy. Verify that your device is enrolled in Managed Google Play, this confirms EMM enrollment is missing.

Step 1: Preserve your device configuration

Before resetting the device, save the Blueprint configuration it was assigned to:

Navigate to Blueprints, find the assigned Blueprint, and select Clone to create a backup copy.
Alternatively, write down the Blueprint name so you can re-assign it after reprovisioning.

Step 2: Create a diagnostic Blueprint

Create a minimal Blueprint with only these settings enabled to verify EMM enrollment completes:

Managed Google Play Services: Always Enabled
Google Play Store Visibility: Enabled

This streamlined Blueprint isolates EMM enrollment before you re-apply your full production configuration.

Step 3: Factory reset the device

In the Esper Console, navigate to Devices & Groups → [Device Name] → Actions → Factory Reset.
Alternatively, perform a manual factory reset directly on the device if it is offline.
Wait for the reset to complete.

Step 4: Reprovision with the diagnostic Blueprint

Reprovision the device using your diagnostic Blueprint. Use the provisioning method appropriate for your fleet:

QR code provisioning
Zero-Touch Enrollment
Knox Mobile Enrollment (KME)

Ensure the device has stable internet access during provisioning — EMM enrollment requires outbound connectivity to Google's Play EMM APIs.

Step 5: Verify EMM enrollment completed

Wait for provisioning to complete.
On the device, open the Play Store and confirm that a managed account now appears with a "Managed by [Enterprise]" label or managed account badge.
If the managed account is present, EMM enrollment was successful.

Step 6: Apply your production Blueprint

Navigate to Devices & Groups → [Device Name] → Blueprint.
Select Apply and choose your original production Blueprint.
Wait for convergence to complete.

Step 7: Verify app installation works

Navigate to Devices & Groups → [Device Name] → Apps.
Select Install and manually push a test app to confirm it installs without policy update errors.
Verify that any apps assigned via Blueprint also begin installing automatically.

If the managed Google Play account still does not appear

If after reprovisioning the managed account badge is still missing from the Play Store:

Confirm your device has stable internet access and can reach Google's Play EMM APIs.
Return to Enterprise Settings → Managed Google Play and verify the enterprise binding is active and not expired.
Try reprovisioning the device a second time with the diagnostic Blueprint.

If the issue persists after multiple reprovisioning attempts, contact Esper Support. Provide the device model, Android version, Esper Agent version, and Esper Agent logs (collected via adb shell dpc_logs).

Still need help?

If you have questions or the issue is not resolved, submit a support ticket. Include the device name, the error message you received, and confirmation of your Managed Google Play binding status.