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 enable only the Bluetooth network interface or interfaces which are specified through the "AllowedProfiles" characteristic and corresponding parameter values

In this example, three Bluetooth network interfaces are enabled corresponding to the parameter values "{0000111F-0000-1000-8000-00805F9B34FB}", "{0000110A-0000-1000-8000-00805F9B34FB}", and "{0000110C-0000-1000-8000-00805F9B34FB}".

Note:
The GUID must be enclosed within the LocURI by braces {}. ASCII values of %7B and %7D must be used in place of opening and closing braces respectively, as shown in the XML example.

Code Example

Copy Code 
<Atomic>
  <CmdID>1</CmdID>
  <Add>
	<CmdID>2</CmdID>
	<Item>
	 
<Target><LocURI>./Vendor/MSFT/NetworkPolicy/Bluetooth/AllowedProfiles/%7B0000111F-0000-1000-8000-00805F9B34FB%7D</LocURI></Target>
	</Item>
  </Add>

  <Add>
	<CmdID>3</CmdID>
	<Item>
	 
<Target><LocURI>./Vendor/MSFT/NetworkPolicy/Bluetooth/AllowedProfiles/%7B0000110A-0000-1000-8000-00805F9B34FB%7D</LocURI></Target>
	</Item>
  </Add>

  <Add>
	<CmdID>4</CmdID>
	<Item>
	 
<Target><LocURI>./Vendor/MSFT/NetworkPolicy/Bluetooth/AllowedProfiles/%7B0000110C-0000-1000-8000-00805F9B34FB%7D</LocURI></Target>
	</Item>
  </Add>
</Atomic>

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.

The example above is treated as an "add" operation, as opposed to a replace operation, so this means that if some profiles were already configured to be in the allowed profile list, then this operation would add additional profiles to the list.

Parameter values can also be deleted from the allowed profile list. For more information on deleting profiles from the allowed profile list, see Remove Bluetooth AllowedProfiles Example for OMA DM.

See Also