Wi-Fi and Power Management Configuration on Samsung Devices: What Esper Supports

Android

Title: Samsung Wi-Fi and power management — what Esper can configure

When managing Samsung devices through Esper, some Wi-Fi and power management settings are configurable via the Samsung Knox Service Plugin (KSP), while others are outside the reach of any MDM platform.

Why some settings cannot be managed

Android Enterprise APIs expose only a subset of Wi-Fi and power controls. Settings like transmit power, roaming aggressiveness, and Wi-Fi power save mode are governed at the chipset, firmware, or OS level — no MDM platform, including Esper, can reach them through standard management APIs. KSP extends what is possible on Samsung hardware, but only for settings Samsung has chosen to expose through Knox.

Before you begin

• Devices must be Samsung hardware running a supported Android version.
• Knox Service Plugin must be deployed, activated, and licensed on each target device.
• KSP behavior can vary by Samsung One UI version — validate on a test device before rolling out fleet-wide.
• Non-Samsung Android devices do not support KSP controls. Standard Android Enterprise Wi-Fi APIs apply instead.

Settings Esper supports on Samsung devices

MAC address randomization (Private/Randomized MAC)

Esper supports enabling or disabling Wi-Fi MAC address randomization on Samsung devices through KSP Managed Configuration.

1. Open the Esper Console and navigate to Devices & Groups, then select the target device or group.
2. Navigate to Apps & Configuration → Apps and confirm Knox Service Plugin is listed as installed and active. KSP must be running before any Knox Managed Configuration takes effect.
3. Open the Managed Configuration for Knox Service Plugin and locate the MAC address randomization setting.
4. Set the value to enabled or disabled according to your network policy.
5. Save and push the configuration to the device.

Verify: On the device, go to Settings → Wi-Fi → [Network] → Advanced and confirm the MAC address type reflects the value you configured. The change should appear within 5 minutes of the configuration being applied. The device's Activity Feed in the Esper Console will show the configuration as applied.

Settings not configurable through Esper

The following settings cannot be managed through Esper, KSP, or any Android MDM platform. They are listed here with the reason, so you can address them through alternative means if needed.

• Roaming Aggressiveness — Not exposed through Android Enterprise APIs or KSP. Cannot be set remotely via MDM.
• 5 GHz Band Preference — Requires chipset-level or OEM-specific control not available through Android Enterprise or KSP.
• Transmit Power — A hardware and firmware-level setting. Not exposed through Android Enterprise or KSP.
• Wi-Fi Power Save Mode — Managed by the Android OS and chipset driver. Not addressable through Esper APIs or Blueprint settings.

Troubleshooting

MAC address randomization is not taking effect

1. Navigate to Devices & Groups → [Device Name] → Apps in the Esper Console and confirm Knox Service Plugin appears in the installed apps list.
2. Verify KSP is activated and that your account has a valid Knox license — an unlicensed KSP installation will silently ignore Managed Configuration values.
3. Confirm the target devices are Samsung hardware. KSP settings have no effect on non-Samsung devices.
4. Check the device's Activity Feed for any configuration errors or rejection events that indicate KSP did not accept the policy.

Verify: After correcting the KSP deployment, re-push the Managed Configuration. The Activity Feed should show a successful configuration event, and the MAC setting on the device should update within 5 minutes.

If this doesn't resolve it

If MAC address randomization is still not applying after confirming KSP is deployed, licensed, and activated, contact Esper Support with the following information:

• Device make, model, and Android version
• Samsung One UI version
• Knox Service Plugin version installed on the device
• A screenshot of the Activity Feed entries from the time the configuration was pushed
• Confirmation of whether the device is enrolled in a fully managed or work profile deployment

If you need one of the unsupported settings listed above, contact Esper Support to submit a feature request. Include the specific setting, your use case, and the size of your fleet so the request can be routed to the Product team.

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.