Lync 2013 Server Update – July 2018

A full year between updates, this July update – to be Lync’s last – takes the server to 5.0.8308.1001 from last July’s 5.0.8308.992. This time ’round 7 components receive an update.

What’s Fixed?

  • Kb 4090984 Can’t receive notification email when a team-call group member answers your work calls
  • Kb 4090977 Loss of static meetings in Microsoft Lync Server 2013
  • Kb 4339732 Add a header to HTTP response over SIP TLS channel for HSTS compliance in Lync Server 2013
  • Kb 4090981 A deadlock was found in RtcSrv.exe that can cause Lync Server 2013 Front-end servers to stop listening for requests
  • Kb 4343061 Event ID 1000 (0xc0000005) and the RtcSrv.exe of the SBA/SBS crashes after the startup in the Lync Server 2013
  • Kb 4102001 Event ID 32002 and 32007 when RGS crashes with the “System.Reflection.TargetInvocationException” exception during announcement
  • Kb 4339731 Support viewing scheduled meetings in Skype for Business on Mac when AllowExchangeConnectivity is set to false
  • Kb 4339730 UCWA encounters an unhandled exception “System.ArgumentNullException” in Lync Server 2013
  • Kb 4090979 Can’t share desktop in a meeting in Lync Server 2013
  • Kb 4090980 Fix the startup to initialize McuInfra components only after ASMCU is completely ready to take new requests in Lync Server 2013

What’s New?

  • Kb 4343362 Support for TLS 1.2 in Lync Server 2013

Korbyn has called out a warning on this one, lest you misunderstand what’s going on:



Here’s the “before” view of it going on to my Standard Edition Front-End:


After you’ve run the installer & updated the databases (if required), don’t overlook the final few steps:

  1. Enable-CSTopology – which will fail if you have SfB2015 co-existing, so don’t be frightened by the error “Command execution failed: “1” error categories reported in topology document.”
  2. Fire off the bootstrapper: %ProgramFiles%\Microsoft Lync Server 2013\Deployment\Bootstrapper.exe
  3. And if you’ve skipped an update or two, best run Update-CsAdminRole after you’re done to make sure the new commandlets added in previous updates are accessible when PS Remoting.


Yes, the installer prompted me to reboot.

Revision History

11th July : This is the initial release.


– 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.