Share via

Managing Windows Mobile Devices

  • Article

4/8/2010

Managing a device involves configuring the device after the initial operating system (OS) is put in ROM. The initial image placed in ROM is the bootstrap image. You can then manage the device from a remote location through continuous provisioning by using a device management (DM) server.

The mobile operator, corporation, or user can perform the following tasks, depending on the security policy set by the device manufacturer:

  • Configure the device to change functionality. For example, change settings related to phone functionality.
  • Change core configuration and registry settings.
  • Set the security policy on the device to limit or control functionality. For example, the policy may state that only applications that have been signed can run, or it may prevent an application from running.
  • Change device configuration settings, sometimes transparent to the users, over Open Mobile Alliance (OMA) Client Provisioning (WAP-based) or OMA DM protocols.
  • Offer new services that may require adding or changing device settings.
  • Reduce the total cost of ownership (TCO). You can use commercial servers that can manage devices from multiple vendors.
  • Update operating system components, including executable files.
  • Personalize and add user interface (UI) components.
  • Configure, add, update, and remove software.
  • Activate or update software available in ROM or installed over the air (OTA).

The following table shows the two major ways in which you can manage devices.

Way of managing devices Description

Provision a device with XML

You can manage a device by provisioning it. Provisioning a device involves creating a provisioning XML file that contains configuration information, and then sending the file to the device. Configuration Manager and Configuration Service Providers on the device then configure the device based on the contents of the provisioning XML file. For more information, see Understanding Provisioning.

Your OEM can also place your provisioning XML files in ROM to be processed during cold boot or put it in an Image Update package to be processed during the image update process.

Update a device by using OTA Firmware Update

If the OEM used the Image Update technology to create updatable regions in the OS, then the regions can be updated.

To update a device by using an OTA Firmware Update, you should determine what to change (configuration settings, customization, registry keys, or security settings) and then notify the OEM.

Update packages are created by the OEM. For information about how the packages are downloaded to a device, see Understanding OTA Firmware Update.

> [!NOTE] > Settings updated through Image Update persist after cold boot; over-the-air provisioned settings persist after a warm boot, but do not persist after a cold boot.

In This Section

  • Understanding Provisioning
    Describes the concepts of provisioning a device, including the architecture, protocols, and available services.
  • Understanding OTA Firmware Update
    Describes how Windows Mobile handles OTA firmware update at the various component levels, and contains scenarios and FUMO result codes.
  • Client Services
    Describes client services that are available for Windows Mobile devices.

  • How To Topics for Managing Devices
    Describes how settings can be customized for branding, security, or convenience. The topics in this section will help you understand what can be configured and how to modify the configuration.

    This section includes instructions about how to bootstrap and customize a device. It also provides information about how to configure a device after manufacture.

  • Migration for Managing Devices
    Describes the changes in features, architecture and protocols from earlier versions as they relate to Managing Devices.