CM_NetEntries Configuration Service Provider

  • Article

Send Feedback

The CM_NetEntries Configuration Service Provider configures additional network entries such as Desktop Passthrough (DTPT) or Wired Netcard, on Microsoft Windows Mobile-based Smartphones and Windows Mobile-based Pocket PCs.

The CM_NetEntries Configuration Service Provider is used to configure an association with Internet or Private networks on Pocket PC.

Note   This Configuration Service Provider is managed over the OMA Client Provisioning (formerly WAP) protocol. To provision devices using the OMA DM protocol, use the NAP Configuration Service Provider instead.

Note   Access to this Configuration Service Provider is determined by Security roles. Because OEMs and Mobile Operators can selectively disallow access, ask them about the availability of this Configuration Service Provider. For more information about roles, see Security Roles and Default Roles for Configuration Service Providers.

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 sub node.

Permissions Read/Write
Roles allowed to query and update setting Manager

AuthenticatedUser

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. This characteristic sets the name of the connection. This parameter also typically identifies which type of network connection is defined by the characteristic, for example, CurrentDTPTNetwork or CurrentWirelessNetwork.

Parameters

  • AlwaysOn
    Used in the <entryname> characteristic to specify whether the connection supports AlwaysOn. Permitted values are false (AlwaysOn not supported) and true (AlwaysOn supported).

    The following table shows the default settings.

    Permissions Read/Write
    Data type Boolean
    Roles allowed to query and update setting Manager

    AuthenticatedUser

  • Desc.<langid>
    Used in the <entryname> characteristic. A tag in the format of Desc.<langid> is used as the language-specific identifier for that entry. For example, if the field <parm name="Desc.0409" value="GPRS Connection" /> is set, "GPRS Connection" appears in the UI to identify this connection when the device is set to the English language (language ID 0409).

    Descriptions for multiple languages may be provisioned 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

    AuthenticatedUser

  • DestId
    Used in the <entryname> characteristic as a GUID that represents the unique ID of the network to which this entry connects. See the Connmgr.h header for predefined GUID values IID_DestNet*.

    The following table shows the default values.

    Permissions Read/Write
    Data type String
    Label Connects to
    Roles allowed to query and update setting Manager

    AuthenticatedUser

  • Secure
    Used in the <entryname> characteristic to specify whether the connection is marked as secure. Permitted values are false (not secure) and true (secure).

    The following table shows the default settings.

    Permissions Read/Write
    Data type Boolean
    Roles allowed to query and update setting Manager

    AuthenticatedUser

Note   Setting the value of Secure to false is not supported for Desktop Passthrough (DTPT) connections. DTPT was designed to work as a secure connection.

Microsoft Custom Elements

The following table shows the Microsoft custom elements that this Configuration Service Provider supports for OMA Client Provisioning.

Elements Available
noparm No
nocharacteristic Yes
characteristic-query Yes
parm-query Yes

Use these elements to build standard OMA Client Provisioning (formerly WAP) configuration XML. For information about specific elements, see MSPROV DTD Elements. For examples of how to generally use the Microsoft custom elements, see Provisioning XML File Examples.

For information about OMA Client Provisioning, see OMA Client Provisioning Files.

See Also

Configuration Service Provider Reference for Windows Mobile-Based Devices | CM_NetEntries Configuration Service Provider Examples for OMA Client Provisioning

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.