Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
4/8/2010

The Wi-Fi Configuration Service Provider allows you to specify the encryption technique of a network

Code Examples

The following example shows how to specify the encryption technique of an access-point network. In this example, the network name is "Work Network" and the encryption is 802.11 wired equivalent privacy (WEP) key.

Copy Code 
<Replace>
	 <CmdID>3</CmdID>
	 <Item>
	
<Target><LocURI>./Vendor/MSFT/Wi-Fi/access-point/Work%20Network/Encryption</LocURI></Target>
		 <Data>0</Data>
	 </Item>
</Replace>

The following example shows how to specify the network encryption technique of a device-to-device network. In this example, the network name is "Work Network" and the encryption is Temporal Key Integrity Protocol (TKIP) sequence counters.

Copy Code 
<Replace>
	 <CmdID>3</CmdID>
	 <Item>
	
<Target><LocURI>./Vendor/MSFT/Wi-Fi/ad-hoc/Work%20Network/Encryption</LocURI></Target>
		 <Data>4</Data>
	 </Item>
</Replace>

Remarks

One provisioning XML file typically contains configuration information for multiple Configuration Service Providers. To use this example, you must replace the values as appropriate, and add the node as a child of the SyncBody node in an OMA DM provisioning file. For more information about the syntax of the provisioning file, see OMA DM Provisioning Files.

See Also