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. |
You must also add an entry to .provxml that defines the DestIDfor the network connection. The same SSID must be used in the .provxml file as is in the Presetregistry key. There must be a DestIDentry for each of the networks that is to be pre-configured. The following code example shows how to use provisioning XML to set the DestIDparm.
Code Example
Copy Code | |
---|---|
<characteristic type="CM_WiFiEntries"> <characteristic type="MSFTINET"> <parm name="DestID" value="{GUID}"/> </characteristic> </characteristic> |
This information must be extracted from the .provxml file and inserted in the provisioning of the network.
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 OMA Client Provisioning file. For information about the syntax of this file, see OMA Client Provisioning Files. For examples, see OMA Client Provisioning XML File Examples.