This is expected behavior on Android and is not usually caused by an incorrect Hexnode Wi-Fi policy if the profile is already saved on the device.
When a new Wi-Fi configuration is pushed through MDM, Android adds it to the device’s network configuration. However, Android does not always immediately trigger an active network switch to the newly added SSID while the device is running. This is more noticeable when kiosk mode is active because kiosk restrictions can limit user access to system Wi-Fi controls and may also affect how quickly background system network changes are acted on.
In practice, one of the following is usually required for the first connection to a newly pushed Wi-Fi profile:
1. Manually select the new Wi-Fi network once from Android Wi-Fi settings.
2. Restart the device so Android reinitializes network services and evaluates the saved Wi-Fi profiles again.
3. Temporarily exit kiosk mode if manual selection is required.
After the device has connected to the network once, Android should normally reconnect to it automatically in future, provided the SSID is available and the saved credentials are valid.
A restart is a reasonable workaround when deploying a replacement Wi-Fi profile at scale, but the result can vary by Android version and device model. Some devices may still require the first connection to be selected manually.
Regards,
Mary Romero
What's new 
19 Views
