Here’s an update that seems largely for the benefit of the meeting junkies out there. This update (KB2956174) takes the Lync 2013 Client to 15.0.4701.1000.
I’m also pleased to report that it drops another of the pre-req’s we’ve been used to seeing, now down to 2 – and if you’re running with the February update there’s no change needed there.
- KB 3040496 Lync 2013 does not show who changes content in a shared whiteboard in an online meeting
- KB 3040495 Cannot scroll down text that is more than two pages in whiteboard in Lync 2013
- KB 3040494 “We couldn’t connect to the presentation” error occurs when an anonymous user shares a desktop in a meeting in Lync 2013
- KB 3040493 Lync Online users cannot search contacts in Lync 2013 in an environment that has a proxy server deployed
- KB 3040491 Meeting does not start if you click a meeting URL in a meeting invitation email message when Lync 2013 is signing in
- KB 3040489 Text labels for toll and toll-free numbers disappear in a meeting invitation when you create the meeting in Lync 2013
- KB 3040488 Outlook 2010 freezes, and then crashes when it runs together with Lync 2013
- KB 3040487 “We found a problem with you Lync Meeting. Please leave Lync client running for 15 mins” error occurs in Lync 2013
Nothing that I can see.
Screen-readers are an ongoing problem – unchanged from the known issues list of previous updates:
- 2898357 Screen readers cannot read aloud keystrokes during a Lync 2013 application or desktop sharing session in Windows
- 2932389 Persistent Chat file transfer fails between an external user and an internal user in Lync 2013
No new updates needed here, and the previous requirement for MSORES appears to be no longer (hence the strike-through):
|Office 2013 MSO (KB2920798)||1.0||2 February 2015|
|LyncHelp (kb2881083)||1.0||2 August 2014|
|MSORES (kb2817624)||1.0||6 Sept 2013|
The Install Process
I’ve converted to using Tom’s great “install-hotfixes” PowerShell module to install my updates these days. It’s kinda redundant with this month’s update as I only have one component to install, but I’ve still stuck with it here just in case you’re upgrading from an earlier patch level and have more bits to load.
Supposedly, yes. The KB says no, the install image (above) says yes, but if you bounce Lync (just Lync – not the PC) after the update it’s already showing the new version number. (And yes, I rebooted anyway and it remained unchanged).
Before & After
Here’s a before and after comparison of the x64 client on my Windows 8.1 machine.
|Lync 15.0.4693.1000 MSO 15.0.4693.1001||Lync 15.0.4701.1000 MSO 15.0.4693.1001|