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.

Windows Mobile devices can be provisioned over-the-air using OMA DM provisioning XML and an OMA Device Management server. This is the preferred method, since it provides two-way communication for subsequent provisioning.

Microsoft does not provide an OMA DM server. The OEM, mobile operator, or a third party must create their own server. For information about server requirements, see Server Requirements for OMA Device Management.


The following illustration shows how a device is provisioned using an OMA DM server.

The numbers in the illustration correspond to the following steps:

  1. You place the OMA DM provisioning XML file on the OMA DM server to be ready for download.

  2. Using a WAP push, the DM server sends a Short Message Service (SMS) message to the device. The message, also called the server trigger, includes the server ID and tells the client device to initiate a session with the server. The client device will use this information to verify that the server is authorized to communicate with it.

  3. The device initiates a DM session with the OMA DM server and downloads the OMA DM provisioning XML file.

    The device is updated.

For greater detail of what occurs on the device, see OMA DM version 1.1.2 Architecture.

For information about what occurs during a DM session, see The Device Management (DM) Session.

See Also