OMA Device Management

Windows Mobile 6.5
4/8/2010

Device Management (DM) is one way to provision a device. Provisioning is updating the device after manufacture. This may or may not include bootstrapping a device. When an OEM or Operator bootstraps a device after manufacture, or makes any other update (except a firmware update) it is provisioning the device. When an OEM bootstraps a device during manufacture it is not provisioning.

Managing devices with OMA DM allows two-way communication between server and client, which allows remote device manageability because the server can receive a response.

Bb737369.note(en-us,MSDN.10).gifNote:
In some areas, Microsoft has extended the OMA standards. For more information, see OMA DM Standards and Extensions.

The following table shows the OMA DM versions that Windows Mobile supports.

Protocol Description

OMA Device Management version 1.1.2

Allows two-way communication between server and client.

This protocol was supported in Windows Mobile Version 5.0, and is supported in Windows Mobile 6.5 for backward compatibility.

OMA Device Management version 1.2

Allows two-way communication between server and client, and supports the Generic Alert. Firmware Update Managed Object (FUMO) uses the generic alert to notify the server that the update was successful or that it failed.

For more information, see OMA DM Standards and Extensions.

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

For general best practices in managing devices, see Best Practices in Managing Devices.

For security best practices, see Security and Managing Devices and OMA Device Management Security Best Practices.

Server Requirements for OMA Device Management

Describes server requirements for supporting OMA Device Management.

OMA DM version 1.1.2 Architecture

Describes managing a device over the air (OTA) using the OMA DM version 1.1.2 Protocol.

OMA DM version 1.2 Architecture

Describes managing a device over the air (OTA) using the OMA DM version 1.2 Protocol.

OMA DM Client Connection Retry

Describes the OMA DM Client Connection Retry technology that is used in remote device management with OMA DM version 1.2 to more reliably connect to the server. It also tries to reconnect if the connection fails during a device management session.

OMA DM Standards and Extensions

Describes the standards and any Microsoft extensions to the OMA Client Provisioning protocol.

OMA Device Management Tree

Describes the OMA Device Management configurable features that are put in a logical view of a tree structure for ease of manageability.

Configuration Service Providers Managed Over OMA DM

Lists the Configuration Service Providers that support OMA Device Management on Windows Mobile devices.

The Device Management (DM) Session

Describes the DM session that consists of a series of commands exchanged between a DM server and a client device. The server sends commands indicating operations that must be performed on the client device's management tree. The client responds by sending commands that contain the results and any requested status information.

OMA DM Provisioning Files

Describes the OMA DM message, which is a provisioning XML document that contains DM commands. DM commands are transmitted between the server and the client device in these messages. Each message can contain one or more command.

OMA DM Protocol Command Elementss

Lists the OMA DM Command elements that are used to manage Windows Mobile devices.

OMA DM Protocol Common Elements

Lists common elements that are used by other OMA DM element types.

Understanding OTA Firmware Update

Describes how Windows Mobile handles OTA firmware update at the various component levels, and contains scenarios and FUMO result codes.

OMA Client Provisioning

Describes managing a device over the air (OTA) through a WAP push.

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.

Community Additions

Show: