Contents Microsoft® Exchange Server 2003 Exchange ActiveSync® (EAS) 1 Sync Client Architecture 5 Object Management on the Device 7 Sync Protocol Versions and Device Support 8 Sync Protocol Negotiation 9 SSL 11 Sync Protocol Commands 13 Performance Counters 22 Synchronization and DAV Replication 28 Device Logging 30 Up to Date Notification 32 Administrative Tasks 33 Device Provisioning 38 Device Info XML 42 Lab 4.1: Configuring ActiveSync 46 Exercise 2 47 AUTD 48 OMA Sink 49 Batching of Notifications 51 Performance Counters 53 Known Issues 58 Lab 4.2: Setting Up AUTD 62 Module 4: Mobility Sync/Push Last Saved: 7/18/2003 12:03 PM Last Printed: 7/18/2003 6:59 PM Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.  2002 Microsoft Corporation. All rights reserved. Microsoft, MS-DOS, Windows, Windows NT, ActiveSync®, ActiveSync® 3.7, Microsoft® Exchange Server 2003, Microsoft® Mobile Services, Microsoft® Outlook® Mobile Access, Microsoft® Outlook® Web Access, Microsoft® Product Support Services, Microsoft® Server ActiveSync®, Microsoft® Small Business Server, Microsoft® Windows® Powered Pocket PC 2002, Microsoft® Windows® Powered Pocket PC 2002 Phone Edition, Microsoft® Windows® Powered Pocket PC 2003, Microsoft® Windows® Powered Smartphone, and MSN™ Internet Access are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. Module 4: Mobility Sync/Push 1 Last Saved: 7/18/2003 12:03 PM Last Printed: 7/18/2003 6:59 PM Microsoft® Exchange Server 2003 Exchange ActiveSync® (EAS) Exchange ActiveSync allows you to synchronize data between your mobile device and Exchange Server 2003. Email, contacts and calendar information (PIM data) can be synchronized with the Exchange Server. This feature was previously available through Mobile Information Server (MIS) and was referred to as Microsoft® Server ActiveSync® or MSAS. It has now been integrated with Exchange Server 2003. With MIS, devices running Microsoft® Windows® Powered Pocket PC 2002, Microsoft® Windows® Powered Pocket PC 2002 Phone Edition, and Microsoft® Windows® Powered Smartphone had the Server ActiveSync client component installed and were supported. With Exchange ActiveSync, devices running Pocket PC 2002, Pocket Phone Edition and Smartphone are still supported. In addition, Microsoft® Windows® Powered Pocket PC 2003 devices are supported. Pocket PC 2003 devices allow more granularity in scheduling sync and also support the Always Up To Date functionality that is introduced in Exchange Server 2003. Overview 2 Module 4: Mobility Sync/Push Last Saved: 7/18/2003 12:03 PM Last Printed: 7/18/2003 6:59 PM Module 4: Mobility Sync/Push 3 Last Saved: 7/18/2003 12:03 PM Last Printed: 7/18/2003 6:59 PM Enabling Users for Synchronization All users are enabled by default. The Exchange administrator can globally disable sync for all users. This is configurable in Exchange System manager under Global Settings/Mobile Services. Enable user initiated synchronization - Selecting this checkbox allows users to synchronize their Exchange information with their mobile device. 4 Module 4: Mobility Sync/Push Last Saved: 7/18/2003 12:03 PM Last Printed: 7/18/2003 6:59 PM Enable up-to-date notifications - Selecting this checkbox allows users to receive AUTD notifications in order to keep their mobile device up to date with information on their Exchange server. When the administrator changes the settings on this page, changes are written to the msExchOmaAdminWirelessEnable attribute on the Microsoft® Outlook® Mobile Access (OMA) container in Global Settings. This setting is also available on individual user objects. Users can be enabled/disabled on a per user basis through the Exchange Features tab in AD Users and Computers. Files installed with Exchange ActiveSync In Exchsrvr\bin folder:  Massync.dll - OMA Sync ISAPI extension DLL  Masperf.dll - OMA Sync Performance Counter DLL  MasPerf.ini - OMA Sync Performance Counter INI  Masperf.h - OMA Sync Performance Counter header  Exchsrvr\OMA\Sync is a blank folder so if someone tries to gain access to the sync folder, it is mapped to a folder that does not give access to all of the Exchange files. Module 4: Mobility Sync/Push 5 Last Saved: 7/18/2003 12:03 PM Last Printed: 7/18/2003 6:59 PM Sync Client Architecture The sync protocol is a request/response protocol built on a client/server communications model. It is built on the HTTP protocol, using the HTTP POST request/response mechanism and the HTTP OPTIONS command. The HTTP POST header specifies a protocol command and, if the command requires it, command data is sent in the HTTP POST body. The data is usually formatted as compressed Wireless Binary XML (WBXML), which makes efficient use of the constrained bandwidth of mobile clients. The client initiates communication by posting a request. When the server receives the request, it parses the request and then sends an HTTP POST response containing the requested data in its body. The sync protocol requires a TCP/IP connection between the client and server. The underlying network layers, however, are implementation-specific. Three common transport layers that support the protocol are GPRS, CDMA 1xRTT and IEEE 802.11. The sync protocol requires that any transmission errors be handled by the networking software, and that the protocol messages sent between the client and server be complete and error-free. The sync protocol is designed to enable any mobile client to efficiently synchronize PIM data with data stored on an Exchange server. To achieve this, the client uses the sync protocol to talk to the Exchange front-end server component, which provides the synchronization engine as well as the means to retrieve data from the Exchange stores. Figure 1 shows the functional components of the client/server communications model used by the sync protocol. 6 Module 4: Mobility Sync/Push Last Saved: 7/18/2003 12:03 PM Last Printed: 7/18/2003 6:59 PM Figure 1 Protocol communication between the client and server The following steps occur for all commands the client sends to the server: 1. The client creates a request and sends it to the sync server as an HTTPS POST. 2. The sync server processes the request, communicating with the Exchange back-end server to access the user’s PIM data. 3. The sync server creates a response and sends it to the client as an HTTPS POST response. 4. The client processes the response and, if necessary, updates the local PIM data. The following steps occur when the client sends a Sync command: 1. The client identifies any changes made to local PIM data since the last sync. 2. The client creates a Sync command containing these changes. 3. The client sends the command to the sync server as an HTTPS POST. 4. The sync server identifies changes made to data on the server since the last sync, communicating with the Exchange back-end server to access the user’s data. 5. The sync server resolves any conflicts between changes made to items on the client and on the server. 6. The sync server creates a response containing server changes to be replicated on the client. 7. The sync server sends the response as an HTTPS POST response. The client processes the response and updates the local PIM data. Module 4: Mobility Sync/Push 7 Last Saved: 7/18/2003 12:03 PM Last Printed: 7/18/2003 6:59 PM Object Management on the Device PIM data is stored in “collections” – one for contacts, one for calendar, and one for each e-mail folder. The sync protocol supports syncing multiple e-mail folders. For each collection, the client software stores a SyncKey, which contains 39-48 characters, 38 for the globally unique identifier (GUID), and 1- 10 for the incrementing number. The client also stores a CollectionId, which is a string around 40 characters for each folder as a unique identifier for the folder. The client sends the SyncKey to the server with each sync request. Each object that is synced – message, contact or calendar item – has a unique identifier assigned by the server. This ServerId is a 48-character string that is stored by the client. The identifier is used during sync to identify objects that are stored on both the client and server. 8 Module 4: Mobility Sync/Push Last Saved: 7/18/2003 12:03 PM Last Printed: 7/18/2003 6:59 PM Sync Protocol Versions and Device Support ActiveSync requires that the client and the server use the same protocol version. Mobile Information Server uses the AirSync Protocol v1.0 for ActiveSync. Exchange Server 2003 uses the new and improved AirSync protocol v2.0 for ActiveSync, but also supports AirSync protocol v1.0 for backward compatibility. Server Protocols Supported Mobile Information Server 2002 1.0 Exchange Server 2003 1.0 and 2.0 Pocket PC 2002 client uses AirSync protocol v1.0 for ActiveSync. It can be used against MIS and Exchange Server 2003 using v1.0. Pocket PC 2003 client supports v1.0 and v2.0 protocols. It can negotiate the protocol to be used. Device Protocols Supported Pocket PC 2002 1.0 Pocket PC 2003 1.0 and 2.0 Therefore Pocket PC 2002 and Pocket 2003 devices can be used against MIS and Exchange 2003. Server Devices Supported Mobile Information Server 2002 Pocket PC 2002 and Pocket PC 2003 Exchange Server 2003 Pocket PC 2002 and Pocket PC 2003 [...]... deletes, and fetches (within the sync command) processed per second by Exchange ActiveSync Last Saved: 7/18/2003 12:03 PM Last Printed: 7/18/2003 6:59 PM 28 Module 4: Mobility Sync/Push Synchronization and DAV Replication Synchronization or Replication in the Document Authoring and Versioning (DAV) context is the client-initiated process of fetching the manifest of a collection, downloading the changed resources... resourcetag associated with that particular resource is updated Definitions Resource Last Saved: 7/18/2003 12:03 PM Last Printed: 7/18/2003 6:59 PM Module 4: Mobility Sync/Push 29 A resource is an object in the namespace that is referred to by a URI Resources include documents, collections, etc Repl-uid A repl-uid is a universally unique identifier that identifies a DAV resource The value of this property... archy,CreateCollection,DeleteCollection,MoveCollection,Fold erSync,FolderCreate,FolderDelete,FolderUpdate,MoveItems,Get ItemEstimate,MeetingResponse,Notify Last Saved: 7/18/2003 12:03 PM Last Printed: 7/18/2003 6:59 PM Module 4: Mobility Sync/Push 11 SSL PPC 2002 The Server ActiveSync client on a PocketPC 2002 device is hard coded to use Secure Sockets Layer (SSL) Therefore an SSL certificate should be installed on Exchange 2003... Microsoft Mobile Information Server 2002 CD for PPC 2002 or certchk for PPC 2003 available in the Exchange 2003 Web Releases Last Saved: 7/18/2003 12:03 PM Last Printed: 7/18/2003 6:59 PM 12 Module 4: Mobility Sync/Push See the readme that is provided with the CAB file for more information Using the CAB file does not remove the requirement for a certificate It simply disables certificate validation... ActiveSync presents the ticket to the backend Exchange server 4 Information is retrieved from the back end and returned to the device Last Saved: 7/18/2003 12:03 PM Last Printed: 7/18/2003 6:59 PM Module 4: Mobility Sync/Push 13 Sync Protocol Commands With Sync protocol v1.0, a typical sync session includes the following commands GetHierarchy GetItemEstimate Sync The GetHierarchy command is used to retreive... parameters, including the command name HTTP Header Additional parameters used by the server are transmitted in standard HTTP format Last Saved: 7/18/2003 12:03 PM Last Printed: 7/18/2003 6:59 PM 14 Module 4: Mobility Sync/Push HTTP Body URI Data needed by the command The format varies by command, and some commands have no body The following example shows a typical sync request URI: POST /Microsoft-Server-ActiveSync?User=johndoe&... the body contains an e-mail attachment, the format depends on the type of the attachment file Some commands do not use the body Last Saved: 7/18/2003 12:03 PM Last Printed: 7/18/2003 6:59 PM Module 4: Mobility Sync/Push Sync Command 15 This section shows an example of a sync request from a client, and the matching sync response that a server might return The example sync request contains those contacts... ServerId as the permanent identifier for the contact The ServerId is included in the response sent by the server to confirm the Add Last Saved: 7/18/2003 12:03 PM Last Printed: 7/18/2003 6:59 PM 16 Module 4: Mobility Sync/Push (see below) The ApplicationData contains the contact itself and details are omitted here It consists of XML data for the contact name, address, phone number, and so on 333333333... ClientId matches the ClientId sent with the original Add command from the client The ServerId is a new permanent identifier allocated by the server and must be stored by the client At this point, Module 4: Mobility Sync/Push 17 it’s up to the client to keep this mapping between the original ClientId and the new ServerId The Status value of 1 indicates the operation was successful 333333333... server response provides a list of all non-hidden collections and their corresponding CollectionIds This is for v1 of the protocol Last Saved: 7/18/2003 12:03 PM Last Printed: 7/18/2003 6:59 PM 18 Module 4: Mobility Sync/Push Command Description FolderSync Syncs the collection hierarchy This command works similarly to the Sync command The folder list has a SyncKey After the initial folder sync, subsequent . Overview 2 Module 4: Mobility Sync/Push Last Saved: 7/18/2003 12:03 PM Last Printed: 7/18/2003 6:59 PM Module 4: Mobility Sync/Push 3 Last. Setting Up AUTD 62 Module 4: Mobility Sync/Push Last Saved: 7/18/2003 12:03 PM Last Printed: 7/18/2003 6:59 PM Information in this document, including