CM_NetEntries Configuration Service Provider (Windows Embedded CE 6.0)
1/6/2010
You can use the CM_NetEntries configuration service provider to configure additional network connections, such as desktop passthrough (DTPT) or wired network card, on a Windows Embedded CE powered device.
Note
This configuration service provider is managed over the Open Mobile Alliance (OMA) client provisioning (formerly WAP client provisioning) protocol. For more information about OMA client provisioning, see Configuring Device Connection Settings by using OMA XML. Security roles determine access to this configuration service provider. Because OEMs and mobile operators can selectively disallow access, application developers should ask OEMs and mobile operators about the availability of this configuration service provider.
The nocharacteristic tag will work on the top two levels to delete all, or specific, entries.
The following table shows the default settings. The default security role maps to each subnode unless specific permission is granted to the subnode.
Permissions |
Read/Write |
Roles allowed to query and update setting |
Manager Authenticated User |
The following image shows the Configuration Service Provider in tree format as used by OMA Client Provisioning.
Characteristics
- <entryname>
User-friendly, unique name for the network connection. The name often identifies the kind of network connection; for example, CurrentDTPTNetwork or CurrentWirelessNetwork.
Parameters
Adapter
You can use this in the <entryname> characteristic to specify the fully qualified name of a wireless adapter.The default settings are as follows:
Permissions
Read/Write
Data type
String
Roles allowed to query and update setting
Manager
Authenticated User
AlwaysOn
You can use this in the <entryname> characteristic to specify whether the connection supports AlwaysOn. Permitted values are false (AlwaysOn not supported) and true (AlwaysOn supported).The default settings are as follows:
Permissions
Read/Write
Data type
Boolean
Roles allowed to query and update setting
Manager
Authenticated User
Desc.<langid>
You can use this in the <entryname> characteristic. A tag in the format of Desc.<langid> is used as the language identifier for that entry. For example, if the field <parm name="Desc.0409" value="GPRS Connection" /> is set, the UI might display "GPRS Connection" to identify this connection when the device is set to the English language (language ID 0409).You can provision descriptions for multiple languages using this mechanism, and the operating system automatically switches among them if the user changes language preferences on the device. If no <Desc> tag is provisioned for a specific language, the system defaults to the characteristic tag name used to create the entry.
Permissions
Read/Write
Roles allowed to query and update setting
Manager
Authenticated User
DestId
You can use this in the <entryname> characteristic as a GUID that represents the ID of the network that this entry connects to. See the Connmgr.h header for predefined GUID values IID_DestNet*.The default values are as follows:
Permissions
Read/Write
Data type
String
Label
Connects to
Roles allowed to query and update setting
Manager
Authenticated User
Secure
You can use this in the <entryname> characteristic to specify the security status of a connection. Permitted values are false (not secure) and true (more secure).Note
The configuration service provider does not support setting the value of Secure to false for DTPT connections.
The default settings are as follows:
Permissions
Read/Write
Data type
Boolean
Roles allowed to query and update setting
Manager
Authenticated User
Microsoft Custom Elements
The following table shows the Microsoft custom elements that this configuration service provider supports for OMA client provisioning.
Element Name | Description |
---|---|
noparm |
Not supported |
nocharacteristic |
Supported |
characteristic-query |
Supported |
parm-query |
Supported |
Use these elements to build standard OMA client provisioning (formerly WAP client provisioning) configuration XML. For more information about these elements, see MSPROV DTD Elements.
For more information about OMA client provisioning, see Configuring Device Connection Settings by using OMA XML.
See Also
Concepts
Configuration Service Providers Overview