Device Management Migration from Windows Mobile 2003
4/8/2010
This topic provides information to help you migrate from Windows Mobile 2003 to Windows Mobile Version 5.0. This information may be useful when migrating to Windows Mobile 6.5.
In Windows Mobile 2003, Device Management only accepted OMA Client Provisioning XML files. In Windows Mobile Version 5.0, Device Management began also accepting XML to OMA DM version 1.1.2 standards.
The following table shows the new components that were added in Windows Mobile Version 5.0 to support OMA Device Management.
| Component | Comment |
|---|---|
OMA DM Transport Client |
The client communicates with OMA DM server. For more information, see OMA DM version 1.1.2 Architecture. |
OMA Data Process Unit |
This component does all of the management with OMA DM XML parsing. For more information, see OMA DM version 1.1.2 Architecture. |
Configuration Manager2 can be used 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 Devices. |
For an architectural view and description of these new components, see OMA DM version 1.1.2 Architecture.