1、Step By Step Guide to Deploying Microsoft Mobile Messaging: AppendicesPublished: March 3, 2005Applies To: Microsoft Exchange Server 2003 Service Pack 1Page 1The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publi
2、cation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.This white paper is for informational purposes only.
3、MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.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 transmitte
4、d 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 s
5、ubject 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. 2005 Microsoft Corporation. All rights reserved.The ex
6、ample companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred.Micros
7、oft, Active Directory, ActiveSync, BizTalk, Hotmail, JScript, MS-DOS, MSDN, MSN, Outlook, SharePoint, Visio, Visual Basic, Visual Studio, Windows, Windows Media, Windows Mobile, Windows NT, Windows Server, and Windows Server System are either registered trademarks or trademarks of Microsoft Corporat
8、ion 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.Page 2ContentsAppendix A: Troubleshooting Microsoft Exchange 2003 ActiveSync .1Introduction.1Server Configuration.1Device Configuration.2Sync P
9、rotocol Version and Device Support.4SSL Requirement.5Exchange ActiveSync Profile .10Exchange ActiveSync Checklist.11Device Logging .15Server Logging .18Error Message, Explanation, and User Action .19Frequently Asked Questions and Answers.31Complete List of Errors.34Common Issues and Associated KB Ar
10、ticles.37Appendix B: Windows Mobile Client Configuration Guide .38Setting Up Exchange ActiveSync.38To Set Up EAS on a Cradled Device (recommended method) .38Set Up with an Existing Partnership .43Uncradled Device EAS Setup.48Up-to-Date Notifications (UTD).49Appendix C: ActiveSync Data Architecture A
11、 Reference .62Appendix D: Resources.66Page 3Appendix A: Troubleshooting Microsoft Exchange 2003 ActiveSyncIntroductionExchange ActiveSync (EAS) This appendix is focused on troubleshooting Exchange ActiveSync connections from both the server and client perspective. It was developed by Microsoft Produ
12、ct Support Services as part of their experience in supporting Windows Mobile-based devices. Page 1Server ConfigurationExchange ActiveSync is installed by default with Exchange 2003. No server side configuration is necessary. If you have a single Exchange server and wish to use Exchange ActiveSync wi
13、th Forms Based Authentication or have an SSL requirement on the Exchange virtual directory, please use the additional configuration steps described later in this document.Enabling Users for Exchange ActiveSyncAll users are enabled by default. The Exchange administrator can globally disable Exchange
14、ActiveSync by unchecking “Enable user initiated synchronization”. This setting is configurable in Exchange System manager under Global Settings, Mobile Services.This setting is also available on individual user objects. Page 2Users can be enabled/disabled on a per user basis through the Exchange Fea
15、tures tab in AD Users and Computers. It is possible to enable or disable users in bulk by multi-selecting users and choosing enable or disable.Device ConfigurationTo set up Exchange ActiveSync on the client1. Set up a data connection for your device running Windows Mobile 2002 or 2003 software. 2. S
16、et up your device to sync with your Exchange 2003 server by typing in the URL of the server in the Use this server section. In the example below is used.3. Provide your credentials. Page 34. Sync manually or set up a schedule for synchronization.If you are using a device with Windows Mobile 2003 so
17、ftware, you can use the Up-to-Date Notification functionality included with Exchange 2003 server. Up-to-Date (UTD) is a new feature in Exchange Server 2003 that provides the user with the ability to automatically synchronize the mobile device with the server as new items are received on the server.P
18、age 4Sync Protocol Version and Device SupportExchange ActiveSync uses the AirSync protocol for synchronization. Exchange ActiveSync requires that the client (device) and the server use the same protocol version. Mobile Information Server uses the AirSync Protocol v1.0 for ActiveSync. Exchange Server
19、 2003 uses the new and improved AirSync protocol v2.0 for ActiveSync, but also supports AirSync protocol v1.0 for backward compatibility.Server Protocols supportedMobile Information Server 2002 1.0Exchange Server 2003 1.0 and 2.0Devices with Windows Mobile 2002 software (such as Pocket PCs and Smart
20、phones) use AirSync protocol v1.0 for ActiveSync. Devices with Windows Mobile 2002 software can be used against MIS and Exchange Server 2003 using v1.0.Devices with Windows Mobile 2003 software (Pocket PCs and Smartphones) support v1.0 and v2.0 protocols. They negotiate the protocol with the server.
21、Device Protocols supportedWindows Mobile 2002 1.0Windows Mobile 2003 1.0 and 2.0Therefore Windows Mobile 2002 and 2003-based devices can be used against MIS and Exchange 2003. Server Devices supportedMobile Information Server 2002 Windows Mobile 2002 and 2003Exchange Server 2003 Windows Mobile 2002
22、and 2003ImplementationExchange ActiveSync (EAS) is implemented as an ISAPI extension. The AirSync Protocol was developed to allow the synchronization of mobile devices with servers. The client and server use this protocol to communicate changes to each other. The AirSync Protocol rides on top of the
23、 HTTP protocol and uses the message body area of the HTTP protocol to send and receive changes. The protocol itself is a collection of commands and parameters expressed in XML. Aplication Sync egineAirSync protclCliet ervrAirSyc protclHTP HTPC/IC/IPage 5SSL RequirementPocket PCs with Windows Mobile
24、2002 Software The Exchange ActiveSync client on a device with Windows Mobile 2002 software is hard coded to use SSL. Therefore an SSL certificate should be installed on Exchange 2003 server or the Exchange 2003 front-end server to terminate the SSL connection, unless the SSL session is terminated be
25、fore it reaches the Exchange server.The Exchange ActiveSync client does certificate validation. The following is a list of root certificates installed by default on Pocket PCs with Windows Mobile 2002 software: Verisign/RSA Secure Server Verisign Class 1 Public Primary CA Verisign Class 2 Public Pri
26、mary CA Verisign Class 3 Public Primary CA Verisign Class 3 Public Primary CA (2028) GTE Cybertrust ROOT GTE Cybertrust Solutions ROOT Thawte Server CA Thawte Premium Server CA E Secure Server E CA (2048 bit)If you are using a certificate that is not signed by a CA listed above (not trusted on the W
27、indows Mobile 2002 software), you can disable certificate validation on the device by running the CertChk.exe tool. The Disable Certificate Validation tool can be used in a test environment and is part of the Exchange 2003 All-in-one Tools package available fromhttp:/ 6Pocket PCs with Windows Mobile
28、 2003 SoftwareThe Server ActiveSync client on Pocket PCs with Windows Mobile 2003 software does not require SSL. There is a check box on the client “This server uses secure connections (SSL)” to enable SSL. It is highly recommended that SSL be used to secure communications.When you uncheck the box “
29、This server uses secure connections (SSL)” you will receive the following warning.The following is a list of root certificates installed on Pocket PCs with Windows Mobile 2003 software: Equifax Secure Certificate Authority Verisign Class 2 Public Primary CA Verisign Class 3 Public Primary CA GTE Cybertrust ROOT GTE Cybertrust Solutions ROOT Thawte Server CA Thawte Premium Server CA E Secure Server E CA (2048 bit) GlobalSign Root CA
