Deploying to Symbian devices

Deployment using OMA DM:

Bootstrapping Symbian devices is supported, and Symbian devices should be able to pick the correct DME client for installation.

Silent installation and upgrade of the DME client is supported. Note that the root certificate used for signing the DME server's SSL certificate must be present on the device. The root certificates of major commercial providers of SSL certificates, such as VeriSign, Thawte, Entrust.net are normally present on all devices. When using a self-signed SSL certificate, the appropriate root certificate must be installed on the device before bootstrapping can occur.

Note also that in order to be able to upgrade the client using OMA DM, the security setting Prevent uninstall of DME Client must be Disabled for the device. This is done on the server. This is due to the fact that the client is uninstalled before the upgrade, and the client is unable to tell if it is the user or the DM process that is performing the uninstall. We are working on a resolution to this.

Installation of non-DME software is supported.

Deployment using SMS/WAP push:

Both SMS and WAP push are supported. However, when using a WAP push, the device tends to select a WAP access point for downloading the client. This will in some cases fail. When using SMS push, the device uses whichever access point that is already configured for the browser.

Other modes of deployment:

The DME client and other software can be deployed in other ways:

Next topic

Deploying to UIQ devices