Clicking on a meeting link does not launch the Lync 2013 client

Brian Hadfield -

When attempting to join a Lync 2013 meeting by clicking on the meeting link from an email or calendar item, the only option is to join using the Lync Web Client even though the Lync client is installed on the local machine.


This behavior occurs when the person scheduling the meeting is a Lync 2013 user and the meeting attendee is running Internet Explorer 11 as the default browser.   If you are unable to join a Lync meeting using the Lync client (and it is installed on the workstation) you will need to modify the IE 11 Compatibility View Settings for the meeting URL domain in order to join the meeting with the Lync 2013 client.

Adding the meeting URL domain to the Compatibility View Settings

  1. Launch Internet Explorer and click on the Tools icon in the top right hand portion of the browser window or press Ctrl+x.
  2. Select Compatibility View settings from the menu

  1. From the Compatibility View Settings window, type in the Add this website: field and click Add.  Click Close when done.
  1. When finished, close IE 11.
Now that the meeting URL domain has been added to the compatibility view settings, clicking on the meeting URL from an email or calendar item should launch the Lync 2013 client to join the conference.
Have more questions? Submit a request


  • Avatar
    Ben St. Hilaire

    We have encountered this issue a couple of times in the past day or so, so it's good to know about the IE 11 Compatibility View settings. However, we have also had it happen with other versions of the Lync client. The first time it happened, the person scheduling the meeting was using the Lync 2010 Mac client, and the person attempting to join the meeting was using the Lync 2010 Windows client (32 bit). We had successfully used this configuration with these two exact machines regularly between October 2013 and December 2013, then yesterday morning this issue suddenly began occurring. The issue occurred whether IE 11 or Firefox 25.0.1 was set to be the default browser; it would seem that it can happen with a wider variety of configurations.

    It would be helpful to know if there is a way to work around this issue with other browsers as well.

Powered by Zendesk