Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Continuous provisioning is the on-going provisioning of a mobile device. That is, updating or changing configuration settings and applications, as required, over time. Bootstrapping is initially configuring a device so that it can be continuously provisioned by a trusted agent.
Bootstrapping a Windows Mobile-based device usually involves configuring the device with the following information:
- Trusted Provisioning Server (TPS)
- Trusted Push Proxy Gateway
- WAP Connectivity
- GPRS/1xRTT connectivity
- Changes to the default security model
It may also include configuring other settings such as Browser Favorites, TAPI, Locale, Clock, and Registry.
In This Section
- Bootstrapping To Use An OMA DM Server
Discusses how to configure a device to recognize an OMA DM server as a Trusted Provisioning Server for continuous provisioning - Bootstrapping To Use an OMA Client Provisioning Server
Discusses how to initially configure a device for OMA Client Provisioning continuous provisioning. - Bootstrapping To Use a CPF File
Discusses how to initially configure a device to be continuously provisioned by allowing a user to pull a CAB Provisioning Format (.cpf) file to the device rather than using a OMA Client Provisioning or OMA DM server to push the provisioning files. - Enabling OTA Bootstrapping
Discusses how to enable OTA bootstrapping which is disabled by default. - Enabling Remote API (RAPI) Bootstrapping
Discusses how to enable RAPI, which is restricted by default, for bootstrapping via a desktop computer and ActiveSync. - Bootstrap Security
Provides a brief overview of the security issues that must be considered during the bootstrap process.
Send Feedback on this topic to the authors