~ Joel Stevens | Support Escalation Engineer
In a unified management scenario where Microsoft Intune is integrated with Configuration Manager, you can deploy Wi-Fi profiles to Windows Phone devices via the console UI. With that said, there are some additional Wi-Fi options that can also be configured if you use XML to deploy the profile instead. One such example is defining a Preshared key (PSK) and I’ll walk you through how to do that here.
1. First, create a new configuration item:
2. Name the configuration item and choose Mobile Device as the type. Use a descriptive name for the Configuration Item:
3. Select Configure additional settings that are not in the default settings group then click Next:
4. Click Add:
5. Click Create Setting...
6. Enter the following information:
a. The network name
b. A description
c. Setting type = OMA URI
d. OMA-URI (Case Sensitive) = ./Vendor/MSFT/WiFi/Profile/MyNetwork/WlanXml
Important: For OMA-URI, replace MyNetwork with the SSID of your Wi-Fi network.
7. Select the setting you just created:
Enter the following information:
Rule Type = Value
Paste in the XML code below, formatted to a single line, in standard .XML format. Configuration Manager will automatically convert this to embedded XML when it processes the configuration item. The following example is to deploy a WPA2 PSK with no proxy settings:
<?xml version="1.0"?><WLANProfile xmlns="http://www.microsoft.com/networking/WLAN/profile/v1"><name>MyNetwork</name><SSIDConfig>
Note that the XML above is a single line, it just wrapped here for readability purposes.
Important: Replace "MyNetwork" with the Wi-Fi network SSID. The SSID is case sensitive as is everything else in the XML code. Also replace P@ssword123 with the preshared key (PSK). This example uses WPA2PSK and AES encryption. If your network settings do not match, you must edit the XML code as appropriate.
Now that you have created your configuration item, the next step is to add this to a configuration baseline, deploy the configuration baseline to the required user or device collection, then monitor the compliance of the configuration baseline.
Be aware that having the <connectionMode> property set to “auto” won’t connect the device to your defined network automatically until the user disconnects from the current WLAN connection or taps the new WLAN name to force the connection. You could potentially use <autoSwitch> to overcome this issue, however that will create radio pollution and drain the devices battery more quickly.
You should modify the information above using the information for your network. Additional information about the XML elements and their possible values can be found here:
You can also reference the section titled WiFi configuration service provider (New in Windows Phone 8.1) in the protocol documentation here:
For additional information on creating mobile device configuration items, please see the following:
Joel Stevens | Support Escalation Engineer | Microsoft
- Configuration Manager: http://blogs.technet.com/configurationmgr/
- Data Protection Manager: http://blogs.technet.com/dpm/
- Orchestrator: http://blogs.technet.com/b/orchestrator/
- Operations Manager: http://blogs.technet.com/momteam/
- Operations Management Suite: https://blogs.technet.microsoft.com/omsblog/
- Service Manager: http://blogs.technet.com/b/servicemanager
- Virtual Machine Manager: http://blogs.technet.com/scvmm
- Microsoft Intune: https://blogs.technet.microsoft.com/intunesupport/
- WSUS: http://blogs.technet.com/sus/
- AD and Azure RMS: http://blogs.technet.com/b/rms/
- Application Virtualization: http://blogs.technet.com/appv/
- MED-V: http://blogs.technet.com/medv/
- Application Proxy: http://blogs.technet.com/b/applicationproxyblog/
- Forefront Endpoint Protection: http://blogs.technet.com/b/clientsecurity/
- Forefront Identity Manager: http://blogs.msdn.com/b/ms-identity-support/
- Forefront TMG: http://blogs.technet.com/b/isablog/
- Forefront UAG: http://blogs.technet.com/b/edgeaccessblog/