Wi-Fi Off Setting Delayed 2–3 Hours Post-Provisioning: Expected Sync Behavior Explained

Android

When you apply a Wi-Fi Off setting through a Blueprint to newly provisioned devices, the setting may take up to 2–3 hours to take effect after enrollment. This article explains why this delay occurs and how to verify the setting is working correctly.

Understanding the remote configuration sync delay

After a device completes provisioning, it boots with the configuration that was cached during setup. The device then performs a scheduled synchronization to pull the latest remote configuration from the Esper backend. This synchronization process—called remote configuration convergence—can take approximately 2–3 hours to complete after initial provisioning.

During this window, settings that depend on remote configuration (such as Wi-Fi Off policies) will not be enforced until the device completes its first successful sync. Multiple reboots may speed up the sync cycle slightly, but they do not guarantee immediate updates. This behavior is expected and by design.

Before you begin

Verify the following before concluding that the setting is not applying:

• The device has completed initial provisioning and enrollment.
• The device maintains a stable network connection during the sync window.
• You have not factory reset or re-enrolled the device during the sync window.

How to verify the Wi-Fi Off setting is configured correctly

1. In the Esper Console, navigate to Blueprints → [Your Blueprint Name] → Network and verify that the Wi-Fi Off setting is enabled and saved.
2. Navigate to Devices & Groups → [Your Group Name] and confirm that the correct Blueprint is assigned to the group containing your device.
3. Locate your device in the Esper Console and note the provisioning timestamp.

How to monitor setting enforcement

1. Wait up to 2–3 hours after provisioning completes before checking whether the setting has been applied.
2. After the sync window has elapsed, navigate to Devices & Groups → [Device Name] → Device Details and verify that the Wi-Fi Off setting shows as enforced.
3. On the physical device, confirm that Wi-Fi is disabled.

If the setting has not applied after 2–3 hours

If the Wi-Fi Off setting has not been applied after a full 2–3 hour window and the device appears fully online, collect diagnostic information:

1. Request a bug report from the affected device: navigate to Devices & Groups → [Device Name] → Actions → Request Bug Report. This captures logs showing whether the remote configuration pull was attempted and whether any errors occurred during sync.
2. Verify the device is maintaining a stable network connection during the sync window. A device that repeatedly drops connectivity may fail to complete the remote config pull.
3. Check that your device's Esper Esper Agent version is current. Outdated agent versions may experience degraded sync behavior.
4. If multiple devices in the same group consistently fail to apply the setting beyond the 3-hour window, contact Esper Support and include:
   • Device serial numbers and UUIDs
   • Tenant and group name
   • Blueprint ID
   • Bug reports from affected devices
   • Provisioning timestamps and any observed setting enforcement timestamps

Still need help?

If you need additional assistance, submit a support ticket with details about your device, Blueprint configuration, and the issue you are experiencing.