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.

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.

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

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

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

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.

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.

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

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