Lync 2013 / SfB 2015 Client Update – September 2018

It’s been a month since our last update to the client and our fresh Spring update [here in the southern hemisphere] brings one fix. Kb4092457 takes the Office 2013-based client from 15.0.5059.1000 to “15.0.5067.1000” (according to the KB).

The client – and get-csconnections – report it as 15.0.5065.1000.

What’s Fixed

  • Kb 4346575 Can’t transfer a team call to a team member by clicking the Transfer button in Skype for Business.

What’s New / Changed

Nothing documented.

Known Issues

Nothing documented.

Pre-Req’s

It’s all good if you’ve been diligent in your patching.

If however your patching isn’t to current you’ll need to check you have *all* of these pre-req’s. The Office 2013 SP1 requirement still applies if you’re using Outlook 2010. (Lync 2013 in all of its flavours – e.g. Lync Basic – is still a component of Office 2013).

Update

Download

Current Version

Released

Update for Office 2013 (KB3054853) (NOTE 1 BELOW) 1.0 9 June 2015
LyncHelpLoc (kb3191937) 1.0 22 May 2017
Microsoft Office 2013 Language Pack Service Pack 1 (KB2817427) 1.0 13 February 2014

NOTE1: “You do not have to apply update KB3054853 if you applied the April 14, 2015, update (KB2889923) or the May 12, 2015, security update (KB3039779) for Lync 2013 (Skype for Business)”

Download

This is the client fix itself:

  • x86 (lync2013-kb4092457-fullfile-x86-glb.exe)
  • x64 (lync2013-kb4092457-fullfile-x64-glb.exe)

Reboot

I have all the pre-req’s already installed, had exited the client before we started & was not prompted for a reboot.

Before / After

Before

After

SfB 15.0.5059.1000 MSO 15.0.5031.1000 SfB 15.0.5065.1000 MSO 15.0.5031.1000
Before-Sept2018-15.0.5067.1000 After-Sept2018-15.0.5067.1000

Revision History

10th September 2018: This is the initial post. That you @GuyBachar for alerting me to this one.

  

– G.

Leave a Reply

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

... and please just confirm for me that you're not a bot first: Time limit is exhausted. Please reload the CAPTCHA.

This site uses Akismet to reduce spam. Learn how your comment data is processed.