Using Windows Mobile 5.0-based devices with the Messaging and Security Feature Pack (MSFP) provides an enhanced Outlook Mobile Experience.
Direct push Technology
Direct push is a real-time solution in which the client, that is a Windows Mobile 5.0–based device with MSFP installed, uses a Hypertext Transfer Protocol Secure (HTTPS) Internet connection to establish and maintain a direct connection with Exchange Server 2003 Service Pack 2. This technology replaces Always Up to Date (AUTD) which used Short Message Service (SMS) messages to keep data synchronized. There is no longer a reliance on SMS for notification.
The direct push technology has two parts: one part resides on the device, and the other resides on an Exchange Server SP2 mail server. The following list describes these parts of the technology:
- Windows Mobile–based client with MSFP. ActiveSync technology in the device manages the direct push communication with Exchange Server. It establishes an HTTPS connection with the server, and then periodically sends traffic on it so that the connection remains open. The rate at which this occurs is dynamically adjusted based on parameters set by the OEM or Operator in order to optimally balance battery life with the timeliness of data synchronization.
- Exchange Server 2003 Service Pack 2. This version of Exchange Server includes a direct push component that runs alongside the existing ActiveSync infrastructure that supports manual and scheduled synchronization. Exchange Server uses IP-based notifications to deliver e-mail, contact, calendar, and task updates to a device as soon as the information arrives at the server.
Direct push is easy to configure and manage. A device with MSFP automatically switches from SMS to direct push technology when it synchronizes with ActiveSync.
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.
No additional software or server installations are required other than Exchange Server 2003 SP2.
Best Practices for the Direct Push Technology
The following list shows best practices for the direct push technology:
- IIS and Firewall https connection timeouts to the ActiveSync virtual directory should be 15 to 30 minutes.
- Users having an unlimited data connection (GPRS) with their mobile operator service plan is highly recommended. This allows the device to keep an IP based HTTP connection with the server alive at all times within the coverage area, which allows for a faster and more reliable email experience.
Global Address List Access
Users can view information over the air that is in the global address list (GAL) stored on Exchange Server. They can search remotely for a person based on name, company, or other property. Users will get all of the information they need to reach their contacts without having the data store on their device.
Note GAL information can only be viewed while online; it can not be stored on a device for viewing offline.
GAL Lookup has been designed for easy access from Contacts and Contact Chooser. Contact Chooser can be accessed from within Messaging, Phone, Calendar and Speed Dial.
The following list describes a typical user scenario using GAL Lookup for a contact:
- The user opens Contacts on their device, and then searches for a person by name.
- When the person is not found within the local device contacts, the user then choose Find Online to use GAL Lookup to find the person within the Exchange database.
A list of the closest matches to the entry is displayed so that
- The user can select the desired contact from a list that displays the closest matches to the entry, and then call , send an SMS, or email them.
Note Although the entire GAL cannot be stored on the device, once the contact is found, the user can add the single contact to their local device if desired.
Requirements for GAL
- Users must have some type of data connection (GPRS or desktop pass-through using ActiveSync 4.1) in order to use the GAL functionality.
See Also
Messaging and Security Feature Pack Overview | Administering the Messaging and Security Feature Pack
Send Feedback on this topic to the authors
Feedback FAQs
© 2006 Microsoft Corporation. All rights reserved.