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.

There are several ways that you can physically deliver provisioning XML documents to Windows Mobile devices. The method of delivery will determine whether or not you need to package the XML file.

Settings provisioned over the air or those requiring physical access to the device do not persist after cold boot. Settings that are shipped in ROM or updated through Image Update persist.

The following table shows how they divide, roughly, into three categories.

Delivery Category Delivery Method

Over the air (OTA) delivery

  • OMA DM Server (pushed to the device)

  • WAP Push (pushed to the device)

  • SI and SL (pushed to the device)

  • Over HTTP or HTTPS (Internet Explorer Mobile) (Pulled by the device)

  • Short Message Service (SMS)

  • E-mail

Delivery methods requiring physical access to the device, by the operator or use

  • From the desktop (ActiveSync and Remote Application Programming Interface (RAPI))

  • Secure Digital Multimedia Card (SD/MMC).

  • User Interface

Placing the provisioning files in device ROM either before or after deployment

  • Image Update packages

For information about each delivery method, see Options for Delivering Provisioning XML Filesand Delivering the Provisioning XML File to the Device.

See Also