Managing Devices

Send Feedback

Managing a device involves configuring the device after the initial OS is put in ROM. 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, such as 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 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 software available in ROM or installed over the air.
  • Activate or update software available in read-only memory (ROM) or installed over the air.

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.

In This Section

  • Best Practices in Managing Devices
    Lists general best practices for device management.
  • Device Management Architecture
    Explains the overall architecture of device management, including the Configuration Manager, Push and Short Message Service (SMS) routers, etc. This section also describes the architecture and support of OMA Client Provisioning (previously WAP), and OMA Device Management.
  • Configuration Service Providers
    Describes Configuration Service Providers and the metabase. This section also provides XML examples for the various Configuration Service Providers.
  • Security and Device Management
    Discusses the security features provided by device management, and how device management uses security policies.
  • Device Management Migration
    Presents information that is important to know if you are migrating from one version of Windows Mobile to another.
  • Security
    Discusses the Security model for Windows Mobile-based devices.
  • Bootstrapping Windows Mobile-Based Devices
    Describes the bootstrap procedure that provisions the device with the required connectivity data to enable access to OMA Websites, WAP Web sites, Internet Web sites, and any third-party corporation services.
  • Device Configuration API
    Allows ISVs remote access to the configuration management components of a Windows Mobile-based device.

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.