Share via


Provisioning From a Desktop Computer Using Remote API and ActiveSync

Smartphone and Pocket PC can be bootstrapped from a desktop computer by means of a desktop configuration tool. Smartphone can also be bootstrapped by means of the desktop configuration wizard.

If the Smartphone or Pocket PC device is cradled to the desktop computer, the device can be bootstrapped by means of a desktop configuration tool — Rapiconfig.exe. Either the mobile operator or the corporate manager can use this method to bootstrap the device. For more information about using this tool, see the readme.htm file in the Smartphone or Pocket PC SDK \tools directory.

Benefits   Using this method, the mobile operator is not required to preconfigure the device at the manufacturer or to provide an OTA framework that supports WAP push and the WAP Provisioning Bootstrap requirement.

Drawbacks   The device must be cradled.

Mobile operators or corporate administrators generate the provisioning XML and use methods described in Creating the Provisioning XML for Signed Binary Files to deliver the XML to the device.

After the file is loaded to the device, Configuration Manager is called to process the configuration data so that the device is bootstrapped before it is delivered to the user.

If the mobile operator wants to continuously provision the device with the signed .cpf file after the device is delivered to the user, the provisioning XML file should contain a certificate that is assigned the Manager role. The provisioning file should also contain XML for updating the Grant Manager policy. This update prevents any user authenticated messages from modifying the settings that are assigned the Manager role after the device has been bootstrapped. In this scenario, only the corporation or operator can manage the settings by using signed .cpf files.

For information about certificates and security roles, see Security Policies and Roles.

See Also

Options for Delivering Provisioning XML Files to Windows Mobile Devices

Last updated on Friday, April 22, 2005

© 2005 Microsoft Corporation. All rights reserved.

Send feedback on this topic to the authors.