Wi-Fi disabled setting applied to individual devices during tenant-level migration

Android

Title: Wi-Fi stays enabled on devices during tenant-wide Wi-Fi enforcement migration

When migrating to a tenant-wide Wi-Fi Off policy in Esper, individual devices that were enrolled before the migration may not automatically inherit the new enforcement setting, leaving Wi-Fi active on those devices despite your intended policy.

Why this happens

Tenant-level policy changes apply to newly enrolled devices and groups going forward, but devices already enrolled retain their existing configuration until a new setting is explicitly pushed to them. Until you apply the Wi-Fi Off setting directly to each pre-existing device, those devices continue operating under their prior configuration.

Before you start

For each device that needs Wi-Fi disabled, collect the following:

Device name as it appears in the Esper Console
Serial number or Esper device ID
The group the device belongs to

Apply the Wi-Fi Off setting to individual devices

Open the Esper Console and navigate to Devices & Groups.
Select the first device from your list.
Navigate to Devices & Groups → [Device Name] → Settings and locate the Wi-Fi configuration option. Applying the setting here pushes it directly to the device, bypassing any group-level inheritance delay.
Set Wi-Fi to Off and save the configuration.
Repeat steps 2–4 for every device on your list.
After applying the setting to all devices, confirm the active Blueprint assigned to each device does not contain a conflicting Wi-Fi On rule. Navigate to Devices & Groups → [Device Name] → Blueprint and review the Wi-Fi setting in the applied blueprint. A conflicting blueprint will override the direct device setting and re-enable Wi-Fi.

Verify: On a sample of the updated devices, open the device status in Devices & Groups → [Device Name] → Activity Feed and confirm the Wi-Fi Off command shows as applied. Physically or remotely confirm Wi-Fi is disabled on those devices. Devices should reflect the change within 5 minutes of receiving the command while online. Offline devices will apply the setting upon their next reconnection.

If this doesn't resolve it

Check the following before contacting support:

Wi-Fi re-enables itself after being set to Off: A Blueprint assigned to the device is likely overriding the direct setting. Go to Devices & Groups → [Device Name] → Blueprint, review the active blueprint, and remove or update any rule that sets Wi-Fi to On.
Device is offline: The command is queued but will not apply until the device reconnects. Check device online status under Devices & Groups → [Device Name].
Setting fails on a specific device model consistently: Some OEM devices have hardware or firmware-level restrictions that prevent software-enforced Wi-Fi control. Note the device model and Esper Agent version for your support request.
Ten or more devices are not accepting the configuration: A group-level or tenant-level conflict may be present. Do not attempt to resolve this by re-pushing the setting individually.

If the issue persists after the steps above, contact Esper Support with the following information:

List of affected device IDs
Device models and Esper Agent versions
Screenshots of the Blueprint configuration for one or more affected devices
Steps already taken and the outcome of each

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.