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.

4/8/2010

When an OEM or Operator bootstraps a device after manufacture, or makes any other update (except a firmware update) it is provisioning the device. This may or may not include bootstrapping a device. When an OEM bootstraps a device during manufacture it is not provisioning.

Managing devices with Open Mobile Alliance (OMA) Client Provisioning is done through a one-way push of a OMA Client Provisioning (WAP-based) XML file.

Windows Mobile devices have a provisioning structure, along with a unique extension that allows for continuous provisioning. OMA Client Provisioning is mostly used for bootstrapping, which is initially configuring a device so that it can be continuously provisioned by a privileged agent. OMA Device Management (DM) is then used for continuous provisioning to update or remove configuration settings on Windows Mobile devices. Configuration Manager and the Configuration Service Providers process the configuration settings message.

The Provisioning DTD (PROV DTD) defined in the Open Mobile Alliance Provisioning Content Specification, OMA-WAP-ProvCont-v1_1-20050428-C, was used as a guideline during development. This specification is located at this OMA Web site . However, the provisioning document, MSPROV DTD Format, extends the PROV DTD to allow you to update or remove configuration settings. MSPROV DTD is backward compatible with PROV DTD.

Microsoft does not provide an OMA Client Provisioning server. The OEM, Operator, or a third party must create their own server. For information about server requirements, see Server Requirements for OMA Client Provisioning.

There are various ways to deliver the provisioning XML file to a device. For information about the available options, see Options for Delivering Provisioning XML Files.

For best practices, see Best Practices in Managing Devices.

For security best practices, see Security and Managing Devicesand OMA Client Provisioning Security Best Practices.

In This Section

Understanding Bootstrapping: Describes the purpose and gives an overview of bootstrapping using OMA Client Provisioning.

Server Requirements for OMA Client Provisioning: Describes server requirements for supporting OMA Client Provisioning.

OMA Client Provisioning Device Management Architecture: Describes managing a device over the air (OTA) through a WAP push.

OMA Client Provisioning Protocol Support and Extensions: Describes the standards and any Microsoft extensions to the OMA Client Provisioning protocol.

OMA Client Provisioning Files: Describes the structure and format of OMA Client Provisioning files.

Microsoft Standards for Provisioning Windows Mobile Devices: Describes the standards for the implementation of Microsoft provisioning.

Standard OMA Client Provisioning Parameters Processed by the Device: Describes the Wireless Application Protocol (WAP) characteristic elements that enable Windows Mobile devices to access a network through a WAP gateway.

Related Sections

OMA Device Management: Describes managing a device OTA using the OMA Device Management protocol.

Provisioning Concepts: Describes the concept of provisioning, which is managing the device before and after deployment to your customers. This involves configuring device settings as well as installing and updating applications and device utilities.

Bootstrapping a Device: Describes the process of Bootstrapping, which is initially configuring a device so that it can be continuously provisioned by a privileged agent.