Provisioning with runtime configuration
The previous methods of provisioning the phone through OMA Client Provisioning files built into your phone image, or through Automatic Data Configuration, have been deprecated. This section provides guidance about how to perform these provisioning tasks with the new runtime configuration mechanism. Additional topics with examples will be added in future documentation releases.
A sample OEM customization answer file can be found in the %WPDKCONTENTROOT%\Samples\Customization directory. This answer file shows several configured customizations and it imports two answer files that contain real connection settings data for AT&T and T-Mobile.
Enabling device management
To enable over-the-air provisioning by using WAP push, OEMs must bootstrap the phone with the mobile operator’s OMA Client Provisioning information, including the Trusted Provisioning Server (TPS) and the privileged Push Proxy Gateway (PPG) used by the TPS for continuous provisioning. |
|
OEMs are required to provision or bootstrap the phone with appropriate credentials to communicate with the mobile operator’s OMA DM server. |
Configuring data and MMS connection settings
You are required to configure phone settings correctly for their desired scenarios, such as phones targeted to single operators, open market phones, and phones that need to distinguish between operators and plans. At a minimum, this includes two groups of settings:
Generic-usage cellular data connection settings, including an APN and optionally a proxy.
MMS settings, including the address of the MMS server and relevant APN, proxy settings, and policy information.
For more information about how to configure these connectivity settings using runtime configuration, see Connectivity configuration.
Configuring internet sharing over Wi-Fi
You can configure internet connection sharing, in which the phone can be configured to share its cellular connection over Wi-Fi with up to eight client devices or computers.
For more information about how to configure internet sharing, see Internet sharing (hotspot).
Managing location services (SUPL and V2 UPL)
Configuration of Secure User Plane Location (SUPL) and V2 User Plane Location (V2 UPL) is available.
For more information about how to configure location services, see Location (SUPL and V2 UPL).
Setting security policy
Security policy settings for OMA Client Provisioning, MMS, Service Indication (SI), Service Loading (SL), and WAP push can be configured.
For more information about how to configure security policy, see Security policy.
Managing certificates
Certificates provide a credential to verify the identity of a phone, authenticate a service, or encrypt files or connections. Windows Phone has a set of preinstalled root certificates that are included in the phone’s certificate store. It is also possible to add intermediate, root, and self-signed certificates to the phone by using provisioning. Windows Phone supports separate certificates for development and release-quality builds.
For the list of certificates that are preinstalled on the phone, see Preinstalled SSL root certificates. For more information about the locations in which certificates are saved on the phone, see Certificate stores on the phone.
These certificates are different from those used for verifying the publisher of an application. The Windows Phone Dev Center provides the code-signing services for phone applications. These certificates are also different from the certificates used in package and code signing.
For more information about how to add certificates to the phone during runtime configuration, see Adding certificates to the phone.