How to Configure the Device
A device with MSFP automatically switches from SMS to direct push technology when it synchronizes with ActiveSync.
No additional software or server installations are required other than Exchange Server 2003 SP2. By default, the direct push technology is enabled for all users. The Exchange administrator can use the Exchange System Manager to enable or disable the technology for groups or individual users.
You can use many methods to update the direct push settings on the device. This section describes the following methods:
OEM configures ROM
You can have the OEM build your OS with the desired settings. In this case, the OEM would configure the registry.
You create an XML and get it to the device
You can create an XML to change the device settings. This method allows you to test the change and then update the device without relying on the OEM and the build process.
You can then put the XML on the device by one of the following methods:
Typically, you would use the CAB file packaging method for the following delivery methods:
- Installing the provisioning XML from a memory card, using the autorun feature and a Secure Digital Multimedia Card (SD/MMC).
- Pushing the file using a Service Indication (SI) message, or automatically downloading the file using Service Location (SL).
- Pulling by the device in response to E-mail or Short Message Service (SMS), or by a user downloading it over HTTP or HTTPS (Internet Explorer Mobile).
- Downloading the provisioning XML file from the desktop, using the Remote Application Programming Interface (RAPI) in ActiveSync. This method is supported only when the provisioning file is contained in a CAB file
You can sign the .cab file by using the Microsoft Authenticode® signing tools. This enables a role mask to be assigned to the provisioning request based on the role mask stored with a matching certificate on the device.