Device Management Migration
In Windows Mobile 2003, Device Management only accepted OMA Client Provisioning XML files. In Windows Mobile Version 5.0, Device Management now accepts provisioning XML files not only in the OMA Client Provisioning protocol, but also accepts XML to OMA DM standards.
The following table shows the new components that were added to support OMA Device Management.
| Component | Comment |
|---|---|
| OMA DM Transport Client | The client communicates with OMA DM server. For more information, see OMA Device Management Architecture. |
| OMA Data Process Unit | This component does all of the management with OMA DM XML parsing. For more information, see OMA Device Management Architecture. |
| Configuration Manager2 | Configuration Manager2 can be used over OMA DM |
| Configuration Service Providers Managed over OMA DM | The style of Configuration Service Provider differs from those used in Windows Mobile 2003. Several Configuration Service Providers were added to directly support OMA DM, and some existing Configuration Service Providers can be managed by using the Legacy CSP Wrapper. |
| Legacy CSP Wrapper | The legacy Configuration Service Provider wrapper allows Configuration Manager2 to manage some Configuration Service Providers that were supported over OMA Client Provisioning. Although supported, these Configuration Service Provider they have limitations through OMA DM.
For information about specific rules for legacy Configuration Service Providers, see the documentation for the specific Configuration Service Provider in Configuration Service Provider Reference for Windows Mobile-Based Devices. |
For an architectural view and description of these new components, see OMA Device Management Architecture.
See Also
OMA Device Management | OMA Client Provisioning Device Management
Send Feedback on this topic to the authors