Android Enterprise Wi-Fi policy applied but devices stay on old SSIDSolved

Participant
Discussion
2 days ago Nov 03, 2026

I created a Wi-Fi policy in Hexnode for Android Enterprise scanner devices and associated it successfully with the target devices. The policy uses a dedicated SSID for the scanners, but the devices still connect to the original Wi-Fi network instead of the new one.

The policy association looks successful in Hexnode, so I expected the devices to switch over automatically. The dedicated SSID also does not seem to appear where I expected it on the Wi-Fi controller side. Is there anything specific I should check for Android Enterprise Wi-Fi policies?

Replies (3)

Marked SolutionPending Review
Hexnode Expert
2 days ago Nov 03, 2026
Marked SolutionPending Review

Hi @ed_evans ,

For Android Enterprise devices, a successfully associated Wi-Fi policy adds the configured network to the device’s saved or known networks list. However, the device may not immediately switch from an already connected Wi-Fi network to the newly added SSID.

If the SSID is visible and reachable from the device, select the new Wi-Fi network once on the device. After that first manual selection, the device should be able to reconnect to it automatically in the future when the network is available.

If the configured SSID is not visible on the device or is not active on the Wi-Fi controller, check these points first:

  1. Confirm that the SSID is active and broadcasting on the Wi-Fi controller.
  2. Make sure the SSID is available to the access points or device location where the scanners are being used.
  3. Verify that the Wi-Fi security type and password configured in the Hexnode policy match the network settings.
  4. In Hexnode UEM, confirm that the Wi-Fi policy status is active on the target devices.
  5. Check the device action logs or policy logs for any policy push errors.

Hexnode UEM can deploy the Wi-Fi configuration to the device, but the device can only connect if the SSID is available and reachable from the network infrastructure.

Regards,
Isabel Lora
Hexnode UEM

Marked SolutionPending Review
Participant
2 days ago Nov 03, 2026
Marked SolutionPending Review

In my case, I do not see the dedicated scanner SSID on the Wi-Fi controller side either, so I’m going to check whether the SSID is actually enabled and broadcasting before troubleshooting the device further.

Marked SolutionPending Review
Hexnode Expert
2 days ago Nov 03, 2026
Marked SolutionPending Review

If the SSID is not visible or active on the controller, that should be resolved first. The Hexnode UEM Wi-Fi policy can save the network profile on the Android Enterprise device, but it cannot make an unavailable SSID appear or force a connection to a network that is not being broadcast or assigned to the relevant access points.

Once the SSID is confirmed as active on the controller:

  • Re-sync the policy with the affected devices.
  • Confirm that the policy remains active in Hexnode.
  • Open Wi-Fi settings on one scanner and select the new SSID once.
  • After the first successful connection, test whether the device reconnects automatically when it returns to that network range.

If the policy is active and the SSID is available but the device still does not list or connect to the network, the next useful place to check is the policy/action log for Wi-Fi profile deployment errors.

Regards,
Isabel Lora
Hexnode UEM

Save