Microsoft Lync Server 2010 Understanding Exchange Integration

Microsoft Lync Server 2010
Published: May 2011
Understanding and Troubleshooting Microsoft Exchange Server Integration
Dave Howe, MCSE Senior Support Escalation Engineer Microsoft Corporation - Charlotte NC, USA daveh@microsoft.com
This document is provided as-is. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred. This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. Copyright 2011 Microsoft Corporation. All rights reserved.
Table of Contents
Purpose ......................................................................................................................................................... 1 Features Overview ........................................................................................................................................ 2 Voice Mail ................................................................................................................................................. 3 Contact Search .......................................................................................................................................... 3 Unified Contact Store................................................................................................................................ 3 Free/Busy .................................................................................................................................................. 3 Microsoft Exchange Delegates.................................................................................................................. 4 Working Hours .......................................................................................................................................... 4 OOF Message ............................................................................................................................................ 4 Conversation Environment ....................................................................................................................... 4 Types of Conversations ......................................................................................................................... 4 Conversation Categories ....................................................................................................................... 5 User Interface ....................................................................................................................................... 7 Conversation History............................................................................................................................. 9 Exchange Connectivity ................................................................................................................................ 12 Autodiscover Service............................................................................................................................... 13 Outlook Client ..................................................................................................................................... 14 UC Clients and Devices ........................................................................................................................ 16 Processing the Autodiscover Response .................................................................................................. 17 Caching Exchange URLs in Registry ......................................................................................................... 18 Retrieving Data from Microsoft Exchange Mailbox ................................................................................ 19 Reverse Proxy Pre-Authentication .......................................................................................................... 20 MAPI/EWS Error Handling ...................................................................................................................... 21 Feature Availability ................................................................................................................................. 22 UC Client Features (by Connection Type) ........................................................................................... 22 UC Device Features (by Connection Type) .......................................................................................... 23 Feature Impact ........................................................................................................................................ 23 UC Client Features (Connectivity Failures).......................................................................................... 23 UC Device Features (Connectivity Failures) ........................................................................................ 24 UC Device Features (Authentication Failures) .................................................................................... 25
UC Device Authentication ....................................................................................................................... 26 Strong User Authentication (SUA) ...................................................................................................... 26 Troubleshooting Exchange Integration ....................................................................................................... 28 Lync Configuration Information .............................................................................................................. 28 Outlook / Test E-mail AutoConfiguration ............................................................................................... 29 Checking the Registry for Cached EWS Data .......................................................................................... 30 How to Convert the AutoDiscovery TimeStamp ................................................................................. 31 Exporting EWS Configuration Information ............................................................................................. 32 Get Autodiscover Service Connection Points (SCPs)........................................................................... 33 Get Exchange Web Services Configuration ......................................................................................... 33 Get Exchange Certificate (from each Client Access Server) ................................................................ 34 Using Microsoft Exchange Synthetic Transactions ................................................................................. 35 How to Create a Client Access Server Test Account ........................................................................... 35 How to Test EWS Connectivity ............................................................................................................ 36 How to Test EWS Connectivity using Autodiscover ............................................................................ 36 How to Test MAPI Connectivity .......................................................................................................... 37 How to Test Outlook Connectivity to EWS ......................................................................................... 37 Analyzing the UC Device CELog File ........................................................................................................ 39 How to Collect and Analyze CELog Data ............................................................................................. 40 Collecting Microsoft Exchange Traces .................................................................................................... 42 How to Collect EWS Tracing ................................................................................................................ 42 Scenario: Integration Errors in Lync and on UC Phone (DNS) ................................................................ 46 Scenario: Integration Error on UC Phone (Certificates) ......................................................................... 47 Scenario: Integration Error on UC Phone (Permissions) ........................................................................ 47 Scenario: Integration Errors in Lync and on UC Phone (Corruption) ..................................................... 49 Appendix A: Lync / MAPI Error Strings ....................................................................................................... 50 Appendix B: Lync / EWS Error Strings ........................................................................................................ 52
Purpose
The purpose of this document is to introduce the reader to some of the new client features that are available whenever Microsoft Lync Server 2010 communications software is integrated with Microsoft Exchange Server 2010. Successfully integrating these two enterprise communications solutions can be challenging, especially considering that there are subtle differences in the way that services from each product are leveraged by Lync Server 2010 clients. I decided to write this document after troubleshooting several Exchange Server 2010 integration issues reported by Technology Adoption Program (TAP) customers during the Microsoft Lync Server 2010 Beta program. The information contained in this document is not intended to be authoritative with regard to this topic. Rather, this document can simply be described as a collection of information that Ive read from various product specifications as well as some general troubleshooting information. Thats all nothing more. Please note that this document does not cover Microsoft Lync 2010 instant messaging (IM) and Microsoft Exchange Outlook Web Access (OWA) integration. For details, see the following:
Enable Exchange 2010 SP1 Outlook Web App and IM Integration in the Microsoft TechNet Library at http://go.microsoft.com/fwlink/?LinkId=217004 Configuring Lync RC and Exchange 2010 SP1 to Enable OWA as a Lync Endpoint on Ilse Van Criekinges Weblog at http://go.microsoft.com/fwlink/?LinkId=217007 Exchange 2010 RTM/SP1 OWA IM Integration with Microsoft Lync Server 2010 on Jens Trier Rasmussens blog at http://go.microsoft.com/fwlink/?LinkId=217011
I hope that you find the information provided in this document to be helpful. Thanks! Dave Howe
Microsoft Lync Server 2010: Understanding and Troubleshooting Microsoft Exchange Server Integration
Features Overview
Lync 2010, as well as other unified communications (UC) clients and devices, interact with Microsoft Exchange and Microsoft Outlook to provide Microsoft Exchange-integrated features to the end user, including: Contact Information Calendar Information Conversation History Missed Conversations Missed Calls Voice Mail Playback
The following table shows a list of features by UC client: Feature Voice Mail Conversation History Missed Conversations Contacts Free/Busy Info Working Hours OOF Messages Lync 2010 Yes Yes Yes Yes Yes Yes Yes Office Communications 2007 R2 No No No Yes Yes No Yes Desktop phone Yes Yes (Call Logs) Yes Yes Yes No Yes
Two methods of connectivity with Microsoft Exchange are used to provide this array of integrated features to the user, Exchange Web Services (EWS) and Messaging Application Programming Interface (MAPI). MAPI has been the primary method used by clients to connect to Microsoft Exchange. To provide client-independent connectivity to Microsoft Exchange, EWS was introduced in Microsoft Exchange Server 2007 SP1. This method of Microsoft Exchange connectivity can be used by any client that supports XML/SOAP using a web interface. The cross-platform flexibility of EWS is an ideal solution for providing Microsoft Exchange integration for desktop clients as well as mobile desktop phones. The following sections provide additional detail about each of these features and their interactions with various versions of Microsoft Exchange.
Voice Mail
New in Lync 2010, this feature supports fetching and playback of voice mail messages from Microsoft Exchange through the phone environment. Voice mail retrieval is supported through EWS through a periodic poll (every three minutes, configurable through in-band provisioning). However, configurations without EWS cannot pull these items because MAPI does not support item retrieval. In these configurations, Lync retrieves the new voice mail count by using MAPI calls over a persistent connection.
Contact Search
Lync 2010 accesses the users contacts from Microsoft Exchange and merges this information with the Lync Contacts list in order to include Outlook and other contacts in the Lync client search results. All configurations of Lync and Microsoft Exchange support this feature, but the particular interface used depends on the specific configuration. For Exchange Server 2003, Exchange Server 2007, or Exchange Server 2010 without SP1, the contact feature proceeds through MAPI if it is accessible (changes are pushed instantly over a persistent connection) and through EWS if MAPI is not accessible (through a 15-minute poll for changes). For Exchange Server 2010 SP1, contacts proceed through EWS, where they are pushed over a persistent connection.
Unified Contact Store

With the Lync 2010 release, the Lync client has implemented a unified contact store, which unifies the Lync Contacts list with Outlook, and other contacts, by storing the shared list on Microsoft Exchange. This enables the Lync Contacts list information to be present across all of the users endpoints. Unified contact store is only available for Lync 2010 and Exchange Server 2010 SP1, through EWS. Unified Contacts are synchronized continuously through a persistent connection. In all other configurations, this feature is disabled.
Free/Busy
Microsoft Exchange serves as the centralized calendar information store for Microsoft Office products, and as a result, Lync pulls free/busy information for contacts from Microsoft Exchange. This data is sent through EWS if it is available and through MAPI if EWS is not available. Regardless of the interface, free/busy information is synchronized every 30 minutes by polling the server running Microsoft Exchange.
Microsoft Exchange Delegates

Delegate information is synchronized once each time a user signs into Lync. This feature proceeds through MAPI only; if MAPI is not available, it is disabled.
Working Hours
New in Lync 2010, working hours information is similarly drawn by Lync from Microsoft Exchange. This data is sent through EWS if it is available; there is no fallback to MAPI if EWS is unavailable. Free/busy information is synchronized every 30 minutes through a poll.
OOF Message
Out of Office (OOF) messages and information are pulled from Microsoft Exchange. This data is sent through EWS if it is available and through MAPI if EWS is not available. Regardless of the interface, OOF information is synchronized every 30 minutes through a poll.
Conversation Environment
One of the most important features offered through Microsoft Exchange integration is the conversation environment. The conversation environment provides an easy way for users to initiate a follow-up conversation with people based on missed and past conversations. The conversation environment is displayed as its own tab in the Lync user interface, and it should display nearly all forms of UC conversations. All past conversations are stored in the Microsoft Exchange mailbox of the Lync user (history and retention time is defined by managed Microsoft Exchange policies). This collection of past conversations is referred to as Conversation History.
Types of Conversations The types of conversations that will be displayed in the conversation environment include: Peer-to-peer instant messaging (IM) conversations Peer-to-peer calls Peer-to-peer video calls IM conference (multi-party IM) Conference call (multi-party audio/video conversations) 4
Adhoc collaboration session (including file and screen sharing) Scheduled (and attended) collaboration session
Conversation Categories There are two different categories of conversations that are displayed in the conversation environment: Active Voice Conversations Displays active conversations with a voice component. Conversations are considered active voice conversations if they are voice-involved conversations that the user is a current participant of (for instance, if the conversation window is open and a voice-involved conversation is ongoing). These conversations are sorted by most recent start time (most recent at the top).
Other Conversations Displays all other conversations, sorted chronologically. For voice conversations, the timestamp is the start time of the conversation; for non-voice conversations, the timestamp is the time of the most recent communication. These conversations can fall into one of the following groups, but the groups are not separated or delineated in any way. Active non-voice conversations These are conversations that are currently active, but do not involve voice. Missed conversations These are conversations that were missed while the user was away from the desk, were ignored, or werent responded to in time. Conversations are represented as missed conversations only after they are written in the Conversation History folder stored in the Microsoft Exchange mailbox of the Lync user. All missed IM and conference calls are written in the Conversation History folder by a Lync active end point, while the missed call logs are written by the Front End Server. Missed conversations roam, and they are displayed on all Lync end points. As with voice mail, item retrieval is supported through EWS through a periodic poll (every 15 minutes). However, configurations without EWS cannot pull these items since MAPI does not support item retrieval. In these configurations, Lync retrieves the unseen missed count via MAPI. These MAPI notifications are instantly pushed through to Lync over a persistent connection.
While there may be future support that will allow Lync to read missed conversation items through MAPI, for now only EWS provides retrieval of missed conversations from a given mailbox. Recent Conversations These are conversations from the users recent past in which the user participated (that is, not missed conversations). This is not a complete list of all past conversations but rather a preview of conversations that have happened in recent past. To avoid performance issues, Microsoft Lync 2010 Phone Edition will retrieve only 100 of the most recently archived conversation items. Recent conversations include both incoming and outgoing conversations. Although both EWS and MAPI can be used to write conversation items into a Microsoft Exchange mailbox, items can only be retrieved by using EWS.
User Interface The icon for the conversation environment can be found in the Launcher menu bar located near the top of the Lync window. As new conversations are received, the indicator for the number of conversations waiting acknowledgement is incremented by +1 in the UI.
The conversation environment window displays both Active and Past conversations. Additionally, a Pivot menu can be used to display either all items, only missed conversations, or only phone calls. Active items will be grouped at the top of the list, followed by Past items. Items will be sorted chronologically by time of most-recent activity, with voice and video conversations at the top.
In Outlook 2010, a user has the option of grouping email messages as well as Lync conversations by threads. Lync uses the conversation ID value to group conversation entries into threads. Only the most recent event in a given conversation thread will be displayed in the conversation environment window.
Conversation History Past conversations are archived and stored in the Conversation History folder in the Microsoft Exchange mailbox of the Lync user. Conversation History items appear similar to that of standard mail items, and as such, can be replied to by using Outlook. Likewise, each Conversation History item will have a Mode (IM, Call, or both), which will be displayed using a custom icon in the message header.
Conversation History Observer The Conversation History Observer is responsible for monitoring all of the various ongoing conversations in which the user is a participant, collecting all of the relevant information about each conversation. When archiving is needed, the Conversation History Observer creates a MailItem object containing the conversation data, and then it leverages a spooler component to write this information into the users mailbox.
Archiving Logic There are generally three rules which govern the behavior of the Conversation History Observer for conversations involving the local user: 1. A conversation starts when the first conversation mode gets connected. Whenever a conversation starts, it initializes monitoring of the conversation as it progresses, collecting data for a future archiving event. 2. A conversation ends when the last Mode is disconnected from the conversation. When the conversation ends, the observer performs an incremental archive of all data collected during the conversation. 3. A conversation is missed when an unsuccessful, outgoing conversation attempt is made. A missed/unsuccessful conversation archive is made in response to such events. Message Classes The following message classes are used by the Conversation History Observer when archiving a conversation or missed conversation to a Microsoft Exchange mailbox: IPM.Note.Microsoft.Conversation (IM, IM conferences) IPM.Note.Microsoft.Missed (Missed IM, Missed IM conferences) IPM.Note.Microsoft.Conversation.Voice (A/V calls, A/V conferences) IPM.Note.Microsoft.Missed.Voice (Missed A/V calls, Missed A/V conferences) Error/Failure Notifications Leveraging a background thread, archived conversations are serialized to disk by the Conversation History Observer as MailItem objects. The serialized MailItem objects are picked up by the History Spooler and are then written to the Conversation History folder in the users Microsoft Exchange mailbox.
10
In the event of an error condition, the user will be alerted using the following logic: 1. If the serialization of archived conversations fails, for example due to disk full condition, the user is informed; if this happens when the user is closing the conversation window, then the closing of the conversation window is blocked and user confirmation is requested. 2. If the History Spooler is unable to commit archived conversations to a users mailbox for 30 days, for example due to an offline server running Microsoft Exchange, the failure is reflected in the notification area of the Launcher menu bar.
11
Exchange Connectivity
Many of the features offered within Lync 2010 have dependencies on connectivity to a Microsoft Exchange mailbox. For example, the conversation environment feature leverages both Exchange Web Services (EWS) and MAPI to manage Conversation History items. Unlike previous versions of Lync, EWS is now the primary method used to provide Microsoft Exchange integration features for the Lync client. MAPI will be used if EWS is unavailable, but only in a limited capacity. The impact of this design can be significant for a given user, depending on the location of their mailbox. If the user has an Exchange Server 2003 mailbox, the Lync client will not be able to use EWS to interact with Microsoft Exchange. Rather, MAPI will be used in a fallback capacity to access the Microsoft Exchange mailbox. While the Lync client will be able to write new archived Conversation History items into the users mailbox, it will fail to retrieve any existing Conversation History items from the users mailbox. However, for a user whose mailbox resides on a server running Exchange Server 2007 SP1 or Exchange Server 2010, the Lync client will leverage EWS to provide the user with a complete experience for the conversation environment. Not only will EWS be used to write new archived Conversation History items into the users mailbox, but EWS will also be used to retrieve and display past Conversation History items to the user in the Lync client.
12
Autodiscover Service
The Autodiscover service is used to provide client applications internal and external URLs for accessing information offered by EWS. When you install the Client Access Server role on a computer that is running Exchange Server 2010, a new virtual directory named Autodiscover is created under the default website in Internet Information Services (IIS). Both the Outlook client and the Lync client use the Autodiscover feature of Microsoft Exchange to locate EWS within a given environment. However, there is a significant difference in the way each client searches for EWS, and this difference can impact the conversation environment feature within Lync. While Exchange Server 2010 supports both WSSecurity-based and SOAP/XML-based Autodiscover client requests, Exchange Server 2007 supports only legacy XML-based requests. Upon resolving the Autodiscover URL by using Domain Name System (DNS), the Lync client will send an initial unauthenticated dummy request to the Autodiscover URL. Using the information contained in the 401 response, the Lync client will detect whether the Autodiscover server is configured to support either WSSecurity or SOAP/XML requests. If the Autodiscover server only supports SOAP/XML requests, the Lync client will replace .xml in the Autodiscover URL with .svc and use it as the Autodiscover service URL (for example, https://autodiscover.contoso.com/autodiscover/autodiscover.svc). Lync will then construct a SOAP request and send it to the Autodiscover server to retrieve the internal and external EWS URLs. Please note that while Exchange Server 2007 can be configured to provide different URLs for the Availability Service and OOF Service URLs in Autodiscover responses, this is not true for Exchange Server 2010. As a result of this architectural change, information from the Availability Service and OOF Service is provided by the same EWS URL. For details about the Autodiscover service, see the following:
Understanding the Autodiscover Service in the Microsoft TechNet Library at http://go.microsoft.com/fwlink/?LinkId=217012 Autodiscover Service Architecture (POX) in the MSDN Library at http://go.microsoft.com/fwlink/?LinkId=217013 Autodiscover Service (SOAP in the MSDN Library at http://go.microsoft.com/fwlink/?LinkId=217015 Managing the Autodiscover Service in the Microsoft TechNet Library at http://go.microsoft.com/fwlink/?LinkId=217016
13
Outlook Client During setup, each Client Access Server is assigned a ServiceBindingInfo attribute that is populated with an Autodiscover URL in the form of https://{ServerName}/autodiscover/autodiscover.xml. These Service Connection Points (SCPs) are used to locate Microsoft Exchange services whenever a new mail profile is created using Outlook. Leveraging the users credentials, Outlook will search Active Directory Domain Services (AD DS) for a list of Service Connection Points for servers running Microsoft Exchange within the same AD site or adjacent site. Upon successfully building a list of available SCPs, the Outlook client will contact the first entry on the list to obtain the various EWS URLs that have been configured for Microsoft Exchange services. In the event that an SCP cannot be found or otherwise contacted, Outlook will use DNS records to locate the Autodiscover website. The following information is a summary of the logic that Outlook will use to locate Microsoft Exchange services within a Microsoft Exchange environment.
Internal Network 1. Outlook will query for the Service Connection Point object, which is defined on each Client Access Server in AD DS. 2. If for some reason the SCP object cannot be retrieved, or if the SCP is unavailable, Outlook will extract the SMTP domain from the users Active Directory attributes. 3. Outlook will then use the users SMTP domain to construct DNS queries for the following URLs: https://<smtpdomain>/autodiscover/autodiscover.xml https://autodiscover.<smtpdomain>/autodiscover/autodiscover.xml Autodiscover SRV record
14
External Network 1. Outlook will query for the Service Connection Point object, which is defined on each Client Access Server in AD DS. 2. If for some reason the SCP object cannot be retrieved, or if the SCP is unavailable, Outlook will extract the SMTP domain from the users Active Directory attributes. 3. Outlook will then use the users SMTP domain to construct DNS queries for the following URLs: https://<smtpdomain>/autodiscover/autodiscover.xml https://autodiscover.<smtpdomain>/autodiscover/autodiscover.xml Autodiscover SRV record
15
UC Clients and Devices UC clients such as Lync and UC devices such as the Microsoft Lync 2010 Phone Edition for Aastra 6721ip or Microsoft Lync 2010 Phone Edition for Polycom CX600 also use Autodiscover to locate several Microsoft Exchange web service URLs. Unlike Outlook, which uses an SCP object to locate the Autodiscover URL, UC clients and devices will only use the DNS-based discovery method. The Autodiscover process is initiated one minute after the client successfully authenticates to a Lync Registrar server. To support Exchange 2007 and Exchange 2010 servers, UC devices will first try SOAP / WSSecurity based discovery, but will fall back to XML request/response handling if necessary. The following logic is used by UC clients and devices to locate Exchange Web Services within an Microsoft Exchange environment.
Internal and External Networks 1. UC client will attempt to read any existing Autodiscover data with a valid Time-to-Live (TTL), which may have been previously retrieved by Outlook. 2. UC client or device will extract the SMTP domain from the users presence document. 3. UC client or device will then use the users SMTP domain to construct DNS queries for the following URLs: https://<smtpdomain>/autodiscover/autodiscover.xml https://autodiscover.<smtpdomain>/autodiscover/autodiscover.xml http://autodiscover.<smtpdomain>/autodiscover/autodiscover.xml Autodiscover SRV record 4. UC client or device will send unauthenticated GET to above Autodiscover URLs to determine whether server is running Exchange Server 2007 (X-SOAP-Enabled) or Exchange Server 2010 (XWSSecurity-Enabled). 5. A new SOAP or XML request is sent to retrieve EWS information, which is then cached in the Registry with a default TTL value of 24 hours. 6. In the event of Autodiscover failure, retries will occur as follows: If Autodiscover fails, retry on a three-minute interval over a period of two hours. If Autodiscover fails after three successive attempts, use MAPI but continue to retry. If Autodiscovery succeeds, refresh cached values on an hourly basis.
16
Processing the Autodiscover Response

When the Autodiscover response is received, several fields are used from the response to populate the EWS URLs which will be used by the UC client or device. The following is a sample of an XML response, with only the most relevent information shown. The EXCH protocol type represents the internal Microsoft Exchange configuration settings, which are typically retrieved by Outlook using SCP or by other clients using DNS records. The EXPR protocol type represents the external Microsoft Exchange configuration settings, which are typically retreived by Outlook or other clients using Autodiscover DNS records.
<?xml version="1.0" encoding="utf-8"?> <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a"> <User> <DisplayName>Mickey Monaghan</DisplayName> Shown only when DNS is used to <AutoDiscoverSMTPAddress>mickey@litwareinc.com</AutoDiscoverSMTPAddress> locate Autodiscover URL / not SCP </User> <Account> <Protocol> <Type>EXCH</Type> Used by internal clients <Server>NAE10ALL.contoso.com</Server> CAS server/ServiceConnectionPoint <ServerVersion>738180A0</ServerVersion> Exchange Server version <AD>NADC.contoso.com</AD> <ASUrl>https://NAE10All.contoso.com/EWS/Exchange.asmx</ASUrl> Availability Service URL <EwsUrl>https://NAE10All.contoso.com/EWS/Exchange.asmx</EwsUrl> Exchange Web Service URL <EcpUrl>https://NAE10All.contoso.com/ecp/</EcpUrl> Exchange Control Panel URL <OOFUrl>https://NAE10All.contoso.com/EWS/Exchange.asmx</OOFUrl> Out of Office Assistant URL <UMUrl>https://NAE10All.contoso.com/EWS/UM2007Legacy.asmx</UMUrl> UM Web Service URL (deprecated) </Protocol> <Protocol> <Type>EXPR</Type> Used by external clients <Server>mail.litwareinc.com</Server> DNS A record for Reverse Proxy <SSL>On</SSL> <AuthPackage>Ntlm</AuthPackage> <ASUrl>https://mail.litwareinc.com/EWS/Exchange.asmx</ASUrl> Availability Service URL <EwsUrl>https://mail.litwareinc.com/EWS/Exchange.asmx</EwsUrl> Exchange Web Service URL <EcpUrl>https://mail.litwareinc.com/ecp/</EcpUrl> Exchange Control Panel URL <OOFUrl>https://mail.litwareinc.com/EWS/Exchange.asmx</OOFUrl> Out of Office Assistant URL <UMUrl>https://mail.litwareinc.com/EWS/UM2007Legacy.asmx</UMUrl> UM Web Service URL (deprecated) </Protocol> </Account> </Response> </Autodiscover>
The Outlook client will always try to use a Service Connection Point entry from AD DS to locate the Autodiscover URL. In the event that a SCP entry cannot be found, Outlook will try to locate the Autodiscover URL by using DNS A and SRV records. If DNS is used to locate the Autodiscover URL, the tag <AutoDiscoverSMTPAddress/> will appear in the XML output, as shown above. UC clients and devices will only use DNS records to locate the Autodiscover URL.
17
Caching Exchange URLs in Registry

Upon processing the Autodiscover XML response containing information about Exchange Web Services, the Lync client will store it in the Windows registry. The EWS URLs used by Lync will be stored in HKCU\Software\Microsoft\Communicator\[User SMTP Address]\Autodiscovery, as shown in the screenshot below.
The EWS information stored in the registry by the Lync client has a default TTL value of 24 hours. It is refreshed on a hourly basis, and a TimeStamp value containing the time/date of the most recent successful update is also stored in the same registry location.
18
Retrieving Data from Microsoft Exchange Mailbox

When a user signs in for the very first time on a given computer, a UC client will query EWS to get information about several folders and search folders within the users mailbox. Information about the Contacts folder, the Inbox folder, the VoiceMail search folder, the DeletedItems folder, and the Calendar folder is requested from the UC client or device in the GetFolders request.
<messages:GetFolder xsi:type="messages:GetFolderType"> <messages:FolderShape> <types:BaseShape>AllProperties</types:BaseShape> <types:AdditionalProperties> <types:ExtendedFieldURI PropertyType="Binary" PropertyTag="0xFFF"/> <types:ExtendedFieldURI PropertyType="Binary" PropertyTag="0x36DA"/> <types:ExtendedFieldURI PropertyType="Binary" PropertyTag="0x35E9"/> <types:ExtendedFieldURI PropertyType="SystemTime" PropertyTag="0x670A"/> <types:ExtendedFieldURI PropertyType="Integer" PropertyTag="0x670B"/> </types:AdditionalProperties> </messages:FolderShape> <messages:FolderIds> <types:DistinguishedFolderId xsi:type="types:DistinguishedFolderIdType" Id="contacts"></types:DistinguishedFolderId> <types:DistinguishedFolderId xsi:type="types:DistinguishedFolderIdType" Id="inbox"></types:DistinguishedFolderId> <types:DistinguishedFolderId xsi:type="types:DistinguishedFolderIdType" Id="voicemail"></types:DistinguishedFolderId> <types:DistinguishedFolderId xsi:type="types:DistinguishedFolderIdType" Id="deleteditems"></types:DistinguishedFolderId> <types:DistinguishedFolderId xsi:type="types:DistinguishedFolderIdType" Id="calendar"></types:DistinguishedFolderId> </messages:FolderIds> </messages:GetFolder>
A response from Microsoft Exchange will include information such as the FolderID, the FolderClass, TotalCount of items, and ManagedFolderInformation (MAPI canonical permissions) of the folder.
Inbox Folder
<m:ResponseMessages> <m:GetFolderResponseMessage ResponseClass="Success"> <m:ResponseCode>NoError</m:ResponseCode> </m:ResponseMessages> <m:Folders> <t:Folder> <t:FolderId Id="AQMkAGU0NzVmZTVhLWU4MTUtNDM1MC1iOWRmLWQ3ZDM2" ChangeKey="AQAAABYAAAAg6jcZ"/> <t:ParentFolderId Id="AQMkAGU0NzVmZTVhLWU4MTUtNDM1MC1iOWRmLWQ" ChangeKey="AQAAAA=="/> <t:FolderClass>IPF.Note</t:FolderClass> <t:DisplayName>Inbox</t:DisplayName> <t:TotalCount>239</t:TotalCount> <t:ManagedFolderInformation><t:CanDelete>true</t:CanDelete> <t:IsManagedFoldersRoot>false</t:IsManagedFoldersRoot> <t:ManagedFolderId>065171c7-7492-4870-b9df-fcd6706cac8c</t:ManagedFolderId> </t:Folder> </m:Folders>
Upon completing the GetFolders task, the UC client or device will then launch SyncFolderItems to index all of the items within each folder. This is soon followed by a series of GetItem requests, which will retrieve information from several MAPI attributes for each item in that folder. This information is then cached in memory/local storage and updated whenever a change is detected in the folder status.
19
Note: The intial mass retrieval of data from the mailbox is only performed during the very first logon to the pool from the particular UC client or device. During subsequent logons, cached data will be retrieved from local storage, and only delta information will be requested from the Microsoft Exchange mailbox.
Reverse Proxy Pre-Authentication

Microsoft Forefront Threat Management Gateway is a web gateway that helps enables safe employee web use through comprehensive protection against malware, malicious websites, and vulnerabilities. Building on its predecessor, Microsoft Internet Security and Acceleration (ISA) Server 2006, Forefront Threat Management Gateway provides new URL filtering, anti-malware, and intrusion-prevention technologies to protect businesses against the latest web-based threats. These technologies are integrated with core network protection features such as firewall and virtual private network (VPN) to create a unified, easy-to-manage gateway. When deployed in a peremiter network, Forefront Threat Management Gateway can be configured to provide an extra measure of security for Microsoft Exchange resources by pre-authenticating client requests. Although this feature is widely used by many organizations using Microsoft Exchange, preauthenticating requests from UC clients and devices will often result in failures that can significantly impact feature availability. Requests involving the following web services may fail when pre-authentication is enabled for external UC clients and devices: Exchange Autodiscover service Exchange Web Services Lync WebTicket service Lync Certificate Provisioning Web service Lync Server Address Book Download Web service Lync Server Address Book Web Query service Lync Device Update Web service
20
MAPI/EWS Error Handling

The Outlook and Microsoft Exchange integration messages and notifications that a UC client or device will display depends on the connectivity status of EWS and MAPI. When an error occurs involving either EWS or MAPI connectivity to a Microsoft Exchange mailbox, it is categorized as either a transient or critical error. While transient failures are those for which the UC client or device attempts to reconnect to the server running Microsoft Exchange, permanent failures are those for which no attempts are made to reestablish the connection.
Connection Type MAPI EWS Transient Failures Sign-in failure Process terminated Everything else Permanent Failures Everything else EWS Autodiscovery issues Credential-related issues
The following summary describes the retry logic that the UC client or device will use in response to an error condition representing EWS or MAPI connectivity failure.
Error Condition MapiFolderCriticalError EwsFolderCriticalError EwsFolderTransientError Error Description Non-recoverable MAPI error (Win32 system call failure or otherwise occurred) Non-recoverable EWS error occurred Recoverable transient error (change of networks or momentary network outage) Non-recoverable condition where EWS is not configured in the environment, or one of the following conditions exist: 1) EwsNotConfigured 2) Cached EWS URLs are found, but hourly refresh fails 24 consecutive times If EWS response is successful, however, no EWS URLs are present in response Yes No No cached EWS URLs in the registry and there is a failure contacting EWS No Retry Connection No No Yes
3)
MapiFolderTransientError MapiNotInstalled
Recoverable transient error (change of networks or momentary network outage) Non-recoverable condition where MAPI/Outlook not installed
21
Feature Availability
The following information contains a summary of the available features which are offered by UC clients and devices, sorted by connection type. This information is critical for understanding the difference between expected versus unexpected feature behavior when dealing with Microsoft Exchange integration.
UC Client Features (by Connection Type)

Exchange Server 2007, Exchange Server, 2010 Lync Server (No EWS) Exchange Server 2007, Exchange Server 2010, Lync Server (MAPI + EWS) Exchange Server 2007, Exchange Server 2010, Lync Server (No MAPI)
Lync / Attendant Feature
Exchange Server 2003 Lync Server (No EWS)
Voice Mail Notification Read/Unread Missed Conversations Notification Read/Unread Voice Mail display in Lync Recent Conversations in Conversation Environment Exchange Contacts Integration (Merge/Search) Write Conversation History to Exchange Create Contacts in Exchange (write) Free/Busy Calendar Information Working Hours Out of Office Manager Exchange Delegates
MAPI (Pushed)
N/A N/A MAPI (Pushed) MAPI (On Demand)
EWS (Subscription)
EWS (On Demand) N/A MAPI (Polled) N/A MAPI (Polled) MAPI (Pushed) N/A EWS (Polled)
22
UC Device Features (by Connection Type)

Exchange Server 2007, Exchange Server 2010 Lync Server Features (No EWS) MWI Call Voicemail View Contacts MWI Call Voicemail View Contacts MWI Call Voicemail View Contacts Exchange Server 2007, Exchange Server 2010 Lync Server Features (EWS) MWI, Call Voice mail, Calendar View Contacts, Call Logs Unified Contact Store MWI, Call Voice mail, Calendar View Contacts, Call Logs Unified Contact Store MWI, Call Voice mail, Calendar View Contacts, Call Logs Unified Contact Store
Device
Context Signed in through computer (USB) Signed in through device (Username/Password) Signed in through computer (USB) (Username/Password)
Polycom CX700 IP desk phone
Aastra 6725ip, Polycom CX600, Polycom CX3000 Aastra 6721ip, Aastra 6725ip, Polycom CX500, Polycom CX600, Polycom CX3000
Signed in through PIN (PIN/Certfiicate)
Feature Impact
The following information contains a summary of the UC client and device features which are impacted by Microsoft Exchange connectivity issues. This information is critical for understanding how Microsoft Exchange connectivity failures can directly affect the availability of features offered by UC clients and devices.
UC Client Features (Connectivity Failures)

Scenario MAPI Available EWS Available Configuration Information MAPI status OK EWS status OK MAPI unavailable, retrying connection MAPI Unavilable EWS Available MAPI unavailable EWS status OK None No features impacted Error Message in UI None Feature Impact No features impacted
MAPI unavailable, retrying connection MAPI Unavailable EWS Not Deployed MAPI unavailable EWS Not Deployed
Lync is experiencing connection issues with Exchange. Lync will attempt to repair the connection. All features impacted Lync cannot connect to the Exchange server. Please try signing out and signing back in.
23
Scenario
Configuration Information
Error Message in UI Lync is experiencing connection issues with Exchange. Lync will attempt to repair the connection. Lync cannot connect to the Exchange server. Please try signing out and signing back in. Lync is experiencing connection issues with Exchange. Lync will attempt to repair the connection. Lync cannot connect to the Exchange server. To restore this connection, please try signing out and signing back in. Lync cannot connect to the Exchange server. Lync will attempt to retry the connection. Lync cannot connect to the Exchange server. Lync will attempt to retry the connection.
Feature Impact
MAPI status OK MAPI Available EWS Unavailable EWS Unavailable, retrying connection EWS unavailable
Voice Mail, Contacts (write), Working Hours, and Conversation History (read) impacted
MAPI not installed MAPI Not Installed EWS Unavailable EWS unavailable
All features impacted
MAPI unavailable MAPI Unavailable EWS Unavailable EWS unavailable
UC Device Features (Connectivity Failures)

Device Polycom CX700 IP desk phone Context Signed in through computer (USB), or Signed in through device (Username/Password) Aastra 6725ip, Polycom CX600, Polycom CX3000 Signed in through computer (USB) (Username/Password) Signed in through computer (USB) Signed in through device (Username/Password) Aastra 6725ip, Polycom CX600, Polycom CX3000 (Username/Password) Aastra 6721ip, Aastra 6725ip, Polycom CX500, Polycom CX600, Polycom CX3000 Signed in through computer (USB) (Username/Password) Signed in through PIN (PIN/Certfiicate) Please sign in to restore the connection to Microsoft Exchange. (Permanent) Unable to connect to Microsoft Exchange. Please contact your support team. Calendar Call Logs Unified Contact Store Calendar Call Logs Unified Contact Store Unable to connect to Microsoft Exchange. Retrying (Transient) Please sign in to restore the connection to Microsoft Exchange. (Permanent) Calendar Call Logs Unified Contact Store Calendar Call Logs Unified Contact Store Notification Message Unable to connect to Microsoft Exchange. Retrying (Transient) Features Impacted Calendar Call Logs Unified Contact Store
Polycom CX700 IP desk phone
24
UC Device Features (Authentication Failures)

Device Polycom CX700 (Username/Password) Context Expired Password Invalid EWS Credentials Notifcation Message Connectivity to Exchange is currently unavailable due to invalid credentials. To restore access to Call Logs, Voice Mail and Calendar information, select Re-signin. Connectivity to Exchange is currently unavailable due to invalid credentials. To restore access to Call Logs, Voice Mail and Calendar information, select Re-signin. Ensure you are connected to a PC running Microsoft Lync. Connectivity to Exchange is currently unavailable. To initiate access to Call Logs, Voice Mail and Calendar information, select Re-signin. Ensure you are connected to a PC running Microsoft Lync. Features Impacted
Aastra 6725ip, Polycom CX600, Polycom CX3000 (Username/Password) Aastra 6721ip, Aastra 6725ip, Polycom CX500, Polycom CX600, Polycom CX3000 (PIN/Certfiicate)
Expired Password Invalid EWS Credentials
Ethernet Only Ethernet + USB
25
UC Device Authentication
The Polycom CX700 IP desk phone provides an on-screen keyboard that can be used to enter domain credentials for Kerberos or NTLM authentication, and it also can be connected to a workstation running the Lync client using a USB cable (tethered). Upon connecting the device to the workstation, the Enterprise Voice-enabled user will be prompted to enter his/her domain credentials in the Lync client rather than on the phone itself. This authentication mechanism is called Strong User Authentication (SUA). The Aastra 6721ip common area phone, the Aastra 6725ip desk phone, the Polycom CX500 common area phone, the Polycom CX600 IP desk phone, and the Polycom CX3000 IP conference phone do not provide an on-screen keyboard for entering domain credentials. As such, these devices only support the certificate-based authentication model available in Microsoft Lync Server 2010. The Aastra 6725ip desk phone, the Polycom CX600 IP desk phone, and the Polycom CX3000 IP conference phone provide a USB interface for connecting the device to a workstation running the Lync client. These devices can authenticate to a Lync Registrar server using either of the following two methods: 1. By entering a phone number and personal identification number (PIN) of an Enterprise Voiceenabled user on the phone (PIN Authentication), or 2. By connecting the phone to a workstation by using a USB cable and entering the domain credentials of an Enterprise Voice-enabled user in the Lync client (Strong User Authentication). The Aastra 6721ip common area phone and the Polycom CX500 common area phone do not provide a USB interface, as these phones are designed to be deployed in public areas. Since these devices cannot be connected to a workstation running the Lync client using a USB cable, PIN Authentication is the only method available for authenticating to a Lync Registrar server. Strong User Authentication (SUA) When Strong User Authentication (SUA) is used to complete authentication on a Polycom CX700 IP desk phone, an Aastra 6275ip desk phone, a Polycom CX600 desk phone, or a Polycom CX3000 conference phone, the Lync client running on the connected workstation is used to submit the domain credentials of the Enterprise Voice-enabled user to the Certificate Provisioning Web service. Upon successfully resolving the users information, an OCS-signed certificate is issued for the endpoint and returned to the device. The OCS-signed certificate is used to authenticate to the Lync Registrar server and Lync Web Services. A user certificate is also issued for the endpoint and returned to the device. This certificate can be used to access other web services, such as Exchange Web Services.
26
PIN Authentication Supported IP phones using only PIN Authentication (with or without USB tethering) cannot authenticate to Exchange Web Services, and as such will always display an Exchange Integration Error. The Calendar, Call Logs, and unified contact store features will also be unavailable on these devices. This is by design.
27
Troubleshooting Exchange Integration

The following troubleshooting suggestions can help to isolate and resolve Microsoft Exchange connectivity problems that may impact your UC environment.
Lync Configuration Information

Lync 2010 has a built-in reporting mechanism which can be used to generate a summary of connectivity information for a given session. The Configuration Information option can be located by holding down CTRL and right-clicking the Lync icon located in the System Tray.
Please note that certain fields displayed in the Configuration Information report may be inaccurate; however, the fields highlighted in yellow in the following screenshot can be safely used to troubleshoot problems with Microsoft Exchange integration. If the Lync client is communicating directly with a Lync Registrar server, the Inside User Status setting will report TRUE. Otherwise, if the Lync client is routing traffic through a server running the Lync Server Access Edge service, the Inside User Status setting will report FALSE.
28
Outlook / Test E-mail AutoConfiguration

Outlook 2007 and Outlook 2010 also have a built-in reporting mechanism which can be used to generate a summary of Microsoft Exchange configuration information. The Test E-mail AutoConfiguration option can be located by holding down CTRL and right-clicking the Outlook icon in the System Tray.
To gather configuration information about Exchange Web Services, enter your email address, enter your password, select the Autodiscover option, then click Test. The output from this report can be collected by copying all of the information from the XML tab and pasting it into a Windows Notepad file.
29
Checking the Registry for Cached EWS Data

Another key resource for troubleshooting Microsoft Exchange integration issues is the Windows registry. Upon successfully querying the Autodiscover site for EWS information, the Lync client will cache it in the registry of the local workstation or UC device. The Exchange Web Services URLs will be stored in HKCU\Software\Microsoft\Communicator\[User SMTP Address]\Autodiscovery, as shown in the screenshot below.
30
The EWS information stored in the registry by the Lync client has a default TTL value of 24 hours and is refreshed on a hourly basis. A TimeStamp value is also used to record the time/date of the most recent successful update of EWS information, and it can be found in the same registry location. If the HKCU\Software\Microsoft\Communicator\[User SMTP Address]\Autodiscovery registry key does not exist on the users workstation, then it likely means that one of the following failures have occurred: Lync was unable to locate a valid DNS A record or SRV record for the Autodiscover site Lync successfully resolved one of the hard-coded Autodiscover DNS values but was unable to contact the site (for instance, because of an invalid IP address or invalid reverse proxy publishing rule) Certificate assigned to Autodiscover site is not trusted by the Lync workstation
Even if you do find an Autodiscovery entry in the registry, it can be somewhat challenging to determine whether it contains current/valid information. However, if you convert the TimeStamp from the Autodiscovery registry key to a recognizable value, you can conclude that the EWS information is valid if the TimeStamp value is less than 24 hours old (the default TTL setting).
How to Convert the AutoDiscovery TimeStamp The following information can be used to assist you in converting the Autodiscovery TimeStamp to a recognizable value. If the converted time/date value is less than 24 hours old, then it is safe to assume that the cached EWS information from the registry is current/valid. 1. Download and extract the freeware DCode Date conversion utility from the following site: http://www.digital-detective.co.uk/downloads.asp 31
2. Open the Registry, and note the TimeStamp value from the following registry location: HKCU\Software\Microsoft\Communicator\[User SMTP Address]\Autodiscovery 3. Using Little Endian, reorder the bytes from the TimeStamp registry value as shown:
4.
Open the DCode Date conversion utility, then select the Decode Format option. Windows: FileTime [xxxxxxxx: xxxxxxxx]
5. In the Value to Decode entry, paste the reordered 16-character TimeStamp value from the Autodiscovery registry key. Be sure to remove all spaces. 6. Click Decode to convert the TimeStamp to a readable time/date value.
Exporting EWS Configuration Information

If you find that the Lync client is unable to contact the Autodiscover site to retrieve EWS configuration data, you may need to export it directly from the Microsoft Exchange environment. The following information can be obtained using the Microsoft Exchange Management Shell. Note: You may need Microsoft Exchange Organizational rights to run these Windows PowerShell cmdlets.
32
Get Autodiscover Service Connection Points (SCPs) When a Client Access Server is installed, it is automatically configured as a Service Connection Point for the Autodiscover service. The AutoDiscoverServiceInternalUri value will be used by internal Outlook clients to query for Exchange Web Services information. By default, Outlook will attempt to locate a Client Access Server from the same Active Directory site as the users Mailbox server for Autodiscover services . If for some reason the Outlook client initially contacts a Client Access Server from a different Active Directory site, the client will be referred to a Client Access Server from the same Active Directory site as the users Mailbox server.
Cmdlet: Get-ClientAccessServer | FL fqdn,*autodiscover* > AutodiscoverSCPs.log
Fqdn AutoDiscoverServiceCN AutoDiscoverServiceClassName AutoDiscoverServiceInternalUri AutoDiscoverServiceGuid AutoDiscoverSiteScope Fqdn AutoDiscoverServiceCN AutoDiscoverServiceClassName AutoDiscoverServiceInternalUri AutoDiscoverServiceGuid AutoDiscoverSiteScope : : : : : : : : : : : : NAE7ALL.contoso.com NAE7ALL ms-Exchange-AutoDiscover-Service https://NAE7ALL.contoso.com/Autodiscover/Autodiscover.xml 77378f46-2c66-4aa9-a6a6-3e7a48b19596 {Default-First-Site-Name} NAE10ALL.contoso.com NAE10ALL ms-Exchange-AutoDiscover-Service https://NAE10ALL.contoso.com/Autodiscover/Autodiscover.xml 77378f46-2c66-4aa9-a6a6-3e7a48b19596 {Default-First-Site-Name}
Get Exchange Web Services Configuration The Exchange Web Services URLs that are returned to a requesting client by the Autodiscover service are managed by using the WebServicesVirtualDirectory cmdlet. The EWS URLs are then used by a given client to perform various functions against a Microsoft Exchange mailbox (such as GetFolders, SyncFolderItems, UpdateDelegate, SetUserOOFSettings, and PlayOnPhone).
Cmdlet: Get-WebServicesVirtualDirectory | fl name,server,*url*,*auth*,*version* > EWSSettings.log
Name Server InternalNLBBypassUrl InternalUrl ExternalUrl CertificateAuthentication InternalAuthenticationMethods ExternalAuthenticationMethods LiveIdSpNegoAuthentication WSSecurityAuthentication LiveIdBasicAuthentication BasicAuthentication DigestAuthentication WindowsAuthentication ExchangeVersion : : : : : : : : : : : : : : : EWS (Default Web Site) NAE10ALL https://mail.litwareinc.com/EWS/Exchange.asmx https://mail.litwareinc.com/EWS/Exchange.asmx {Ntlm, WindowsIntegrated, WSSecurity} {Ntlm, WindowsIntegrated, WSSecurity} False True False False False True 0.10 (14.0.100.0)
33
Name Server InternalNLBBypassUrl InternalUrl ExternalUrl CertificateAuthentication InternalAuthenticationMethods ExternalAuthenticationMethods LiveIdSpNegoAuthentication WSSecurityAuthentication LiveIdBasicAuthentication BasicAuthentication DigestAuthentication WindowsAuthentication ExchangeVersion
: : : : : : : : : : : : : : :
EWS (Default Web Site) NAE7ALL https://mail.litwareinc.com/EWS/Exchange.asmx https://mail.litwareinc.com/EWS/Exchange.asmx {Ntlm, WindowsIntegrated} {Ntlm, WindowsIntegrated} False False False False False True 0.1 (8.0.535.0)
Get Exchange Certificate (from each Client Access Server) When dealing with Microsoft Exchange integration failures, it is sometimes necessary to examine the certificate configuration for each Client Access Server in an Exchange environment. Many customers elect to use a wildcard UC certificate for Microsoft Exchange services. While in some cases ths may be considered a supported configuration for Microsoft Exchange, Lync clients and devices will honor only wildcard UC certificates if the wildcard value (for example, *.contoso.com) appears as a subject alternative name entry and not as the subject name of the certificate. The Get-ExchangeCertificate cmdlet can be used to retrieve information for certificates assigned to the IIS service of a server running Microsoft Exchange (either the local machine or from a remote server by using the Server parameter).
Cmdlet (Local Server): Cmdlet (Remote Server): Get-ExchangeCertificate | FL > {CASServer}Certs.log Get-ExchangeCertificate Server {CASServer} | FL > {CASServer}Certs.log
CertificateDomains : {mail.litwareinc.com, autodiscover.litwareinc.com, NAE10All.contoso.com, NAE10All} HasPrivateKey : True IsSelfSigned : False Issuer : CN=contoso-NADC-CA, DC=contoso, DC=com NotAfter : 7/27/2012 4:16:42 PM NotBefore : 7/28/2010 4:16:42 PM PublicKeySize : 2048 RootCAType : Enterprise SerialNumber : 44FB41E5000000000048 Services : UM Status : Valid Subject : CN=mail.litwareinc.com, O=Contoso Corporation, C=US Thumbprint : B6A6D1681DEB98782169D140B6CFD1A61B44A28F CertificateDomains HasPrivateKey IsSelfSigned Issuer NotAfter NotBefore PublicKeySize RootCAType SerialNumber : : : : : : : : : {mail.litwareinc.com, autodiscover.litwareinc.com} True False CN=DigiCert High Assurance CA-3, OU=www.digicert.com, O=DigiCert Inc, C=US 10/20/2012 7:59:59 PM 10/16/2009 8:00:00 PM 2048 ThirdParty 0568AE245E1649E490D8D568FA0B9346
34
Services Status Subject Thumbprint CertificateDomains HasPrivateKey IsSelfSigned Issuer NotAfter NotBefore PublicKeySize RootCAType SerialNumber Services Status Subject Thumbprint
: IMAP, POP, IIS, SMTP : Valid : CN=mail.litwareinc.com, O=Mickey Monaghan, L=Rock Hill, S=South Carolina, C=US : A66AC1A23EBFE33886DA9348AE77E9FB60DE931A : : : : : : : : : : : : : {NAE10All, NAE10All.contoso.com} True True CN=NAE10All 12/13/2014 8:14:15 AM 12/13/2009 8:14:15 AM 2048 None 44860CF3AF2C048A4BCC8400F3A3F267 SMTP Valid CN=NAE10All 506F1871DFA2395D0542F0BC592A26A3E9358087
Using Microsoft Exchange Synthetic Transactions

The Exchange Server 2010 Management Shell offers various synthetic transactions which can be used to test Microsoft Exchange features or configuration settings. These test cmdlets can be especially helpful when troubleshooting Microsoft Exchange integration issues. Synthetic transactions in Microsoft Exchange run under the security context of a special test account which must be created by using the Windows PowerShell script New-TestCasConnectivityUser.ps1 for Microsoft Exchange. This script can be found in the \Program Files\Microsoft\Exchange Server\V14\Scripts folder of an Exchange Server 2010 installation. Note: You may need Microsoft Exchange Organizational rights to run these cmdlets.
How to Create a Client Access Server Test Account The following steps can be used to create a new test account that will be used by Microsoft Exchange synthetic transactions. This account will be provisioned with a Microsoft Exchange mailbox on the specified server running Microsoft Exchange. 1. Launch the Exchange Server 2010 Management Shell using an account with appropriate rights 2. Navigate to \Program Files\Microsoft\Exchange Server\V14\Scripts 3. Create a new ExTest account using the following command: Get-MailboxServer {MbxServer} | .\new-TestCasConnectivityUser.PS1
Get-MailboxServer NAE10All | .\new-TestCasConnectivityUser.PS1
35
Creating a new session for implicit remoting of "Get-MailboxServer" command... Please enter a temporary secure password for creating test users. For security purposes, the password will be changed regularly and automatically by the system. Enter password: ******** Create test user on: NAE10ALL.contoso.com UserPrincipalName: extest_83bc61a4ed5f4@contoso.com The command completed successfully.
How to Test EWS Connectivity The following Windows PowerShell cmdlet can be used to test connectivity to Exchange Web Services.
Cmdlet: Test-WebServicesConnectivity
CasServer --------NAE10All NAE10All NAE10All NAE10All NAE10All NAE10All
LocalSite --------Default-Fi... Default-Fi... Default-Fi... Default-Fi... Default-Fi... Default-Fi...
Scenario -------GetFolder SyncFolderItems CreateItem SyncFolderItems DeleteItem SyncFolderItems
Result Latency(MS) Error ------ ----------- ----Success 25812.50 Success 1265.64 Success 3500.04 Success 1125.01 Success 4687.51 Success 3500.04
How to Test EWS Connectivity using Autodiscover The following Windows PowerShell cmdlet can be used to test Exchange Web Services connectivity by querying the Autodiscover service for EWS information.
Cmdlet: Test-WebServicesConnectivity -UseAutodiscoverForClientAccessServer
CasServer --------NAE10ALL NAE10ALL NAE10ALL NAE10ALL NAE10ALL NAE10ALL NAE10ALL
LocalSite --------Default-Fi... Default-Fi... Default-Fi... Default-Fi... Default-Fi... Default-Fi...
Scenario -------Autodiscover... GetFolder SyncFolderItems CreateItem SyncFolderItems DeleteItem SyncFolderItems
Result Latency(MS) Error ------ ----------- ----Success 9015.60 Success 453.12 Success 406.24 Success 187.50 Success 437.49 Success 187.50 Success 187.50
36
How to Test MAPI Connectivity The following Windows PowerShell cmdlet can be used to test MAPI connectivity to Microsoft Exchange.
Cmdlet: Test-MAPIConnectivity
MailboxServer ------------NAE10ALL
Database Result ------------Mailbox Databas... Success
Error -----
How to Test Outlook Connectivity to EWS The following Windows PowerShell cmdlet can be used to test Exchange Web Services connectivity by simulating requests which are generated by an Outlook client.
Cmdlet: Test-OutlookWebServices {UserEmailAddress}
Id Message : 1019 : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is https://NAE10All.contoso.com/Autodiscover/Autodiscover.xml. : 1006 : Contacted the Autodiscover service at https://NAE10All.contoso.com/Autodiscover/Autodiscover.xml. : 1016 : [EXCH] The AS is configured for this user in the AutoDiscover response received from https://NAE10All.contoso.com/Autodiscover/Autodiscover.xml. : 1015 : [EXCH] The OAB is configured for this user in the AutoDiscover response received from https://NAE10All.contoso.com/Autodiscover/Autodiscover.xml. : 1014 : [EXCH] The UM is configured for this user in the AutoDiscover response received from https://NAE10All.contoso.com/Autodiscover.xml. : 1016 : [EXPR] The AS is configured for this user in the AutoDiscover response received from https://mail.litwareinc.com/Autodiscover/Autodiscover.xml. : 1015 : [EXPR] The OAB is configured for this user in the AutoDiscover response received from https://mail.litwareinc.com/Autodiscover/Autodiscover.xml. : 1014 : [EXPR] The UM is configured for this user in the AutoDiscover response received from https://mail.litwareinc.com/Autodiscover/Autodiscover.xml. : 1022 : Autodiscover was tested successfully.
Id Message
Id Message
Id Message
Id Message
Id Message
Id Message
Id Message
Id Message
37
Id Message
: 1106 : Contacted the Autodiscover service at https://NAE10ALL.contoso.com:443/Autodiscover/Autodiscover.xml. : 1116 : [EXCH] The AS is configured for this user in the AutoDiscover response received from https://NAE10ALL.contoso.com:443/Autodiscover/Autodiscover.xml. : 1115 : [EXCH] The OAB is configured for this user in the AutoDiscover response received from https://NAE10ALL.contoso.com:443/Autodiscover/Autodiscover.xml. : 1114 : [EXCH] The UM is configured for this user in the AutoDiscover response received from https://NAE10ALL.contoso.com:443/Autodiscover/Autodiscover.xml.
Id Message
Id Message
Id Message
Id Message
: 1116 : [EXPR] The AS is configured for this user in the AutoDiscover response received from https://NAE10ALL.contoso.com:443/Autodiscover/Autodiscover.xml. : 1115 : [EXPR] The OAB is configured for this user in the AutoDiscover response received from https://NAE10ALL.contoso.com:443/Autodiscover/Autodiscover.xml. : 1114 : [EXPR] The UM is configured for this user in the AutoDiscover response received from https://NAE10ALL.contoso.com:443/Autodiscover/Autodiscover.xml. : 1122 : Autodiscover was tested successfully. : 1024 : [EXCH] Successfully contacted the AS service at https://mail.litwareinc.com/EWS/Exchange.asmx. The elapsed time was 46 milliseconds. : 1026 : [EXCH] Successfully contacted the UM service at https://mail.litwareinc.com/EWS/Exchange.asmx. The elapsed time was 624 milliseconds.
Id Message
Id Message
Id Message Id Message
Id Message
38
Analyzing the UC Device CELog File

If you encounter Microsoft Exchange integration errors on a supported IP phone, the CELog from the device contains a wealth of troubleshooting information. However, collecting and analyzing this data can be somewhat challenging. Logging options for supported IP phones can be managed either directly on the phone or from the Global or Site level Device Configuration policy. When logging is enabled manually on the phone, the setting will be reverted the moment the device is restarted. However, if logging is enabled by policy, the setting will persist if the device is rebooted. To collect CELog files from a given device, they must first be uploaded to the File Store of the associated Lync Pool. The following CELog excerpt is from a Polycom CX600 IP phone and has been converted and filtered to display only relevant Autodiscover events.
Aries:CLM startlitwareinc.coms component 'AutodiscoverService' Aries:Performing autodiscovery using DNS. Aries:CLM started component 'AutodiscoverService', reporting state STARTED Aries:Received email address change event to retry AutoDiscover. New address is mickey@litwareinc.com Aries:StartAutodiscoveryTask: Performing autodiscovery using DNS. Aries:GetPrimarySmtpAddress: primarySmtp=mickey@litwareinc.com, hr=0 Aries:Trying with email address, mickey@litwareinc.com Aries:DnsAutodiscoverTask::TryAutodiscoverUrls: Trying url, https://litwareinc.com/autodiscover/autodiscover.xml Aries:DnsAutodiscoverTask::HttpSendRequest failed. Server=litwareinc.com, Path=/autodiscover/autodiscover.xml Aries:DnsAutodiscoverTask::Failed to send request: hr=0x80f10045, url=https://litwareinc.com/autodiscover/autodiscover.xml Aries:DnsAutodiscoverTask::TryAutodiscoverUrls: GetHttpHeaders failed with 0x80f10045 Aries:DnsAutodiscoverTask::TryAutodiscoverUrls: Exception with this url. hr=0x80f10045 Aries:DnsAutodiscoverTask::TryAutodiscoverUrls: Trying https://autodiscover.litwareinc.com/autodiscover/autodiscover.xml Aries:GetHttpHeaders: 7/28/2010 at 15:00:55. SOAP request= GET /autodiscover/autodiscover.xml HTTP/1.1 User-Agent: CPE/4.0.7576.0 OCPhone/4.0.7576.0 (Microsoft Lync 2010 Phone Edition) Host: autodiscover.litwareinc.com Cache-Control: no-cache SOAP response= HTTP/1.1 401 Unauthorized Cache-Control: private Content-Type: text/html Server: Microsoft-IIS/7.0 X-SOAP-Enabled: True X-WSSecurity-Enabled: True X-WSSecurity-For: None X-AspNet-Version: 2.0.50727 WWW-Authenticate: Negotiate WWW-Authenticate: NTLM WWW-Authenticate: Basic realm="autodiscover.litwareinc.com" X-Powered-By: ASP.NET Date: Wed, 28 Jul 2010 19:00:56 GMT Content-Length: 58
39
Aries:MetaDataDescription successfully created. baseUrl=https://autodiscover.litwareinc.com/autodiscover/autodiscover.svc Aries:Static metadata validation for https://autodiscover.litwareinc.com/autodiscover/autodiscover.svc, binding count=1 BaseUrl:https://autodiscover.litwareinc.com/autodiscover/autodiscover.svc UpdateTime:2010-07-28T19:00:55Z # of bindings:1 ----------------------Endpoint address:https://autodiscover.litwareinc.com/autodiscover/autodiscover.svc OperationName:http://schemas.microsoft.com/exchange/2010/Autodiscover:GetUserSettingsRequestMessage SoapAction:http://schemas.microsoft.com/exchange/2010/Autodiscover/Autodiscover/GetUserSettings TokenProvServicePolicy: AuthTypeSupported:1 Aries:Credential user 3 created a web service, ServerUrl=https://autodiscover.litwareinc.com/autodiscover/autodiscover.xml Aries:GetMetaDataDescription called for baseUrl=https://autodiscover.litwareinc.com/autodiscover/autodiscover.svc, mode=1 Aries:DnsAutodiscoverTask::TryAutodiscoverUrls: Exception with this url. hr=0x80f10041 Aries:DnsAutodiscoverTask::TryAutodiscoverUrls: Autodiscover is cancelled. Aries:DnsAutodiscoverTask::PerformAutodiscovery: User cancelled credential dialog. No retry will happen until user signs-in. Aries:DnsAutodiscoverTask::PerformAutodiscovery: DNS autodiscover failed Aries:Autodiscovery failed. hr=0x80f10041.
How to Collect and Analyze CELog Data The following information can be used to assist you in collecting and analyzing trace data from a UC device such as a Polycom CX700, Aastra 6721ip, Aastra 6725ip, Polycom CX500, Polycom CX600, or Polycom CX3000 phone. 1. Start the Microsoft Lync Server 2010 Control Panel, and then navigate to Clients \ Device Configuration. 2. Select to open either the Site Policy (if exists) or the Global Policy. 3. Set the Logging level option to Medium, and then commit your changes.
40
4. After a few minutes, check the Logging option from the System menu of the device to verify that the policy has been enforced. 5. Once you have confirmed that Logging is enabled on the UC device, restart it by powering it off and then on again. 6. Attempt to sign in to the phone, then choose the the Send Logs option from the System menu 7. On the computer hosting the File Store for the associated Lync Pool, navigate to the {SiteWebService-1}\DeviceUpdateLogs\Client\CELog folder and locate the uploaded CLG file.
8. Obtain a copy of the ReadLog.exe tool, which is part of the Windows Embedded CE 6.0 Platform
Builder SP1 package available on Microsoft TechNet. To download Windows Embedded CE 6.0 Platform Builder Service Pack 1, go to the Microsoft Download Center at http://go.microsoft.com/fwlink/?LinkId=217019. 9. After installing Platform Builder, open a command prompt with elevated privileges and navigate to the \WINCE600\PUBLIC\COMMON\OAK\BIN\I386 folder. 10. Use to ReadLog.exe utility to convert the CLG file to text format by using the following command line: ReadLog.exe v UCPhone_CX600_system.clg1 ConvertedCLG1File.log 11. Use Windows Notepad to open the converted log file.
41
Collecting Microsoft Exchange Traces

Almost every component within the Microsoft Exchange product contains an extensive amount of tracing, which can be enabled for troubleshooting purposes. In some cases, it may be necessary to collect traces from Microsoft Exchange in an effort to isolate a problem. Once the trace files have been created, a Microsoft Support Professional can assist with converting the ETL trace file to a readable format and analyzed for possible failures with the EWS component. How to Collect EWS Tracing The following information contains instructions for collecting and analyzing tracing from Exchange Web Services. If there are multiple Client Access Servers involved (for example, load balanced array of Client Access Servers), these steps should be completed on each Client Access Server in the communication path. Additionally, Microsoft Exchange Organization rights may be required to complete this task. 1. Start the Microsoft Exchange Management Console. 2. From the Navigation pane on the left of the Microsoft Exchange Management Console window, click the Toolbox option.
3. From the center Work pane, double-click the Performance Troubleshooter option to open the Troubleshooting Assistant.
4. Within the Microsoft Exchange Troubleshooting Assistant, select the Select a Task option from the Navigation pane on the left.
42
5. Next, select the Trace Control option from the center Work pane of the Troubleshooting Assistant.
6. Configure the trace options as shown, then click Set Manual Trace Tags.
7. Configure the appropriate tags on the Set Trace Tags Manually page, and then click Start Tracing.
43
MSExchangeAutoDiscover Enable tracing for all Trace Tags of this component if you are troubleshooting Autodiscover connectivity problems. MSExchangeWebServices Enable tracing for all Trace Tags of this component if you are troubleshooting Exchange Web Services connectivity issues. MSExchangeUM Enable tracing for all Trace Tags of this component if you are troubleshooting Exchange Unified Messaging (UM) issues. InfoWorker.Common Enable tracing for the MWI trace tags of this component if you are troubleshooting Message Waiting Indicator issues. Certificate Authentication/Common (Certificate Authorization)/NetworkingLayer (Certificate) Enable trace tags for these components if you are troubleshooting certificate issues. MAPINet / MAPI Provider Enable tracing for all Trace Tags of these components if you are troubleshooting MAPI / XSO access to a given mailbox. NetworkingLayer Enable tracing for all Trace Tags of this component if you are troubleshooting any connectivity problems at the physical layer.
8. Reproduce the issue (for example, log on by using Lync or restart the UC phone).
44
9. After successfully reproducing the error, click Stop Tracing Now.
10. Contact Microsoft Technical Support for assistance with converting and analyzing the Exchange trace files.
45
Scenario: Integration Errors in Lync and on UC Phone (DNS)
NAE10ALL.contoso.com
In this scenario, the Outlook client successfully retrieves the Autodiscover URL from the ServiceConnectionPoint in AD DS. However, the Lync client and UC phone fail to locate Exchange Web Services because there are no DNS records for either of the two hard-coded Autodiscover URLs: https://autodiscover.litwareinc.com/ _autodiscover._tcp.litwareinc.com
46
Scenario: Integration Error on UC Phone (Certificates)
The Autodiscover/EWS certificate assigned to the server running Microsoft Exchange is issued by a third-party certification authority (CA). Although the computer running both the Lync and Outlook clients trusts the issuing CA, it is not trusted by the UC phone.
47
Scenario: Integration Error on UC Phone (Permissions)
In this scenario, the Autodiscover/EWS site is configured to use Basic, NTLM, and Windows Integrated Authentication. By default, Polycom CX700 IP desk phones use NTLM for authentication. If Basic Authentication is offered by the Exchange server, the Polycom CX700 IP desk phone will not be able to authenticate correctly to Exchange Web Services.
48
Scenario: Integration Errors in Lync and on UC Phone (Corruption)
In this scenario, both the Lync client and the UC phone contact Exchange Web Services successfully, however, the GetFolders function fails to enumerate the contents of the mailbox. After enabling Exchange Tracing, corruption errors are captured while querying for information from the Contacts folder. Removing the corrupt Contact object can resolve this issue.
49
Appendix A: Lync / MAPI Error Strings
MAPI Errors Line 1031 1033 Error Name IDS_STPOPUP_OUTLOOK_ISSUE IDS_STPOPUP_OUTLOOK_ISSUE_TOOLTIP Outlook integration error Outlook integration error MOC_PRODUCTGENERICNAME_STR " is not compatible with your existing version of Microsoft Office Outlook. Some Outlook integration features may not work as expected. Do you want to get instructions for downloading the correct version now?" There was a problem connecting to Microsoft Office Outlook. %1 Outlook is not installed correctly. Repair or reinstall Outlook, and then update the personal information manager setting on the Personal tab in the Options dialog box. Your Outlook profile is not configured correctly. Contact your system administrator with this information. The e-mail address used in your default Outlook profile is different from the sign-in address used in MOC_PRODUCTGENERICNAME_STR ". Change your default Outlook profile to match the sign-in address you are using in " MOC_PRODUCTGENERICNAME_STR ", and then sign out and sign back in to " MOC_PRODUCTGENERICNAME_STR "." A separate sign in was required to connect to Outlook, but the sign in dialog was canceled or closed, or your Exchange server may be unavailable. To establish the connection, sign out and then sign back in to MOC_PRODUCTGENERICNAME_STR "." Outlook is set to work offline. MOC_PRODUCTGENERICNAME_STR " will not receive missed call or voice mail information. To reconnect, change the Work Offline setting in Outlook." Outlook is not installed or configured correctly. Repair or reinstall Outlook, and then sign out and sign back in to MOC_PRODUCTGENERICNAME_STR "." Your Exchange server is temporarily unavailable. MOC_PRODUCTGENERICNAME_STR " will automatically continue trying to reconnect. If this problem continues, contact your system administrator." Your Exchange server is temporarily unavailable. To establish a connection, sign out and sign back in to MOC_PRODUCTGENERICNAME_STR " later. If this problem persists, contact your system administrator." MOC_PRODUCTGENERICNAME_STR " cannot retrieve contact information from Outlook. If this problem continues, contact your system administrator with this information." Cannot retrieve your Outlook calendar information. MOC_PRODUCTGENERICNAME_STR " will automatically continue to retry. If this problem persists, contact your system administrator." Error String
1504
IDS_INVALID_OUTLOOK_VERSION
1782 1784 1785
IDS_MAPI_INTEGRATION_FAILED_TEMPLATE IDS_MAPI_ERROR_INSTALLATION_MISCONFIGURED IDS_MAPI_ERROR_PROFILE_MISCONFIGURED
1786
IDS_MAPI_ERROR_EMAIL_ADDRESSES_DO_NOT_MA TCH
1787
IDS_MAPI_CREDENTIAL_DIALOG_CANCEL
1788
IDS_MAPI_STORE_OFFLINE
1789
IDS_MAPI_MISCONFIGURATION
1791
IDS_MAPI_ERROR_AUTH_FAILED_OR_SERVER_DOW N
1792
IDS_MAPI_ERROR_OUTLOOK_CONTACT_PROVIDER_ AUTH_FAILED_OR_SERVER_DOWN IDS_MAPI_ERROR_OUTLOOK_CONTACT_PROVIDER_ UNKNOWN_ERROR MOC_PRODUCTGENERICNAME_STR IDS_MAPI_ERROR_CALENDAR_UNKNOWN_ERROR
1793
1798
50
1799
IDS_MAPI_NOT_READY MOC_PRODUCTGENERICNAME_STR IDS_MAPI_ERROR_WAB_CONTACT_PROVIDER_UNK NOWN_ERROR MOC_PRODUCTGENERICNAME_STR
1800
1801
IDS_MAPI_SPOOLER_MALFUNCTIONING MOC_PRODUCTGENERICNAME_STR
1802 3472 3473
IDS_MAPI_SPOOLER_DISCARDED_OLD_FILES MOC_PRODUCTGENERICNAME_STR IDS_DETAILS_SCHED_MEETING_ERR_NO_OUTLOOK IDS_DETAILS_SCHED_MEETING_ERR_OUTLOOK_ITE M
is in the process of connecting to the Exchange server. This process may take a few minutes. Some features will not be available until the connection is complete. MOC_PRODUCTGENERICNAME_STR " cannot retrieve contact information from Windows Address Book. If this problem continues, contact your system administrator with this information." MOC_PRODUCTGENERICNAME_STR " cannot save conversations in your Outlook mailbox at this time. This problem may be temporary, and " MOC_PRODUCTGENERICNAME_STR " will continue to retry. If this problem persists and you are not experiencing other problems with your Outlook connection, contact your system administrator with this information." MOC_PRODUCTGENERICNAME_STR " could not save some conversations in your Outlook mailbox after trying for 30 days. These conversations will now be deleted permanently." Microsoft Office Outlook is not installed on this computer. Cannot connect to Microsoft Office Outlook to schedule a meeting because Outlook is not responding. Please close any open Outlook dialog boxes and try again. If the problem persists, contact your system administrator. Cannot connect to Microsoft Office Outlook to send email because Outlook is not responding. Please close any open Outlook dialog boxes and try again. If the problem persists, contact your system administrator. Cannot search for previous conversations in Outlook. Please close any open Outlook dialog boxes or try selecting fewer contacts. If the problem persists, contact your system administrator. Cannot connect to Microsoft Office Outlook to view contact properties because Outlook is not responding. Please close any open Outlook dialog boxes and try again. If the problem persists, contact your system administrator. Cannot connect to Microsoft Office Outlook to add a contact because Outlook is not responding. Please close any open Outlook dialog boxes and try again. If the problem persists, contact your system administrator. Cannot connect to Microsoft Office Outlook to open the desired folder. Please close any open Outlook dialog boxes and try again later. If the problem persists, contact your system administrator. Cannot perform this action because Microsoft Office Outlook is not running with the default profile. MOC_PRODUCTGENERICNAME_STR " will update and restart shortly; Outlook will automatically close and then attempt to restart. Please save relevant Outlook items now." An update will be installed and MOC_PRODUCTGENERICNAME_STR " will restart shortly; Outlook will automatically close and then attempt to restart. Please save relevant Outlook items now." The installation of Lync could not be completed. Please close Outlook and then try again to update. $(MOC_PRODUCTGENERICNAME_STR) cannot open Outlook. Copy and send the following dial-in instructions to people you want to invite to your conference.,IDC_STATIC,7,7,262,24,
3474
IDS_DETAILS_SEND_EMAIL_ERR_OUTLOOK_ITEM
3475
IDS_DETAILS_FIND_CONVERSATION_ERR_OUTLOOK_ ITEM
3476
IDS_DETAILS_CONTACT_PREPERTIES_ERR_OUTLOOK _ITEM
3477
IDS_DETAILS_ADD_CONTACT_ERR_OUTLOOK_ITEM
3482
IDS_MYPANE_ERR_OUTLOOK_LAUNCH
3483 3693
IDS_MYPANE_ERR_NON_DEFAULT_PROFILE_IN_USE IDS_AUTOUPDATE_CHECKED_DIALOG_TEXT
3699
IDS_AUTOUPDATE_COUNTDOWN_WARNING_TEXT
3708
IDS_AUTOUPDATE_INSTALLATION_FAILED
874
IDD_INVITEOUTSIDEUSER_DIALOG_EMAIL DIALOGEX
51
Appendix B: Lync / EWS Error Strings
EWS Errors Line 1034 1035 Error Name IDS_STPOPUP_EXCHANGE_ISSUE IDS_STPOPUP_EXCHANGE_ISSUE_TOOLTIP IDS_MAPI_ERROR_AUTODISCOVERY_PENDING MOC_PRODUCTGENERICNAME_STR Description Exchange Connection Error Exchange connection error MOC_PRODUCTGENERICNAME_STR " is in the process of trying to locate your Exchange Web Services. Your Outlook calendar information and Out of Office message may not be available and your calls may not be forwarded based on your working hours." MOC_PRODUCTGENERICNAME_STR " could not determine the location of your Exchange Web Services. Your Outlook calendar information and Out of Office message may not be available and your calls may not be forwarded based on your working hours." MOC_PRODUCTGENERICNAME_STR " will try to retrieve this information again later. If this problem persists, contact your system administrator." MOC_PRODUCTGENERICNAME_STR " could not determine the location of your Exchange Web Services. Your Outlook calendar information and Out of Office message may not be available and your calls may not be forwarded based on your working hours. Please try signing out and then back in to " MOC_PRODUCTGENERICNAME_STR "." MOC_PRODUCTGENERICNAME_STR " could not retrieve calendar or Out of Office information from Exchange Web Services. " MOC_PRODUCTGENERICNAME_STR " will automatically continue to retry. If this problem persists, contact your system administrator."
1794
1795
IDS_MAPI_ERROR_AUTODISCOVERY_FAILED_TEMPO RARILY MOC_PRODUCTGENERICNAME_STR
1796
IDS_MAPI_ERROR_AUTODISCOVERY_FAILED_PERMA NENTLY MOC_PRODUCTGENERICNAME_STR
1797
IDS_MAPI_ERROR_WEB_SERVICE_AUTH_FAILED_OR _SERVER_DOWN MOC_PRODUCTGENERICNAME_STR
52

Microsoft Lync Server 2010 Understanding Exchange Integration

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Microsoft Lync Server 2010 Understanding Exchange Integration

Transféré par

Droits d'auteur :

Formats disponibles

Microsoft Lync Server 2010

Published: May 2011

Understanding and Troubleshooting Microsoft Exchange Server Integration

Unified Contact Store

Microsoft Exchange Delegates

Processing the Autodiscover Response

Caching Exchange URLs in Registry

Retrieving Data from Microsoft Exchange Mailbox

Reverse Proxy Pre-Authentication

MAPI/EWS Error Handling

UC Client Features (by Connection Type)

Lync / Attendant Feature

Exchange Server 2003 Lync Server (No EWS)

N/A N/A MAPI (Pushed) MAPI (On Demand)

UC Device Features (by Connection Type)

Polycom CX700 IP desk phone

Signed in through PIN (PIN/Certfiicate)

UC Client Features (Connectivity Failures)

All features impacted

MAPI unavailable MAPI Unavailable EWS Unavailable EWS unavailable

All features impacted

UC Device Features (Connectivity Failures)

Polycom CX700 IP desk phone

UC Device Features (Authentication Failures)

All features impacted

Expired Password Invalid EWS Credentials

All features impacted

Ethernet Only Ethernet + USB

All features impacted

Troubleshooting Exchange Integration

Lync Configuration Information

Outlook / Test E-mail AutoConfiguration

Checking the Registry for Cached EWS Data

Exporting EWS Configuration Information

Using Microsoft Exchange Synthetic Transactions

Get-MailboxServer NAE10All | .\new-TestCasConnectivityUser.PS1

CasServer --------NAE10All NAE10All NAE10All NAE10All NAE10All NAE10All

LocalSite --------Default-Fi... Default-Fi... Default-Fi... Default-Fi... Default-Fi... Default-Fi...

Scenario -------GetFolder SyncFolderItems CreateItem SyncFolderItems DeleteItem SyncFolderItems

CasServer --------NAE10ALL NAE10ALL NAE10ALL NAE10ALL NAE10ALL NAE10ALL NAE10ALL

LocalSite --------Default-Fi... Default-Fi... Default-Fi... Default-Fi... Default-Fi... Default-Fi...

Scenario -------Autodiscover... GetFolder SyncFolderItems CreateItem SyncFolderItems DeleteItem SyncFolderItems

Database Result ------------Mailbox Databas... Success

Analyzing the UC Device CELog File

Collecting Microsoft Exchange Traces

9. After successfully reproducing the error, click Stop Tracing Now.

Scenario: Integration Errors in Lync and on UC Phone (DNS)

Scenario: Integration Error on UC Phone (Certificates)

Scenario: Integration Error on UC Phone (Permissions)

Scenario: Integration Errors in Lync and on UC Phone (Corruption)

Appendix A: Lync / MAPI Error Strings

1782 1784 1785

IDS_MAPI_INTEGRATION_FAILED_TEMPLATE IDS_MAPI_ERROR_INSTALLATION_MISCONFIGURED IDS_MAPI_ERROR_PROFILE_MISCONFIGURED

IDS_MAPI_ERROR_OUTLOOK_CONTACT_PROVIDER_ AUTH_FAILED_OR_SERVER_DOWN IDS_MAPI_ERROR_OUTLOOK_CONTACT_PROVIDER_ UNKNOWN_ERROR MOC_PRODUCTGENERICNAME_STR IDS_MAPI_ERROR_CALENDAR_UNKNOWN_ERROR

IDS_MAPI_NOT_READY MOC_PRODUCTGENERICNAME_STR IDS_MAPI_ERROR_WAB_CONTACT_PROVIDER_UNK NOWN_ERROR MOC_PRODUCTGENERICNAME_STR

1802 3472 3473

IDS_MAPI_SPOOLER_DISCARDED_OLD_FILES MOC_PRODUCTGENERICNAME_STR IDS_DETAILS_SCHED_MEETING_ERR_NO_OUTLOOK IDS_DETAILS_SCHED_MEETING_ERR_OUTLOOK_ITE M

Appendix B: Lync / EWS Error Strings

IDS_MAPI_ERROR_AUTODISCOVERY_FAILED_TEMPO RARILY MOC_PRODUCTGENERICNAME_STR

IDS_MAPI_ERROR_AUTODISCOVERY_FAILED_PERMA NENTLY MOC_PRODUCTGENERICNAME_STR

IDS_MAPI_ERROR_WEB_SERVICE_AUTH_FAILED_OR _SERVER_DOWN MOC_PRODUCTGENERICNAME_STR

Vous aimerez peut-être aussi