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.

This section lists the OMA DM command elements that are used to manage Windows Mobile devices. For each command element a short description and any information specific to its implementation are included. For further information OMA DM command element see "SyncML Representation Protocol Device Management Usage (OMA-SyncML-DMRepPro-V1_1_2-20030613-A)" available from the Open Mobile Alliance (OMA) Web site .

If an XML element is not a valid OMA DM command then the status code 400 is returned for that element.

The following table shows the OMA DM command elements that are used in Windows Mobile devices.

OMA Command Element Description


Creates a new node in the DM tree. Windows Mobile 6.5 supports Implicit Add which means that interior nodes specified in the Target LocURI will be added if they don't already exist.

The following example shows how to use the Add command. In this example b1 is to be added to be tree as a child node of interior node B. c1 is the data value of node b1. Because b1 is not currently in the device's DM tree, this node will be automatically created.

Copy Code
	 <Format xmlns='syncml:metinf'>...</Format> 
	 <Type xmlns='syncml:metinf'>....</Type> 

Alert (DM Alert)

Sends notifications, such as device management session requests, to the recipient.


Indicates that the client device must process a specified group of OMA DM commands together or not at all.

Performing an Add command followed by Replace on the same node within an Atomic element is not supported.


Removes a node from the DM tree, and the entire sub-tree beneath that node if one exists.


Invokes an executable on the client device.

For OTA Firmware Update to occur, Firmware Update Managed Object (FUMO) requires that the Correlator be specified in the Exec command. For an example, see OMA DM Generic Alert.


Retrieves data from the client device.


Overwrites data on the client device.


Returns the data results of either a Get or Search command to the DM server.


Specifies the order in which a group of commands must be processed.


Indicates the completion status (success or failure) of an operation.

See Also