Last week i noticed on Twitter thanks to @randychapman there’s been a new Cumulative Update for Skype for Business Server and this is CU8.
This is a massive CU which 32 fixes / improvements so be sure to check it out ! also this always SfB Server users to move straight to Microsoft Teams !!! This follows on from CU7 in July 2018.
It also mentions this cumulative update includes a defense in depth fix and enables Location-Based Routing to support the Skype for Business mobile clients.
Update Version is now 6.0.9319.537
Date published 08/01/2019
Download link here
Its listed on the KB here
There is one known issue where when you run the Test-CsDatabase cmdlet to test the configuration of the Skype for Business Server databases, you could notice that the installed local XDS (Master) database version isn’t matched with the “Expected Version”. More info here
What’s the fixes and improvements ?
WOW !!! there’s alot in here !!! 32 in total !!!!
Quick highlights for me
- SfB Server to Teams cmdlets which will ease migration to Microsoft Teams
- Lots of SfB for Mac and SfB Mobile UCWA updates and fixes
- Conversion interop messages for SfB Mac and Mobile with Microsoft Teams
- Lots of Location based routing (LBR) fixes
- Fix for CU7 SQL Server 2008 R2 installation issue
- Some RGS fixes
- Watcher node update for Germany
- TLS update fix for TLS1.2 only
- SBA / SBS fix
- Some Windows Server 2016 fixes for Test-csbootstrap
- VBSS fixes
How to get update ?
Download is here
Full details on Fixes
This cumulative update fixes the following issues and there so many in this CU again like July 2017 CU7 its another jam packed CU !! The SfB Server team have been very very busy yet again !
Ill try and summarize some but it will be hard
|Fixes||Cause and Fix|
||In a Microsoft Skype for Business Server 2015 environment, an anonymous participant joins a Skype for Business meeting by using the Skype for Business Web App or Skype Meeting App. Even though the conferencing policy (where AllowParticipantControl and AllowExternalUserControl are both set to False) doesn’t enable participants to take control, the participant can give control to other users in the meeting and bypass the conferencing policy.
Note This fix only applies to Skype Meeting App. If you are using the Skype for Business Web App, you have to enable the Skype Meetings App to replace the Skype for Business Web App.
To enable the Skype Meetings App, please run the following cmdlet:
Set-CsWebServiceConfiguration -MeetingUxUseCdn $True
||In a Microsoft Skype for Business Server 2015 environment, you create a Skype for Business mobility policy in which the AllowSaveCredentials parameter is set to False. In this scenario, users can’t save their credentials information (such as passwords) on their mobile devices. However, when a user tries to sign in to Skype for Business by using the Skype for Business on Mac desktop client, the password is also not saved even if the user selects the Keep me signed in option on the client. It’s expected that the Skype for Business on Mac desktop client can save the sign-in credentials.
The issue occurs because the mobility policy was applied to the Skype for Business on Mac desktop client, and it was by design. After you apply this update, the mobility policy is applied only to the mobile clients.
|4464370 Skype for Business UCWA clients can’t be distinguished on CDR report if connection is internal or external||In a Microsoft Skype for Business Server 2015 environment, you use a Skype for Business UCWA client that’s in an external network to start a call with a Skype for Business client user. You may find that the value of Is From user internal always shows Yes on the Call detail recording (CDR) report. It’s expected that the clients should be flagged correctly as external or internal on this report.|
|4458698 Notify Skype for Business on Mac and mobile users that the conversation is an interop conversation in Skype for Business Server 2015||The interoperability of Microsoft Teams and Skype for Business enables users in the same organization to make one-on-one voice and video calls or chat. However, there’re some limitations about the interop experience, such as screen sharing (desktop or app sharing), file transfer for two-party chats, and so on. For a richer experience, users may have to know the client that the other side uses. After you apply this update, Skype for Business on Mac and mobile users can be notified that it is an interop conversation when users are in a one-on-one chat or call.
|4345985 “Failed to setup database rtcxds” error when you upgrade the SQL Server 2008 R2 back-end database in Skype for Business Server 2015||In a Microsoft Skype for Business Server 2015 environment, you use Microsoft SQL Server 2008 R2 as a back-end database. After you install the July 2018 cumulative update 6.0.9319.534 (CU7) for Skype for Business Server 2015, you may find the SQL Server database can’t be upgraded. In addition, you may receive an error message that resembles the following:
Failed to setup database rtcxds due to an unexpected error.
Detail: Microsoft.SqlServer.Management.Smo.UnknownPropertyException: Cannot write property TargetRecoveryTime.This property is not available on SQL Server 2008 R2.
This issue occurs because a value of targetRecoveryTime attribute isn’t set correctly, and it isn’t present in SQL Server 2008 R2.
|4132306 Invitee visibility delay when a UCMA application uses AudioVideoMcuSession.BeginDialOut to create a conference||In a Microsoft Skype for Business Server 2015 environment, you use a Unified Communications Managed API (UCMA) application to schedule an audio or video conference and dial out a PSTN number from the conference by using the AudioVideoMcuSession.BeginDialOut method. After the UCMA application performs the dial-out operation from the Audio/Video Multipoint Control Unit (AVMCU), the invitee accepts the call and joins the conference successfully. However, the conference organizer or other participants could not immediately see the invitee through the UCMA application. It may delay for four to five seconds. It’s expected that the invitee can be visible in less than one to two seconds.|
|4458688 Support to prevent external file transfer especially for Skype for Business on Mac users in Skype for Business Server 2015||In a Microsoft Skype for Business Server 2015 environment, you create a file transfer filter configuration for the Edge Server to block a user’s ability to transfer certain type files by using a Skype for Business Server client in an external network. When a Skype for Business Server client that’s enabled by Microsoft Unified Communications Web API (UCWA), such as a Skype for Business on Mac client, is externally talking to an internal client, you may notice that it doesn’t honor the file transfer policy as configured.
This issue occurs because the external file transfer’s traffic doesn’t traverse the Edge Server. Therefore, the external file transfer is enabled.
|4458695 QoE Call Detail SubReport shows a wrong caller/callee connection type in Skype for Business Server 2015||In a Skype for Business Server 2015 environment, you successfully make a telephone call with another Skype for Business user by using your mobile phone on mobile cellular network. Then you open the details of this session in the User Activity report. You may notice that the caller connection type is displayed as Tunnel (VPN) instead of MobileBB (Mobile Broadband) in the QoE Call Detail SubReport (which is a part of Media Quality report).
This issue occurs because the connection type of MobileBB and Tunnel is interchanged.
|4459712 Update parameters of Move- CsUser in Skype for Business Server 2015||After you apply this update for Microsoft Skype for Business Server 2015, the irrelevant parameter ConcurrentMovesPerFE will be removed from the Move- CsUser cmdlet. In addition, the following parameters are reordered so that they can first appear when you press the Tab key through them:
|4458691 Optionally turning on/off the OAuth protocol is available in Skype for Business Server 2015||After you apply this update, the Skype for Business Server 2015 OAuth (Open Authorization) protocol for server-to-server authentication and authorization can be optionally switched by using PowerShell.
Move-CsUser -Identity “UserAccountName” -Target “RegistrarPool FQDN” – UseOAuth
In this example, the OAuth authentication method is invoked when you move the user account by using the Identity to the Registrar pool. Otherwise, the Skype for Business Server will use the existing legacy authentication.
|4458694 New trusted application endpoints are always assigned to the same routing group in Skype for Business Server 2015||When you create multiple new endpoint contacts one after the another for a trusted application in Microsoft Skype for Business Server 2015, the endpoints will always be assigned to the same routing group against the same Front End Server. If the Front End Server goes down, all the endpoints will go into “reestablishing” state. Then, the Front End Server will be overloaded and meetings will be affected. It’s expected that the endpoints that’re created will be assigned to different routing groups to balance the load.
This issue occurs because the routing group IDs for trusted application endpoints don’t populate correctly.
|4458676 Busy Options settings are removed if you change the Call Forwarding settings with a mobile device or third-party phone device in Skype for Business Server 2015||In a Microsoft Skype for Business Server 2015 environment, consider the following scenario:
In this scenario, you can see the Busy Options settings that you set before are lost.
|4458679 Inactive RGS workflow that has deleted queues can’t be imported by Import-CsRgsConfiguration in Skype for Business Server 2015||In a Skype for Business Server 2015 environment, you can’t run the Import-CsRgsConfiguration cmdlet to import the Response Group configuration data that was previously exported by using the Export-CsRgsConfiguration cmdlet. This issue occurs in the following two scenarios:
When you remove the queues, the workflows that use these queues become inactive and Skype for Business Server can’t find the queues referenced by these inactive workflows. Therefore, the import cmdlet fails.
|4458686 Configuring a watcher node test user fails in the German version of Skype for Business Server 2015||Consider the following scenario:
Set-CsTestUserCredential -SipAddress “sip:firstname.lastname@example.org” -UserName “contoso\user” -Password “<Password>”
In this scenario, you receive an error message that resembles the following:
Set-CsTestUserCredential : Fehler beim Festlegen der Anmeldeinformationen f.r sip:email@example.com. Innere Ausnahme: Microsoft.Rtc.Management.SyntheticTransactions.CredentialManagement.NetworkServiceImpersonator+NetworkServiceImpersonatorException: Fehler beim Annehmen der Identit.t des Netzwerkdienstkontos. Fehlerdetails: Es wurden keine Prozesse im Besitz von ‘NT Authority\Network Service’ gefunden..
|4458684 Local Configuration Store can’t be installed when disabling TLS 1.0/1.1 in Skype for Business Server 2015||When you install the Local Configuration Store by using the Microsoft Skype for Business Server 2015 deployment wizard, the installation fails, and you receive the following error message:
Prerequisite installation failed: Prerequisite installation failed: SqlInstanceRtcLocal For more information, check your SQL Server log files. Log files are in the folder C:\Program Files\Microsoft SQL Server\MSSQL*.RtcLocal\MSSQL\Log, where the * represents your SQL Server version number. For example, SQL Server 2012 uses this path: C:\Program Files\Microsoft SQL Server\MSSQL11.RtcLocal\MSSQL\Log.
In addition, an Event ID 26011 could be logged in the Event Viewer. This issue occurs when you enable the TLS 1.2 and disable the TLS 1.0/1.1 on the operating system.
This issue occurs because the setup installs a version of SQL Express that does not support TLS 1.2.
You have to enable TLS 1.0 and TLS 1.1 on the local computer; uninstall Microsoft SQL Server 2014 (64-bit) through Programs and Features in Control Panel, and then rerun step 1 – Install Local Configuration Store and step 2 – Setup or Remove Skype for Business Server Components. After that, update SQL Server to the version that supports TLS 1.2, and then disable TLS 1.0 and TLS 1.1 again after SQL Server is updated.
|4343061 Event ID 1000 (0xc0000005) and RtcSrv.exe of the SBA/SBS crashes after startup in Skype for Business 2015 and Lync Server 2013||onsider the following scenario:
In this situation, when some users’ presence information is queried, the Lync Server Front-End service (RtcSrv.exe) of the SBAs or SBSs starts but then crashes within about 20 seconds. Additionally, you receive an event that resembles the following:
|4458683 Can’t switch the meeting audio to a UCWA client in Skype for Business Server 2015||In a Microsoft Skype for Business Server 2015 environment, you try to transfer audio to a UCWA client such as Skype for Business for iOS during a meeting. However, the audio transfer fails. It’s expected that the conference including the audio can be switched to the UCWA client in the correct way.
You can rejoin the meeting from the UCWA client.
|4458682 “Failed creating application activity” error when you use the Test-CsUcwaConference cmdlet in Skype for Business Server 2015||In a Microsoft Skype for Business Server 2015 environment, you run the Test-CsUcwaConference cmdlet to verify that a pair of users can schedule, join, and then conduct an online conference by using the Unified Communications Web API (UCWA). You may find the test fails and the outputs return a “Failed creating application activity” error message. For example:
$cred1 = Get-Credential “CONTOSO\User1”
The commands that are shown here test the ability of a pair of users (CONTOSO\User1 and CONTOSO\User2) to participate in a UCWA online conference.
|4458677 Escalation to LBR VoIP user fails when a same site LBR user is in a P2P call with a PSTN user in Skype for Business Server 2015||Consider the following scenario:
In this scenario, you may notice that the user can’t be reached because of conferencing service issues. It’s expected that the user can join the conference without any problem as the escalation happens to the same site’s user only.
|4458693 Can’t join a LBR enabled conference after a user uses the “Call me at” feature in Skype for Business Server 2015||You’re hosted on a LBR (Location-Based Routing) enabled pool of Microsoft Skype for Business Server 2015. When you initial a conference call, if one of the participants joins the call by using the “Call me at” feature for his local meeting room device such as Polycom Trio, the later participants can’t join the conference by using a Skype for Business client. However, they can dial in by using PSTN to join the meeting.
|4458697 Skype for Business Front-End servers connecting to Exchange online for OAuth doesn’t use proxy server||Consider the following scenario:
In this scenario, the user of the account can’t use the feature of server-side conversation history to save the conversation history in the Exchange online mailbox. In addition, the on-premises users won’t be affected.
The issue occurs because the Exchange CAS server is redirecting the Autodiscover request to Exchange Online directly instead of using the proxy server. As the Exchange on-premises servers can’t directly connect to Exchange Online, the connection fails.
In addition, as the on-premises mailboxes are local resource, the Autodiscover process works fine.
|4458692 Incorrect caller ID is shown on the Skype for Business client in a call-forwarding scenario||Consider the following scenario:
In this scenario, you may see the Skype for Business client displays the User C’s caller ID (also known as a Calling Line ID) instead of User B’s caller ID.
This issue occurs because the information about the original caller is lost at the Skype for Business Mediation server.
|4458690 RGS call forwarding to a queue or SIP address not working in Skype for Business Server 2015||In a Microsoft Skype for Business Server 2015 environment, you set the Call Action feature to Forward to another queue or Forward to SIP address for a response group queue. When a user calls this response group (RGS), the call is stuck in the queue until it’s hung up and not forwarded to the queue or SIP address as configured.|
|4464374 Can’t create a Skype meeting on behalf of someone else by using the Outlook for Mac client in Skype for Business Server 2015||In a Microsoft Skype for Business Server 2015 environment, you can’t create a Skype meeting on behalf of a specific user in the Outlook for Mac client. In addition, the Outlook on the web (formerly known as Outlook Web App) client and the Outlook for Windows client aren’t affected.|
|4464375 The Test-CsPhoneBootstrap and Test-CsClientAuth cmdlets not working in Skype for Business Server 2015 that’s installed on Windows Server 2016||You can’t run either the Test-CsPhoneBootstrap or Test-CsClientAuth cmdlet against a particular user’s SIP address in Microsoft Skype for Business Server 2015 that’s installed on Windows Server 2016. For example:
Test-CsClientAuthentication -TargetFqdn <FeFqdn> -UserSipAddress <UserSIP> -UserCredential <UserCred> -Verbose
The cmdlet fails and you may receive an error message that resembles the following:
“Unable to perform authentication of credentials. Inner Exception:ComputeSignature failed.”
|4464372 Skype for Business Server 2015 UCMA services crash on service startup when running on Windows Server 2016||This update fixes the issue that the Microsoft Skype for Business Server 2015 UCMA-based services, such as Skype for Business Server Audio/Video Conferencing Unit (AVMCU), Skype for Business Server Application Sharing (ASMCU), Skype for Business Server Conferencing Auto Attendant (CAA), Mediation Server and so on, may crash on service startup when running on Windows Server 2016. The crash has a call-stack that’s similar to the following:
Second chance exception on worker thread. Thread: 21, Exception: Exception: System.ArgumentOutOfRangeException
|4464371 Support Rate my Call feature for Skype for Business UCWA clients in Skype for Business Server 2015||After you apply this update, Microsoft Skype for Business Server 2015 will enable Skype for Business on Mac clients and Skype for Business mobile clients to use the Rate my Call feature that provides a way for enterprises to achieve feedback from end-users. To get this update, install the January 2019 cumulative update 6.0.9319.537 for Skype for Business Server 2015, Web Components Server and the January 2019 cumulative update 6.0.9319.537 for Skype for Business Server 2015 and Unified Communications Managed API 5.0 Runtime.|
|4458678 Skype for Business VbSS application sharing not working for UCMA based Contact Center in Skype for Business Server 2015||Consider the following scenario:
In this scenario, the desktop sharing fails.
|4458687 “An error occurred during this screen presentation” error occurs in VbSS application sharing conference in Skype for Business Server 2015||In a Microsoft Skype for Business Server 2015 environment, you apply the March 2018 cumulative update for Skype for Business Server 2015 and enable Video-based Screen Sharing (VbSS) in Skype for Business. In this scenario, when you try to share your desktop during a conference, you may receive the following error message:
An error occurred during the screen presentation.
|4470530 Can’t make an outbound PSTN call by using Skype for Business on Mac if LBR is enabled||In a Microsoft Skype for Business Server 2015 environment, you’re located in a network site that’s enabled for Location-Based Routing (LBR). When you make an outbound PSTN call by using a UCWA client such as a Skype for Business on Mac client or a Skype for Business mobile client, the call fails. In addition, the Skype for Business for Windows client isn’t affected.|
|4470531 Support moving users from on-premises to Teams in Skype for Business Server 2015||After you apply this update, Microsoft Skype for Business Server 2015 will support migrating your on-premises users to Teams. To get this update, install the following updates:
|4464373 Can’t escalate a peer-to-peer call to a conference if VbSS is used in screen-sharing in Skype for Business on Mac||In Microsoft Skype for Business Server 2015, when a Skype for Business on Mac client user tries to add a new participant to a peer-to-peer call that has a screen sharing by using the Video-based Screen Sharing (VbSS) feature, you may find the escalation fails and the participant can’t receive the meeting invitation to join the peer-to-peer session.|
7 thoughts on “Skype for Business Server 2015 CU8 January 2019”
Do you get an XDS version mismatch when running Test-CsDatabase – Localservice?
ExpectedVersion : 10.15.5
InstalledVersion : 10.15.4
Hi James, ill check but I think this is known issue ive read somewhere.
After installing this CU update in our environment last month we have an increase of issues with our Mac users (relative small group of users but all seem affected, all using latest skype client version).
They have issues with receiving and sending IM’s (the im was not sent), issues with audio and with calling. This is P2P but in a federated environment. Have you heard anything about this? I cannot find any information online but I cannot pinpoint the problem on our end.
Sorry for the late reply Alex, there is a March CU released but waiting for details on what included. Hope this helps. Thanks Martin
Also introduces a few issues form what we have seen:
SLA – Call Forward takes delegates Call Forward settings
SLA – Unable to forward to PSTN number
If you depend on SLA, postpone! MS states one fix will probably not make it until CU10!
Thanks for sharing the info Jeff. Have you opened a case with Microsoft for this ? There is a March 2019 CU recently released but waiting for details on whats included. Thanks Martin
You called out new Win 2016 support updates around Test-CsBootstrap, I think the command you meant to call out is Test-CsPhoneBootstrap