--- title: WiFi CSP description: The WiFi configuration service provider (CSP) provides the functionality to add or delete Wi-Fi networks on a Windows device. ms.assetid: f927cb5f-9555-4029-838b-03fb68937f06 ms.reviewer: manager: dansimp ms.author: dansimp ms.topic: article ms.prod: w10 ms.technology: windows author: manikadhiman ms.date: 06/18/2019 --- # WiFi CSP > [!WARNING] > Some information relates to pre-released products, which may be substantially modified before it's commercially released. Microsoft makes no warranties, expressed or implied, concerning the information provided here. The WiFi configuration service provider provides the functionality to add or delete Wi-Fi networks on a Windows device. The configuration service provider accepts SyncML input and converts it to a network profile that is installed on the device. This profile enables the device to connect to the Wi-Fi network when it is in range. Programming considerations: - If the authentication method needs a certificate, for example, EAP-TLS requires client certificates, you must configure it through the CertificateStore configuration service provider. The WiFi configuration service provider does not provide that functionality; instead, the Wi-Fi profile can specify characteristics of the certificate to be used for choosing the right certificate for that network. The server must successfully enroll the certificate first before deploying the Wi-Fi network configuration. For example, for an EAP-TLS profile, the server must successfully configure and enroll the required client certificate before deploying the Wi-Fi profile. Self-signed certificate works for EAP-TLS/PEAP-MSCHAPv2, but it is not supported in EAP-TLS. - Because the Windows 10 Mobile emulator does not support Wi-Fi, you cannot test the Wi-Fi configuration with an emulator. You can still provision a Wi-Fi network using the WiFi CSP, then check it in the Wi-Fi settings page, but you cannot test the network connectivity in the emulator. - For WEP, WPA, and WPA2-based networks, include the passkey in the network configuration in plaintext. The passkey is encrypted automatically when it is stored on the device. - The SSID of the Wi-Fi network part of the LocURI node must be a valid URI based on RFC 2396. This requires that all non-ASCII characters must be escaped using a %-character. Unicode characters without the necessary escaping are not supported. - The \*name\_goes\_here*\\ must match \\ *name\_goes\_here*\\. - For the WiFi CSP, you cannot use the Replace command unless the node already exists. - Using Proxyis only supported in Windows 10 Mobile. Using this configuration in Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) will result in failure. The following shows the WiFi configuration service provider in tree format. ```console ./Device/Vendor/MSFT or ./User/Vendor/MSFT WiFi ---Profile ------SSID ---------WlanXML ---------Proxy ---------ProxyPacUrl ---------ProxyWPAD ---------WiFiCost ``` The following list shows the characteristics and parameters. **Device or User profile** For user profile, use ./User/Vendor/MSFT/Wifi path and for device profile, use ./Device/Vendor/MSFT/Wifi path. **Profile** Identifies the Wi-Fi network configuration. Each Wi-Fi network configuration is represented by a profile object. This network profile includes all the information required for the device to connect to that network – for example, the SSID, authentication and encryption methods and passphrase in case of WEP or WPA2 networks. Supported operation is Get. **\** Specifies the name of the Wi-Fi network (32 bytes maximum) to create, configure, query, or delete. The name is case sensitive and can be represented in ASCII. The SSID is added when the WlanXML node is added. When the SSID node is deleted, then all the subnodes are also deleted. SSID is the name of network you are connecting to, while Profile name is the name of the Profile which contains the WiFi settings information. If the Profile name is not set right in the MDM SyncML, as per the information in the WiFi settings XML, it could lead to some unexpected errors. For example, \./Vendor/MSFT/WiFi/Profile/<*MUST BE NAME OF PROFILE AS PER WIFI XML*>/WlanXml\. The supported operations are Add, Get, Delete, and Replace. **WlanXML** The XML that describes the network configuration and follows the [WLAN\_profile Schema](/windows/win32/nativewifi/wlan-profileschema-schema) on MSDN. Supported operations are Get, Add, Delete, and Replace. Value type is chr. The profile XML must be escaped, as shown in the examples below. If it exists in the blob, the **keyType** and **protected** elements must come before **keyMaterial**, as shown in the example in [WPA2-Personal Profile Sample](/windows/win32/nativewifi/wpa2-personal-profile-sample). > **Note**  If you need to specify other advanced conditions, such as specifying criteria for certificates that can be used by the Wi-Fi profile, you can do so by specifying this through the EapHostConfig portion of the WlanXML. For more information, see [EAP configuration](./eap-configuration.md). The supported operations are Add, Get, Delete, and Replace. **Proxy** Optional. Specifies the configuration of the network proxy. A proxy server host and port can be specified per connection for Windows 10 Mobile. This proxy configuration is only supported in Windows 10 Mobile. Using this configuration in Windows 10 for desktop editions will result in failure. The format is *host:port*, where host can be one of the following: - A registered host name, such as server name, FQDN, or Single Label Name, such as myweb instead of myweb.contoso.com. - IPV4 address - IPv6/IPvFuture address. If it is an IPvFuture address, then it must be specified as an IP literal as "\[" (IP v6 address / IPvFuture ) "\]", such as "\[2441:4880:28:3:204:76ff:f43f:6eb\]:8080". Supported operations are Get, Add, Delete, and Replace. **DisableInternetConnectivityChecks** > [!Note] > This node has been deprecated since Windows 10, version 1607. Added in Windows 10, version 1511. Optional. Disable the internet connectivity check for the profile. Value type is chr. - True - internet connectivity check is disabled. - False - internet connectivity check is enabled. Supported operations are Get, Add, Delete, and Replace. **ProxyPacUrl** Added in Windows 10, version 1607. Optional. Specifies the value of the URL to the Proxy auto-config (PAC) file location. This proxy configuration is only supported in Windows 10 Mobile. Value type is chr, e.g. http://www.contoso.com/wpad.dat. **ProxyWPAD** Added in Windows 10, version 1607. Optional. When set to true it enables Web Proxy Auto-Discovery Protocol (WPAD) for proxy lookup.This proxy configuration is only supported in Windows 10 Mobile. Value type is bool. **WiFiCost** Added in Windows 10, version 1809. Optional. This policy sets the cost of WLAN connection for the Wi-Fi profile. Default behavior: Unrestricted. Supported values: - 1 - Unrestricted - unlimited connection - 2 - Fixed - capacity constraints up to a certain data limit - 3 - Variable - paid on per byte basic Supported operations are Add, Get, Replace and Delete. Value type is integer. ## Examples These XML examples show how to perform various tasks using OMA DM. ### Add a network The following example shows how to add PEAP-MSCHAPv2 network with SSID 'MyNetwork,' a proxy URL 'testproxy,' and port 80. ```xml 301 302 ./Vendor/MSFT/WiFi/Profile/MyNetwork/WlanXml chr MyNetwork412D4D534654574C414EMyNetworkfalseESSmanualWPA2AEStrueuser2500025truetruefalse26falsefalsefalsefalsefalse $CmdID$ ./Vendor/MSFT/WiFi/Profile/MyNetwork/Proxy chr testproxy:80 ``` ### Query network profiles The following example shows how to query Wi-Fi profiles installed on an MDM server. ```xml 301 ./Vendor/MSFT/WiFi/Profile ``` The following example shows the response. ```xml 3 1 301 ./Vendor/MSFT/WiFi/Profile node TestWLAN1/TestWLAN2 ``` ### Remove a network The following example shows how to remove a network with SSID ‘MyNetwork’ and no proxy. Removing all network authentication types is done in this same manner. ```xml 300 301 ./Vendor/MSFT/WiFi/Profile/MyNetwork/WlanXml ``` ### Add a network and certification authority for a server certificate The following example shows how to add PEAP-MSCHAPv2 network with SSID ‘MyNetwork’ and root CA validation for server certificate. ```xml 300 301 ./Vendor/MSFT/WiFi/Profile/MyNetwork/WlanXml chr MyNetworkMyNetworkfalseESSmanualWPA2AEStrueuser2500025true InsertCertThumbPrintHere truefalse26falsefalsefalsetruefalse ``` ## Related topics [Configuration service provider reference](configuration-service-provider-reference.md)