Blueprint application failure on select devices: resolved in latest Esper Agent release (System Update Policy — "Disabled" not honoured by all OEMs)

Android

Some Android devices may fail to fully apply a Blueprint that includes a System Update Policy set to "Disabled". This issue occurs on devices from certain manufacturers that don't fully support this policy restriction. The fix has been included in the latest Esper Agent release. Follow the steps below to resolve this on your affected devices.

Before you begin

Verify that your affected devices are online and connected to Wi-Fi. Blueprints cannot be re-applied to offline devices. Check the device status in the Esper Console under Devices & Groups → [Device Name] → Overview.

Step 1: Update your Esper Agent

Open the Esper Console and navigate to Devices & Groups → [Device Name] → Device Info.
Check the current Esper Agent version.
Update the Esper Agent to the latest available version on all affected devices.
Verify the update has completed by checking the agent version again in Device Info.

Step 2: Re-apply the Blueprint

In the Esper Console, navigate to Devices & Groups → [Device Name] → Blueprint.
Select your target Blueprint.
Click Apply.
Wait for the status to update to Applied (indicated by a green checkmark or compliant status).

Step 3: Verify the Blueprint is applied

Confirm that device-level settings now reflect the expected Blueprint configuration. Check Devices & Groups → [Device Name] → Blueprint to verify the status shows as Applied.

Workaround for non-compliant devices

If your Blueprint contains a System Update Policy set to "Disabled" and the device manufacturer does not fully support this restriction, consider modifying the Blueprint to set the System Update Policy to an alternative value such as "Automatic" or "Windowed". This workaround can help you maintain device compliance while the manufacturer updates their implementation.

If the Blueprint still fails to apply

Collect diagnostic information

Generate a bug report from the affected device:
- Navigate to Devices & Groups → [Device Name] → Actions → Bug Report
- Download and save the report
If the device is accessible via ADB, pull the relevant logs by running:
```
adb shell logcat -d | grep -i "Esper Agent\|blueprint\|policy"
```
Note the exact device manufacturer, model, and Android firmware version.

Submit diagnostic data to Esper Support

If Blueprint application continues to fail after updating the Esper Agent, contact Esper Support and provide:

The bug report from the affected device
Esper Agent logs (if available)
Device manufacturer, model, and Android version
The number of devices affected
Whether multiple device manufacturers are affected

Still need help?

Submit a support ticket and include the diagnostic information above. Our support team will help you resolve the issue.