Wallpaper cannot be updated post-provisioning on Template-based devices: migrate to Blueprint to enable remote wallpaper management

Android

When devices are provisioned using a Template, any wallpaper set in that Template is applied once at provisioning time and cannot be changed remotely afterward — attempts to update the wallpaper from the Esper Console have no effect on the device.

Why this happens

Provisioning Templates are a static construct: they configure a device at the moment of provisioning and have no mechanism to push configuration changes after deployment. Wallpaper management requires a live, ongoing connection between the device configuration and the Esper Console, which only Blueprints support. Migrating the device to a Blueprint enables remote wallpaper updates — and all other dynamic configuration changes — without a factory reset.

Migrate a Template-provisioned device to a Blueprint

Create a Blueprint that mirrors your existing Template configuration. In the Esper Console, navigate to Blueprints and select Create Blueprint. Recreate the settings from your Template — apps, network settings, kiosk mode, compliance policies — so the device experience is unchanged after migration.
Set the desired wallpaper inside the Blueprint. Within the Blueprint editor, go to Blueprints → Appearance → Wallpaper, upload your wallpaper image, and save the Blueprint. This ensures the wallpaper is delivered as part of the Blueprint configuration when it is applied.
Assign the Blueprint to the device. Navigate to Devices & Groups → [Device Name] → Blueprint and select the Blueprint you just created.
Apply the Blueprint to the already-provisioned device. Select Upgrade Now to push the Blueprint over-the-air. This applies the full Blueprint configuration — including the new wallpaper — without requiring a factory reset or re-provisioning. If Upgrade Now is greyed out, the device is offline; bring it online and retry.

Update wallpaper going forward

Once a device is Blueprint-managed, update the wallpaper at any time by editing the wallpaper under Blueprints → Appearance → Wallpaper and saving. The change is pushed to all devices assigned to that Blueprint automatically — no re-provisioning required.

Verify

Verify: On the physical device, confirm the new wallpaper is visible. In the Esper Console, navigate to Devices & Groups → [Device Name] → Blueprint and confirm the device shows the correct Blueprint as its active configuration with a status of In Sync. This should reflect within 5 minutes of applying the Blueprint.

Troubleshoot common issues

Blueprint applies but wallpaper does not update. Navigate to Devices & Groups → [Device Name] → Blueprint and check the compliance status for any failed or pending configuration items. Resolve any listed failures, then re-apply the Blueprint.
Device cannot migrate without a factory reset. If the device's Esper Agent version or device state is incompatible with Blueprint assignment, re-provision the device using a Blueprint-based QR code or Zero-Touch Enrollment with the wallpaper configured in the Blueprint beforehand.

If this doesn't resolve it

If the wallpaper still does not update after following these steps, contact Esper Support with the following information:

Device serial number
Blueprint name and the timestamp of the last Upgrade Now action
A screenshot of the compliance status from Devices & Groups → [Device Name] → Blueprint
The Esper Agent version shown under Devices & Groups → [Device Name] → Device Info

Still need help?

If you're unable to update wallpaper on your Template-based devices after migrating to Blueprint, please submit a support ticket and include your device names, the Blueprint configuration you're using, and the wallpaper image or settings you're attempting to deploy.