Quick Tip: Lync + Exchange Connectivity after O365 Move (Fix Conversation History + Meeting Tab)

In this quick tip we look at the Lync client behavior after a users mailbox has been moved from on-premise exchange to Office 365.

Problem

After a migration from your on-prem mailbox to Office 365 you may find your Lync Client is unable to connect to the Exchange Server and pull Conversation History and Meeting Tab.  You would find the following error.

pic1

Where Does the Client Store This Info?

As you can most likely guess, the Lync Client stores all of this information within the Registry.  If we browse to HKCUSoftwareMicrosoftOffice15.0Lyncuser@domain.comAutodiscovery

pic2

Here, we can see the available EWS and various other URLs are all pointing outlook.office365.com.  What I’ve seen on various Lync Clients there are situations where this information doesn’t update and the client is still pointing to the on-premise Exchange deployment.  For whatever reason, the client may never find it’s way home and the on-premise Exchange doesn’t forward the requests correctly.

The fix is easy.  Close the Lync client, and delete HKCUSoftwareMicrosoftOffice15.0Lyncuser@domain.comAutodiscovery key.  Once you start the Lync Client again, your client will go through the Exchange Autodiscover process and get the correct location will be published into the registry.

Share

0 comments on “Quick Tip: Lync + Exchange Connectivity after O365 Move (Fix Conversation History + Meeting Tab)”

  1. Chad Reply

    We’ve resolved this by having users sign out of Lync and then choose “Delete my sign-in info”, then just sign back in and their Lync client now connects to 365. We provide this as post-migration steps to users once we move their mailboxes to 365. Hope that helps and is typically easier than deleting reg entries

  2. Pingback: NeWay Technologies – Weekly Newsletter #115 – October 2nd, 2014 | NeWay

  3. Pingback: NeWay Technologies – Weekly Newsletter #115 – October 3rd, 2014 | NeWay

Leave a Reply

Your email address will not be published. Required fields are marked *