Options for Delivering Provisioning XML Files to Windows Mobile-Based Devices
This section discusses the options available to Mobile Operators for physically delivering provisioning XML documents to Windows Mobile-based devices. They divide, roughly, into three categories.
- Over the air (OTA) delivery (pushed or pulled from the device).
- Delivery methods requiring physical access to the device, by the operator or user.
- Placing the provisioning files in device ROM either before or after deployment.
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 tables list the available options by category.
OTA Pushed to device
| Delivery Method | Description |
|---|---|
| OMA DM Server | The OMA DM server sends a SMS server notification message to the device. The OMA DM client connects to the server. The server sends provisioning OMA DM XML file to the device. For more information see OMA Device Management Provisioning |
| WAP Push | Windows Mobile-based Smartphones and Windows Mobile-based Pocket PCs (Phone Edition) can be provisioned by means of over-the-air (OTA) Wireless Application Protocol (WAP) push. For more information see, Provisioning OTA Through a WAP Push. |
OTA Pulled by device
| Delivery Method | Description |
|---|---|
| Over HTTP or HTTPS (Internet Explorer Mobile) | The user uses Internet Explorer Mobile to browse a web site from which they can download the provisioning XML files. See Delivering Applications for more information. |
| SMS | The user receives an Short Message Service (SMS) message containing a link to the web site from which they can download the provisioning files. See Delivering Applications for more information. |
| The user receives an email message containing a link to the web site from which they can download the provisioning files. See Delivering Applications for more information. |
Physical access to the device
| Delivery Method | Description |
|---|---|
| From the desktop | The Remote Application Programming Interface (RAPI) in ActiveSync can be used to push the provisioning XML file. See Provisioning From a Desktop Computer Using Remote API and ActiveSync.
Note The Remote API Security policy is set to RESTRICTED by default. |
| Memory Card | The Autorun feature can be used to provision the Windows Mobile-based device using a Secure Digital Multimedia Card (SD/MMC). See Delivering Applications for more information. |
| User Interface | The user can manually reconfigure the device by using the User Interface (UI) to change settings. See Provisioning Through the User Interface for more information. |
Placed in ROM
| Delivery Method | Description |
|---|---|
| In ROM (Image Update) | Provisioning XML files can be placed in Image Update packages in ROM to be processed either during cold boot or during Image Update. See Provisioning Using a ROM Configuration XML File for more information. |
See Also
Provisioning for Windows Mobile-Based Devices | Device Management Architecture
Send Feedback on this topic to the authors