Android Wi-Fi

You can configure the Wi-Fi settings, which needs to be distributed to the devices. After configuring the Wi-Fi settings, the profile needs to be associated to the devices/groups.

To ease the Wi-Fi configuration process, you can add all the required Wi-Fi configurations to a single profile. This will ensure the device connects to any of the specified Wi-Fi networks when in it's vicinity. It also reduces the chances of the device being unmanaged, in case connection to Wi-Fi networks not distributed by MDM, is restricted.

Note:For devices running Android 9.0 or below, the devices will connect automatically to the Wi-Fi distributed if Automatically join network is enabled. In case of non-Samsung devices running Android 10.0 or later, once the Wi-Fi profile is distributed, the users will be prompted to connect to the Wi-Fi. In Device Owner devices, the users will be prompted continuously until they connect to the Wi-Fi. While in Profile Owner devices, the users will only be prompted 5 times.

FEATURE	DESCRIPTION	SAMSUNG	NON-SAMSUNG
			LEGACY	PROFILE OWNER	DEVICE OWNER
Wireless Network identification	Specify the name of your Wi-Fi network
Automatically join network	Enabling this option, will allow the device to automatically join the Wi-Fi network
Security type	Choose the security type as None/WEP/WPA/WPA2 PSK/ 802.1x EAP
Password (Can be configured only if Security type is configured)	Specify the Password if you have chosen the security type as WEP / WPA/WPA2 PSK
EAP Method (Can be configured only if Security type is '802.1x EAP')	If you have chosen the security type as 802.1x EAP, then you need to specify the type of authentication as PEAP/TLS/TTLS/ EAP PWD
Phase 2 Authentication (Can be configured only if Security type is '802.1x EAP')	Specify the Phase 2 Authentication type as PAP/MSCHAP/MSCHAPV2/GTC
Identity	Using %UserName% will fetch the appropriate user name mapped with the device. You can also specify a user name if you wanted to distribute this profile to one device. If you distribute a profile by providing a user name to more than one device, then all the devices will try to establish Wi-Fi connectivity with the same user name.
Anonymous Identity	If you do not want to disclose the user name mapped with the device, while establishing the Wi-Fi connection then you can use anonymous user name. Anonymous user name will use a dummy, anonymous identity to establish the connection
CA Certificate (Supported from Android 4.3)	Choose the existing Global Certificate or add a Global certificate to authenticate the device in order to establish the Wi-Fi connectivity. This will work only if the Wi-Fi certificate is configured in the Wi-Fi server. User specific certificates will be supported soon
Identity Certificate	Specify the ceritificate to be used for Certificate-based authentication(CBA).
CONFIGURE PROXY
Proxy Settings (Samsung-only feature, supported from Android 4.0)	Choose the type of proxy as "None" or "Manual". If you choose the proxy type as "None", then no proxy is required. If you choose to specify the proxy as manual, then you will have to fill in the details mentioned below
Server (Can be configured only if Security type is 'Manual')(Samsung-only feature, supported from Android 4.0)	Specify the proxy server name
Port (Can be configured only if Security type is 'Manual')(Samsung-only feature, supported from Android 4.0)	Specify the port number
Bypass URLs (Can be configured only if Security type is 'Manual')(Samsung-only feature, supported from Android 4.0)	Specify the URLs which should not be routed via proxy

Troubleshooting Tips

1. Ensure the SSID, password and the security type are correctly specified.
2. If a device is already connected to a particular Wi-Fi connection, it cannot be re-configured using a Wi-Fi policy.
3. If the distributed Wi-Fi configuration isn't working properly, try adding it manually on the Android device and ensure the correctness of the configuration. If you're able to add manually but not through MDM, contact MDM Support(MDM-support@manageengine.com)

If you are able to connect manually but not able to connect when you push through MDM, kindly send the agent logs for further analysis