Wi-Fi Off setting delays 2–3 hours and requires multiple reboots post-provisioning: expected remote config sync behavior

Android

Title: Wi-Fi Off setting not enforced after provisioning — remote config sync delay

When a Blueprint with Wi-Fi Off enabled is applied to a newly provisioned device, the setting may not take effect for up to 2–3 hours after enrollment, even if the device appears fully online.

Why this happens

At the end of provisioning, the Esper Agent boots with a configuration snapshot cached during setup. The device then performs its first remote configuration sync against the Esper backend on a scheduled cycle, which can take up to 2–3 hours to complete. Until that sync succeeds, policies that depend on remote configuration — including Wi-Fi Off — are not yet enforced. Rebooting the device during this window may slightly accelerate the cycle but does not guarantee immediate enforcement.

Before you start

Confirm all of the following are true before proceeding:

• The device has fully completed provisioning and enrollment.
• The device has maintained a stable network connection since provisioning.
• The device has not been factory reset or re-enrolled during the sync window.

Steps

1. Confirm the Wi-Fi Off setting is saved in the Blueprint. Navigate to Blueprints → [Blueprint Name] → Network and verify that Wi-Fi Off is enabled. If it is not toggled on, enable it and save the Blueprint before continuing.
2. Confirm the Blueprint is assigned to the correct group. Navigate to Devices & Groups → [Group Name] and verify that the Blueprint containing the Wi-Fi Off setting is the active Blueprint for the group. A device enrolled into a group with the wrong Blueprint will never receive the setting.
3. Note the provisioning timestamp for the affected device. Navigate to Devices & Groups → [Device Name] → Device Details and record the enrollment time. This establishes when the 2–3 hour sync window began.
4. Wait for the sync window to elapse. Allow a full 2–3 hours from the provisioning timestamp before expecting the setting to be enforced. No action is needed during this period provided the device stays connected.
5. Verify enforcement after the sync window. Return to Devices & Groups → [Device Name] → Device Details and confirm that Wi-Fi Off is shown as enforced. On the physical device, confirm that Wi-Fi is disabled and the toggle is unavailable to the user.

Verify: Wi-Fi Off should appear as enforced in Devices & Groups → [Device Name] → Device Details and Wi-Fi should be disabled on the physical device within 2–3 hours of completed provisioning.

If this doesn't resolve it

If the Wi-Fi Off setting is still not enforced more than 3 hours after provisioning and the device is consistently online, collect the following before contacting support:

1. Request a bug report from the device. Navigate to Devices & Groups → [Device Name] → Actions → Request Bug Report. The report captures whether the remote configuration pull was attempted and whether any errors occurred during sync.
2. Check the Esper Agent version. Navigate to Devices & Groups → [Device Name] → Device Details and confirm the Esper Agent is on the latest available version. An outdated agent may produce degraded or failed sync behavior. Update via Esper Software Updates if needed.
3. Check the Activity Feed for sync errors. Navigate to Devices & Groups → [Device Name] → Activity Feed and look for failed configuration pull events around the time the sync window elapsed.

If multiple devices in the same group consistently fail to apply the setting beyond the 3-hour window, contact Esper Support and include the following:

• Device serial numbers and UUIDs
• Tenant name and group name
• Blueprint name
• Bug report file from at least one affected device
• Screenshots of the Activity Feed showing failed sync events

Still need help?

If you're still experiencing delays with Wi-Fi configuration changes or unexpected reboots after provisioning, submit a support ticket and include your device serial numbers, the timestamps when you initiated the remote config commands, and your network environment details.