Microsoft has released an update for Lync 2013 that is focused on correcting a single issue – memory leaks during a video call on hardware that has an accelerated H.264 chipset KB2933495. The patch will be offered to all computers via Windows Update and if the situation never applies to you – oh well, just be content to know you are on the latest version of Lync post SP1. There have been issues reported regarding the Gallery View within Lync not working correctly since SP1, but this hotfix does not address that issue. There are two known issues – Persistent Chat file transfers may fail and screen readers may not be able to read the Lync keystrokes.

There are now 4 pre-requisites for the Lync patch which include MSO (KB2727096), MSORES (KB2817624), IDCRL (KB2817626), and Lynchelp (KB2817678).

Additional Notes:
Lync Server 2010 build number is 4.0.7577.225
Lync 2010 Client build number is 4.0.7577.4419
Lync Server 2013 build number is 5.0.8308.577
Lync 2013 Client build number is 15.0.4569.1503
Lync Group Chat build number is 4.0.7577. 4409
Lync Group Chat Server build number 4.0.7577. 4409
Lync Group Chat Admin build number 4.0.7577. 4409
Lync Attendee build number is 4.0.7577.4356
Lync Attendant build number is 4.0.7577.4398
Lync Phone Editions build number is 4.0.7577.4420
Lync 2010 for iPhone build number 4.7
Lync 2010 for iPad build number 4.7
Lync 2010 for Android build number 4.0.6509.3001
Lync 2013 for Windows Phone build number is 5.2.1072.0
Lync 2013 for iPad build number is 5.2
Lync 2013 for iPhone build number is 5.2
Lync 2013 for Android build number 5.1.0000
Lync Basic 2013 build number is 15.0.4420.1017
Lync VDI 2013 build number is 15.0.4420.1017

Microsoft Lync Server 2013 has been designed to be a simple install and it is not unusual that the install is not what the client is looking for. Too often an install happens without ever considering the multitude of polices that exist allowing the client to control the features and configuration of Lync. Sure, the client, conferencing, and external policies are looked at but what about the call park configuration or mobility policy and all the others?

Understandably there is confusion as there are tons of polices, options, and configuration that should be reviewed. It does not mean that the defaults need to be changed just simple they should be reviewed. To assist me in the process I have created an Excel template that lists the common policies I review and (for both client and my sake) the explanations of the options placed into comments. While this is not an exhaustive list, it is a great place to start the discussion with clients and yourself when designing a Lync system. Remember – it is always easier to take away/disable features before the users have it.