Hello,

The problem is that whenever a Windows 8.1 user tries to join a Lync server 2010 conference using Internet Explorer 10 (or 11, tried that too) the user can't join the conference. If the conference is created by a Lync server 2013 user joining works fine.

When using Lync 2010 client we get the following error in the client: "error id 87 source id 7".
When using Lync 2013 client we end up with a blank conversation window.
There are no traces in server log, client log or event log.

Below is a set of use cases that may help you to understand what is the problem scenario. Each of these works or does not work with both Lync 2010 and Lync 2013 client.

- Lync server 2010 conference, windows 7, Chrome, Firefox, IE 10 or 11 --> Works.
- Lync server 2010 conference, windows 8.1, IE 10 or 11 --> Does not work.
- Lync server 2010 conference, windows 8.1, Chrome or Firefox --> Works.
- Lync server 2013 conference, windows 8.1, Chrome, Firefox, IE 10 or 11 --> Works.

It does not help to add the meet address to IE compatibility list (Compatibility View Settings).
If i press F12 in IE and change the document mode of the meet page to IE 9 version then i can join meetings with Windows 8.1 and IE 10. Unfortunately i cannot make that as a default setting for the meet website.

Any ideas on how to get Lync server 2010 meetings working with Windows 8.1 and IE 10 or 11?
IE is the company default browser. Windows 8.1 is not a default operating system but we have increasing number of Windows 8.1 computers in our environment (mainly directors).

• Edited by TimoV Tuesday, January 28, 2014 11:17 AM

Have you updated to the latest Cumulative Update?

http://www.microsoft.com/en-us/download/details.aspx?id=11551

I installed the latest updates to the server and client.
No change. The problem is still the same.

It does not matter what company is organizing the meeting. Only the fact that the organizer is using server 2010 matters.

According to your description, it is hard to tell whether the issue is related with IE or Lync Server 2010 or both.

Compare the log when Lync client on Window 8.1 with IE 10 or IE 11 join Lync server 2010 conferencing and Lync Server 2013 conferencing.

Do you by any chance use F5 as reverse proxy? If so, what is the current code version?

.

Drago

Thanks for the responses.

We are using a F5 as reverse proxy but the same problem is from internal network on internal meetings so i do not believe that the F5 is the cause. I don't have access to the F5 so i can't check the code version myself.

Lisa, I believe that the problem is related to Windows 8.1 and IE and Lync Server 2010. I will check logs from different scenarios as soon as i have time for this problem again.