2001 Updates for Lync 2010 Products

MICROSOFT HAS UPDATED THE LYNC CLIENT (32 AND 64 BIT) UPDATES. KB2496325HAS BEEN SUPERSEDED BY KB2540951 WHICH IS DATED APRIL 27, 2011!

On April 4th, Microsoft anounced the release of the updates for the following Lync client products:

Some links are still working their way through the system and will become available within a week from today.

Some of the KBs are still in process. These should be available by 4/8.

Additional Notes:

Lync Client and Group Chat build number is 4.0.7577.253

Lync Attendee/Attendant build number is 4.0.7577.254

The Phone Editions build number is 4.0.7577.250

PIN Authentication works using the Test-CsPhoneBootstrap cmdlet but fails on Lync devices

Recently I decided to 'play' with my Lync devices by moving them to a dedicated voice VLAN on my network. After doing so, I noticed I was unable to use PIN authentication. I found this extremely odd especially since I had just told a fellow colleague how simple the PIN process was. From the Lync 2010 servers the Test-CsPhoneBootstrap cmdlet was passing with a code of Success making me even more perplexed. Digging a bit deeper into the issue, I noticed that the phones authenticating using a PIN as well as my CX700 phones were taking a significant amount of time at boot while they were acquiring their time.

Comparing my two VLANs nothing stood out until I remembered I did not allow the new VLAN Internet access (why should the phones need to go out to the Internet after all?). Well, as it turns out, they were getting their time service from time.windows.com come even though my Windows domain controllers were configured as NTP servers and their SRV records existed in DNS.

The solution was quite simple and all devices benifited from a faster boot time. Within DHCP there is a standard option, 042 NTP Servers, which I configured with mydomain controllers as the defined values. As soon as I added this option, the phones received their time nearly instantly and PIN authentication worked as expected.