Unable to patch Skype on Sonus SBA

I recently was working on a Sonus SBA, patching away, when I found the patch process failing me. The copying, installation, and what appeared to be overall process was generally working but when the last patch (server.msi) was being applied, the process would fail.

Looking at the ASM/server directly I found the Skype server service was not starting – in fact it was unable to fully start as the DynDB database and log files were missing. Odd – must have been dropped during the last patch process, more than likely when the databases were being upgraded. Simple fix (or so I thought) – run Install-CsDatabase -LocalDatabases -Verbose and the missing database and log would be created…or should have been. However, the process failed with an error stating network name not found:

RtcDyn db state is: DbState_DoesNotExist

Dyn Data Path = C:\CsData\RtcDatabaseStore\rtclocal\DynDbPath, Dyn Log Path = C:\CsData\RtcDatabaseStore\rtclocal\DynLogPath.

Creating database rtcdyn from scratch. Data File Path = C:\CsData\RtcDatabaseStore\rtclocal\DynDbPath, Log File Path= C:\CsData\RtcDatabaseStore\rtclocal\DynLogPath.

Clean installing database rtcdyn.

System.IO.IOException: The network name cannot be found.

Now that is just silly – C:\ not found? I could navigate to the path, the permissions matched the FE servers I have in production, so something else was off. Turns out, when the database install process happens local (SBA/SE) or remotely (FE) the installation still uses the \\servername\c$ method to connect and create the databases. In the SBA case, it was hardened by Sonus security template and the C$ was removed.

Blog Image 10.png

It is also interesting to note this impacts tools like SCCM and its ability to push the client – no C$ = no ability to connect. So, in our case, the fix was simple. Add the C$ share to C:\ and re-start the upgrade. To add the share simply right-click in the Shares window, select New Share, and start the share wizard.

Blog Image 11.png

Enter C:\ as the folder path you wish to share.

Blog Image 12.png

Windows will warn you this is a bad idea – acknowledge that you know more than the system by clicking Yes.

Blog Image 13.png

Enter the hidden share name of C$ (and optionally enter a description (the standard being Default Share)).

Blog Image 14.png

Select the second radio button, granting administrators full access and others read. The permissions will be reset after a reboot and selecting the second option allows you to validate/test the process.

Blog Image 15.png

The final result should show the admin share in your list.

As mentioned, this is only a temporary fix – the share is removed when rebooted and the system policies are reapplied. So make sure you perform this workaround just before the patch is installed and all should work as expected.

Blog Image 16.png

RtcDyn db state is: DbState_DoesNotExist

Dyn Data Path = C:\CsData\RtcDatabaseStore\rtclocal\DynDbPath, Dyn Log Path = C:\CsData\RtcDatabaseStore\rtclocal\DynLogPath.

Creating database rtcdyn from scratch. Data File Path = C:\CsData\RtcDatabaseStore\rtclocal\DynDbPath, Log File Path= C:\CsData\RtcDatabaseStore\rtclocal\DynLogPath.

Clean installing database rtcdyn.

Creating database rtcdyn. Attempt: 1

Setting the database rtcdyn to restricted mode.

Database rtcdyn set to mode Restricted.

Setting database options.

Begin transaction.

Creating objects from dbcommon.sql.

Creating database objects.

Executing Types.sql...

Soder on November 28, 2016 asked "Was Sonus notifed, or they simply dontcare at all?" 

Brian then replied "They were not but the issue is with the cmdlet Install-CsDatabase which is part of Skype and not something Sonus created."

Soder replied "Ok, seems I can reply now.So. You wrote
"In the SBA case, it was hardened by Sonus security template and the C$ was removed."
Its Sonus fault. Doing these "hardening" things without doing their homework (plan careefully, do impact analysis, etc. etc.). And as you say the C$ gets removed if the hardening is activated, it means all Sonus equipment owners are affected all over the world. I wouldnt consider this a minor small tiny issue, right?"

Brian replied "Still not in the 'Sonus is at fault' court - the security templates are provided by Microsoft but I will ask for clarity from both Sonus and the Microsoft PG and post a reply. It should be noted that the application of the Security Template - while permanent - is optional."

Soder replied "Well, if the template comes REALLY from Microsoft, thats a different beast (is that like a Security Policy template called Hardened Workstation or something similar?). But still, Sonus allows the enablement / disablement of this template on their GUI, so assume they have tested this before rolling out to customers. I really want to believe they dont just accept everything unconditionally from MSFT and implement without checking its effects first. I know this is a completely optional feature, so it may not affect literally everybody. But as the option is offered to customers without any warning that it may break the whole Sfb update procedure, I am still confident the ball is on Sonus side."

Brian replied "So yes - the security templates are offered from the Microsoft security team and you can apply the XML files to any computer/server - the process stems back to the Windows 2000 days. The key point to remember is the SBA image/process is a managed MS process much like the LPE phones. Sonus and the SBA image are up to the mercy of the MS team and their direction. So, the only question is where did the direction come from for the template - MS or did Sonus do this on their own. That question I have asked and am awaiting the answer."

Mark H on December 1, 2016 stated "I am running Lync 2013 SBA from Sonus and I see the share is disabled as well  but CU are installing properly.
Maybe Microsoft changed something on their installer."

Kevin I replied "Kevin I from Sonus here. The CU Installer has changed with Skype for Business June CU. In previous CU's the updater did not use the SBA C$ share to update. The security template was changed based on customer feedback to remove access to the c$ share. It was changed a couple of years ago with no issues until this CU.

We have implemented a change to our CU installer to restore the share before the CU installs and then remove it afterwards. 

We are also working with Microsoft to understand if there is a way to change the way the CU's are applied to the SBA. Until then the change I mentioned above in the installer will stay to ensure the CU will install moving forward."

Soder replied "Kevin I:
maybe this is not the best platform to discuss this topic, but why there is not a single(!) word about this whole "Security Hardening Template" topic in the 1700+ pages Complete Sonus Documentation PDF ? Regardless of v4.x v5.x or v6.x."

Brian replied "@Soder - have you seen this link? support.sonus.net/.../Applying+an+SBA+Security+Template"

Soder replied "You are right! I didnt find the topic because I was looking for the "hardening" keyword as seen on the button, not searched for generic expression like "template" or "security", as those spit out 1000+ hits on the 1700+ pages document. Yes, I was blind, but organization of content in the Sonus documentation is yet another (saddening) topic.

The first Skype for Business Patch has Arrived

It didn't take long for the first patch for Skype to come along and it is a highly important patch for many. A bug discovered after RTM of Skype was discovered with Exchange UM Interaction and normalization. The actual bug is KB3069206 and stalled many Skype for Business upgrades as Exchange UM Auto Attendants are kind of important.

In addition to the UM fix there are smaller yet just as important fixes listed such as dropping parked calls, SfBWA (aka LWA) crashes, RGS agent transfer issues, and so on. In short - if you have Skype for Business deployed this patch is a must and for those waiting because of the aforementioned bugs, migrations can now move on.

Upgrades are a bit different in Skype for Business only because of the new patching methods. If you were comfortable with patching in Lync & clearly understood upgrade domains, then there is no change. There are also no updates required to the Skype databases in this release so while we can run the good-old Install-CsDatabase command you will simply get a result of:

 

 

 

VERBOSE: All databases at the specified installation location are already up to date.

 

 

 

Make sure all servers are updated in the FE pool, the Edge servers, P-Chat, Mediation and any app servers you may have. The core components at a minimum will be updated while servers like the Edge role have an actual update.

For those that have a highly non-recommended two-node Enterprise Pool, there is an additional Fabric step required. Once you have patched the pool and rebooted, run the following command from PowerShell.

 

 

 

Reset-CsPoolRegistrarState -ResetType FullReset

 

 

 

Additional patching information can be found on the KB Update page 3061064.

Product

Version

KBs

Download

Skype Server 2015

6.0.9319.55

3061064

MS Download

 

Additional Notes: 
Lync Server 2013 build number is 5.0.8308.887

Lync 2013 Client build number is 15.0.4727.1001

Skype for Business Server 2015 build number is 6.0.9319.55
 

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

Lync Attendant build number is 4.0.7577.4098

Lync Phone Editions build number is 4.0.7577.4463
Lync Phone Edition (Tanjay) build number is 4.0.7577.4463
Lync for Mac 2011 build number is 14.0.11
 

Lync 2013 for Windows Phone build number 5.9.1371.0

Lync 2013 for iPad build number 5.7.563

Lync 2013 for iPhone build number 5.7.563

Lync 2013 for Android build number 5.6.3.1
Lync 2013 for Android tablet build number 5.5.3.8919
Lync Windows Store App build number is March 2014
 

Lync Basic 2013 build number is 15.0.4420.1017
Lync VDI 2013 build number is 15.0.4420.1017

 

Jeremy said on July 29: "I've had mixed results with the S4B upgrade from Lync 2013.  In the test environment - smooth sailing and everything worked.  In production, even after installing the S4B update, Response Groups still failed 100% of the time.  Since Response Groups are critical in my environment, we reinstalled Lync 2013 on all the servers and restored our Lync databases from backup.  What started as a short upgrade turned into a lengthy recovery.  Needless to say, I'll be waiting to try another S4B upgrade for a while."

Brian responded : "@Jeremy - Interesting regarding RGS. Of the 10 upgrades/new installs we have not had any issue with RGS. Sounds like there was a larger issue at play."

February 2015 Lync Client/Server Update

Microsoft quietly released the Lync Client and Server CU for February 2015 and perhaps with good reason; little to nothing appears to have been added to Lync other than a not quite functioning correctly  CsClientPolicy setting EnableSkypeUI. The policy is designed to allow a Lync 2013 server admin to preserve the look and feel of the Lync client after the 'Skype' CU has been delivered either automatically via O365, via Windows Update, or via the system administrator. By default this value is $NULL which SHOULD equate to ‘Use the Lync UI’ but instead it defaults to ‘Use the Skype UI’. Setting the value to $FALSE will force the Lync UI and in future client releases (read that as RTM) the feature will work as expected.

Missing/odd features is definitely not a reason to apply a patch and since it has been 30 days since the release with no known/major issues I would say all is good. The patch does update Core, Server, RGS, Management, and Web Components as well as databases.

There are a few database upgrades required for the backend databases (QoE), and for the CMS (assuming you are up-to-date (i.e. since December 2014)). It is interesting that Microsoft is calling out the sequence with more vigor and I cannot stress enough how important it is to make sure your databases match your CU level or ‘bad things happen.’  We discuss over and over how to check upgrade readiness as well the database upgrade methods so if you are unclear, review previous posts here.

Lync Server 2013

5.0.8308.872

2809243

MS Download

 

Lync 2013 Client 32-bit

15.0.4693.1001

2920744

 

 

 

Lync 2013 Client 64-bit

15.0.4693.1001

2920744

MS Download

Additional Notes: 
Lync Server 2010 build number is 4.0.7577.709

Lync 2010 Client build number is 4.0.7577.4446

Lync Server 2013 build number is 5.0.8308.872

Lync 2013 Client build number is 15.0.4693.1001
 

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

Lync Attendant build number is 4.0.7577.4098

Lync Phone Editions build number is 4.0.7577.4455
Lync Phone Edition (Tanjay) build number is 4.0.7577.4451
Lync for Mac 2011 build number is 14.0.10

Lync 2010 for Windows Phone build number 4.3.8120.0

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 5.8.1327.0

Lync 2013 for iPad build number 5.6

Lync 2013 for iPhone build number 5.6

Lync 2013 for Android build number 5.5.3.8935
Lync 2013 for Android tablet build number 5.5.3.8919
 

Lync Basic 2013 build number is 15.0.4420.1017
Lync VDI 2013 build number is 15.0.4420.1017

Microsoft has released August 2014 CU for Lync Server 2013

It is official – an update has finally been released for Lync Server 2013! The update is effectively 8 months in the making so don’t let the small build increment fool you (although one could argue a few hundred rounds is far from insignificant).

Nearly half of all components are updated with this patch – even Windows Fabric – on Front-end servers and all components on the Edge, but no new features are called out as this is a bug fix/stabilization patch. A database update is required (CMS does not), so do not forget to update with the typical Install-CsDatabase commands after upgrading the FE pool servers. We discuss over and over how to check upgrade readiness as well the database upgrade methods so if you are unclear, review previous posts here.

Product

Version

KBs

Download

Lync Server 2013

5.0.8308.738

2809243

MS Download

Additional Notes: 
Lync Server 2010 build number is 4.0.7577.230
Lync 2010 Client build number is 4.0.7577.4445
Lync Server 2013 build number is 5.0.8308.738
Lync 2013 Client build number is 15.0.4605.1003

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.4098
Lync Phone Editions build number is 4.0.7577.4450

Lync 2010 for Windows Phone build number 4.3.8120.0
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 5.4.1087.0
Lync 2013 for iPad build number 5.4
Lync 2013 for iPhone build number 5.4
Lync 2013 for Android build number 5.3.1100

Lync Basic 2013 build number is 15.0.4420.1017
Lync VDI 2013 build number is 15.0.4420.1017

Microsoft has released July 2014 CU for Lync Phone Edition

We are now officially into the 3rd quarter of 2014 and thus into the third round of patching. I know we did not see patches for Lync Server 2013 in the 2nd quarter, but one can assume the trend will not hold and patches will be coming soon. As a teaser Microsoft has released the Lync Phone Edition (LPE) update for Q3, their links are found below. It is always recommended to remain up-to-date with LPE patches regardless of the fixes included.

In this iteration of LPE a Daylight Savings Time (DST) issue is resolved for Egypt and Morocco…nothing exciting but keeping the phones up-to-date ensures you will not run into any patching issues with the next release. You will also notice the CX700/LG-Nortel 8540 was not included in the update cycle – does it not require the DST fix or is this simply Microsoft stating ever so gently to move off the old phones?

*UPDATE*
As noted in the comments below, the CX700 has NOT been updated since April but it is now included in the matrix below.

Product

Version

KBs

Download

Lync Phone Edition (for Aastra 6721ip and Aastra 6725ip)

7577.4450

2973938

MS Download

Lync Phone Edition (for HP 4110 and HP 4120)

7577.4450

2973939

MS Download

Lync Phone Edition (for Polycom CX500, Polycom CX600, and Polycom CX3000)

7577.4450

2973941

MS Download

Lync Phone Edition (for Polycom CX700/LG-Nortel 8450)

7577.4444

2973942

MS Download

Additional Notes: 
Lync Server 2010 build number is 4.0.7577.230
Lync 2010 Client build number is 4.0.7577.4445
Lync Server 2013 build number is 5.0.8308.577
Lync 2013 Client build number is 15.0.4605.1003

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.4098
Lync Phone Editions build number is 4.0.7577.4450
Lync Phone Edition (Tanjay) build number is 4.0.7577.4444

Lync 2010 for Windows Phone build number 4.3.8120.0
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 5.4.1087.0
Lync 2013 for iPad build number 5.4
Lync 2013 for iPhone build number 5.4
Lync 2013 for Android build number 5.3.1100

Lync Basic 2013 build number is 15.0.4420.107
Lync VDI 2013 build number is 15.0.4420.1017

Microsoft has released CU5 for Exchange Server 2013 and RU6 for Exchange Server 2010 SP3

It seems like just yesterday that Microsoft released SP1 for Exchange Server 2013 and yet CU5 (aka as SP1 plus first cumulative update) is out in the wild. As with all Exchange 2013 CUs the update is a FULL install of Exchange 2013 so the download is approximately 1.5GB in size. The good news is, unless you require maintaining older copies/versions of Exchange you can discard previous version as the latest and greatest DVD can be used for updating an Exchange Server or building an Exchange Server (that’s right, read slipstreamed).

There is a known “issue” with the latest release and the built-in Managed Availability Probe. Basically, you will see that the Exchange Share Cache Service restarts often because of an overly aggressive probe.  Details of the issue may be found here but while the logging events are annoying, they are harmless. Your bigger issues may be where monitoring software starts to light up once CU5 is installed and if you do not want to modify the monitoring software, you can disable the probe (again in the KB article).

Be prepared for AD/schema updates when applying CU5 and as always, make sure the PS Remote Script Execution Policy is set unrestricted before installing the update (from an elevated PS prompt Set-ExecutionPolicy Unrestricted). Beyond the OAB improvements in distributed environments and the Managed Availability Probe bug, the remaining updates are basic fixes/updates to the existing code.

For Exchange 2010 SP3, RU6 is a basic update of bug fixes and updates to improve overall system stability.

Both updates have been applied to my labs with no issue and I suspect if all goes well the 2013 CU5 will be in my production in the next few weeks.

Product

Version

KBs

Download

Cumulative Update 5 for Exchange Server 2013

15.00.0913.022

2936880

MS Download

Exchange Server 2013 CU5 UM Language Packs

15.00.0913.022

2872696

MS Download

 

 

 

 

Update Rollup 6 for Exchange 2010 SP3

14.03.0195.001

2936871

MS Download

 

Additional Notes: 
Lync Server 2010 build number is 4.0.7577.230
Lync 2010 Client build number is 4.0.7577.4445
Lync Server 2013 build number is 5.0.8308.577
Lync 2013 Client build number is 15.0.4605.1003

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.4098
Lync Phone Editions build number is 4.0.7577.4444

Lync 2010 for Windows Phone build number 4.3.8120.0
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 5.4.1087.0
Lync 2013 for iPad build number 5.4
Lync 2013 for iPhone build number 5.4
Lync 2013 for Android build number 5.3.1100

Lync Basic 2013 build number is 15.0.4420.1017
Lync VDI 2013 build number is 15.0.4420.1017

Microsoft has released CU April 2014 for Lync Edition Phones

New Lync Phone Edition (LPE) firmware has been released for all phones. Keeping the phones up-to-date with current firmware is imperative – too often I run into Lync certificate updates where the phones do not have a current root certificate for newly issued public certs and everything comes to a screeching halt. As a side, my basic work around for this is to setup an SE server with an internally accessible CA (read http is in the CRL and AIA), update it to the latest firmware, and then use on the phone on production. A pain, yes, but sometimes needed even if you are diligent as it is not uncommon to receive new phones with old firmware.

Product

Version

KBs

Download

Lync Phone Edition (for Aastra 6721ip and Aastra 6725ip)

4.0.7577.4444

2954032

MS Download

Lync Phone Edition (for HP 4110 and HP 4120)

4.0.7577.4444

2954033

MS Download

Lync Phone Edition (for Polycom CX500, Polycom CX600, and Polycom CX3000)

4.0.7577.4444

2954034

MS Download

Lync Phone Edition for Polycom CX700 and LG-Nortel IP Phone 8540

4.0.7577.4444

2954035

MS Download

Additional Notes: 
Lync Server 2010 build number is 4.0.7577.230
Lync 2010 Client build number is 4.0.7577.4445
Lync Server 2013 build number is 5.0.8308.577
Lync 2013 Client build number is 15.0.4605.1003

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.4098
Lync Phone Editions build number is 4.0.7577.4444

Lync 2010 for Windows Phone build number 4.3.8120.0
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 5.4.1087.0
Lync 2013 for iPad build number 5.4
Lync 2013 for iPhone build number 5.4
Lync 2013 for Android build number 5.3.1100

Lync Basic 2013 build number is 15.0.4420.1017
Lync VDI 2013 build number is 15.0.4420.1017

Microsoft has released a March 2014 update for Lync 2013 to address a memory leak

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

Product

Version

KBs

Download

Lync 2013 Client 32-bit

15.0.4569.1503

2863908

MS Download

Lync 2013 Client 64-bit

15.0.4569.1503

2863908

MS Download

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 has released CU January 2014 for Lync Server 2010/2013 & Lync Edition Phones

Microsoft has released updates for Lync Server 2013 and Lync Server 2010 on time for their quarterly release cadence. The updates are bug fixes to the product and not introducing new features (none of the 2013 databases are updated in this release). If this CU is being applied to RTM, then follow the instructions here to update or check your version level using Doug Deitterick’s blog post.

In addition to the server patches, the Debugging Tools and Resource Kit has been updated. Unfortunately the updates are actually full installs so you will need to uninstall any previous versions before the apps are “updated”. The good news is the Debugging Tools contain the correct updated TMX file from the January 2014 CU so there is no need to manually replace it with the locally installed copy.

Finally, Lync Edition phones have been update which include the entire line of Aastra, HP, and Polycom phones. Updating them is the same method it has been so no news there.

Product

Version

KBs

Download

Lync Server 2013

5.0.8308.577

2809243

MS Download

Lync Server 2013 Debugging Tools

5.0.8308.577

2905051

MS Download

Lync Server 2013 Resource Kit Tools

5.0.8308.577

2905053

MS Download

 

 

 

 

Lync Server 2010

4.0.7577.225

2493736

MS Download

Lync 2010 Client 32-bit

4.0.7577.4419

2912208

MS Download

Lync 2010 Client 64-bit

4.0.7577.4419

2912208

MS Download

 

 

 

 

Lync Phone Edition: Aastra 6721ip / 6725ip

4.0.7577.4420

2918033

MS Download

Lync Phone Edition: HP 4110 / 4120

4.0.7577.4420

2918035

MS Download

Lync Phone Edition: Polycom CX500 / CX600 / CX3000

4.0.7577.4420

2918038

MS Download

Lync Phone Edition: Polycom CX700 / LG-Nortel 8540

4.0.7577.4420

2918036

MS Download

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.4551.1007
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.4098
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 has released CU July 2013 for Lync Server 2013

Yesterday Microsoft released Cumulative Update (CU) July 2013 for Microsoft Lync Server 2013. The update is a typical Lync Server path file but has some additional steps and safety measures built-in. To start, the upgrade now supports a SQL mirror so there is no need to break and re-create the HA configuration. There are additional Lync Management Shell commands to be run in this process starting with Get-CsPoolUpgradeReadinessState. While the readiness check is a good idea for SE deployments, the importance is less as the pool is either functioning or not.

  1. Execute Get-CsPoolUpgradeReadinessState for a Lync PowerShell command. Assuming the returned value is Ready you are to begin the process. Listed in the returned information is the state of the front-end servers within the pool and their current upgrade domain readiness state. User data will be distributed among multiple front-end servers (up to 3) and making sure a server upgrade combination that takes down all three of a user’s pool is avoided is important. The easiest way to avoid this is to simply upgrade a single server at any one time and wait for the server to come back online and list a status of True.

  2. Upgrading a pool that has active users can be a challenge when a high uptime is desired. If you are faced with this dilemma, start with shutting down the front-end services of a desired pool member by using the Stop-CsWindowsService –Graceful cmdlet. Using the graceful switch the services stop only after current requests have been filled. It also prevents any further request from being queued so think of it as an option to shut down as soon as possible with as little disruption as possible. This doesn’t mean people logged into that pool sever will not be logged out and back into another pool member, it simply means if they are in an active conversation the server will not interrupt the communications.

  3. Once the services have been shut down gracefully (or if you have an outage window and simply want to perform the upgrade, launch the LyncServerUpdateInstaller.exe. This can be done at the command line as before or by simply launching the executable and running the GUI.

  4. The next step is the beloved backend database upgrade. The SE upgrade is the same as before with the running of the commandInstall-CsDatabase -ConfiguredDatabases -SqlServerFqdn SE.FQDN -Verbose. If you have an SE deployment with Persistent Chat collocatedyou must run the above command with the -ExcludeCollocatedStores parameter and perform the upgrade to the PChat databases after the initial install.

    1. To upgrade a collocated PChat database on an SE server the command you would need to run next would be Install-CsDatabase -DatabaseType PersistentChat -SqlServerFqdn PChatBE.fqdn -SqlInstanceName DBInstance -Verbose. Again, this is only required when you have an SE with PChat collocated.

  5. After all the application and user databases have been upgraded, the final step is updating the CMS database. This upgrade is ONLY required if you are updating your server from Lync Server 2013 RTM as the update has not changed since February 2013 Cumulative Updatebut it does not hurt to run it if you are not sure. To do this, run the command Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn CMS.FQDN -SqlInstanceName DBInstanceName -Verbose.

  6. It is recommended that the Enable-CsTopology command is run after the upgrade to ensure mobility is active and functioning andbootstrapper is executed (found in a default install at%ProgramFiles%\Microsoft Lync Server 2013\Deployment\Bootstrapper.exe) on all SE, EE, and Director servers (basically anywhere the web components are installed).

  7. After the upgrade of a front-end server is complete, reboot the server (you could just start services, but I prefer a reboot) and before moving on to the next make sure the Get-CsPoolUpgradeReadiness cmdlet returns a Ready state before moving on.

Make sure all servers in the environment have been updated, including the PChat, Edge, custom application servers, etc. when performing this update and should you have a large Lync Server 2013 installation, expect the process to take some time. I expect additional updates for clients and devices will be coming shortly so check back for updates often.

Product

Version

KBs

Download

Lync Server 2013

5.0.8308.420

2809243

MS Download

Additional Notes:
Lync Server 2010 build number is 4.0.7577.216
Lync 2010 Client build number is 4.0.7577.4378
Lync Server 2013 build number is 5.0.8308.420
Lync 2013 Client build number is 15.0.4454.1506
Lync Group Chat build number is 4.0.7577.4102
Lync Group Chat Server build number 4.0.7577.4778
Lync Group Chat Admin build number 4.0.7577.4102
Lync Attendee build number is 4.0.7577.4356
Lync Attendant build number is 4.0.7577.4098
Lync Phone Editions build number is 4.0.7577.4387
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.0.8250.0
Lync 2013 for iPad build number is 5.0
Lync 2013 for iPhone build number is 5.0
Lync Basic 2013 build number is 15.0.4420.1017
Lync VDI 2013 build number is 15.0.4420.1017