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 NetworkPolicy Configuration Service Provider example below can be used to disable the Bluetooth network interface.

In this example, the Bluetooth network interface is disabled since the "Disabled" parameter value is set to "1".

If any other value had been specified, or if the "Disabled" parameter were missing altogether, the Bluetooth network interface would be enabled.

Code Example

Copy Code 
<Add>
  <CmdID>1</CmdID>
  <Item>
   
<Target><LocURI>./Vendor/MSFT/NetworkPolicy/Bluetooth/Settings/Disabled</LocURI></Target>
	<Meta>
	<Format xmlns="syncml:metinf">node</Format>
	<Type xmlns="syncml:metinf">text/plain</Type>
	</Meta>
	<Data>1</Data>
  </Item>
</Add>

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.

This example could be extended to disable Wi-Fi and IrDA as well. Simply replace "Bluetooth" with "Wi-Fi" or "IrDA" as applicable. To disable multiple network interfaces, duplicate the XML for each network interface.

See Also