Server Requirements for OMA Device Management

4/8/2010

The following list shows the general server requirements for using OMA DM to manage Windows Mobile devices:

The OMA DM Server must support the OMA DM v1.1.2 or later protocol.
There must be a WAP Push channel (Short Message Service (SMS)) for sending DM trigger messages to each device.
Secure Sockets Layer (SSL) must be on the OMA DM server, and it must provide server certificate-based authentication, data integrity check, and data encryption. If the certificate is not issued by a commercial Certificate Authority whose root certificate is preinstalled in the device, you must provision the Operator's root certificate in the device's ROOT store.
To authenticate the client, you must use either Basic or MD5 client authentication at the application level.
The server notification trigger must be MD5 hashed with DM server credentials
The server MD5 nonce must be renewed in each DM session. The DM client sends the new server nonce for the next session to the server over the Status element in every DM session.
For more information about Basic or MD5 client authentication, MD5 hash and MD5 nonce, see the OMA Device Management Security specification (OMA-TS-DM_Security-V1_2-20070209-A) available from this OMA Web site.
The server must support HTTPS.
For a non-customized device, the server must bootstrap the device over-the-air (OTA) with DM server account information and corresponding data connectivity settings using OMA Client Provisioning XML through WAP Push over SMS message. This requires the OEM to enable OTA bootstrap for the device.

See Also