Thursday, April 09, 2015
Thursday, January 08, 2015
Very useful read below for those persistent SChannel messages in the Event log.
Public information from Microsoft Lync/Skype team:
Recent and upcoming Google changes to the Chrome browser affect the Lync Web App on both Mac and Windows platforms, and require us to make changes to Lync Server and Lync Online in order to deliver a great experience for Chrome users. We have begun making these changes, and expect to complete them in the first quarter of 2015; in the meantime, when needed, we will provide users with manual work-around instructions as part of the meeting join experience.
For Mac users: Google discontinued support in October for the 32 bit version of Chrome on Mac. Because the existing Lync Web App works only in the 32 bit version of Chrome, Mac users must for now use either Safari or Firefox to join a Lync meeting. When joining a Lync meeting, users with Chrome set as their default browser will see a message instructing them to copy the Lync meeting URL, open Safari or Firefox, and paste the meeting URL into the new browser window. The Lync meeting will then begin. We plan to remove this manual step for Chrome users by adding support for the 64 bit version of Chrome early in 2015.
For Windows users: The most recent update to Lync Server 2013 (Cumulative Update 5.0.8308.857) provided manual work-around instructions to Windows users with the 32-bit version of Chrome set as their default browser, even though the 32-bit version of Chrome is still supported on Windows. On 12/31/2014, we released a new update to Lync Server 2013 (Cumulative Update 5.0.8308.866) to remove the manual work-around instructions and to allow the Lync Web App to run in Chrome as it did previously. We encourage administrators to apply Cumulative Update 5.0.8308.866 as soon as is practical to avoid the manual work-around. We have already begun applying this update to Lync Online.
What’s next? As noted above, we plan to add support for 64 bit Chrome on Mac early this year. We are also working on solutions to minimize the impact on Chrome users with the planned deprecation of the so-called “Netscape Plug-In API”, or NPAPI, targeted by Google for April, 2015.