Skype for Business Server 2015 Cumulative update 5 May 2017

There’s a new Skype for Business Server 2015 cumulative update May 2017 which is CU5.

This update notes enables Location-Based Routing to support the Skype for Business mobile clients. This was mentioned on the previous CU4 HF1.

This CU seems a biggy with many many fixes and new stuff as well in it. Took a while to read over them. There’s updates and fixes for lots here

  • Pool Pairing fixes
  • voicemail
  • Busy on Busy
  • In Place upgrade
  • Allows move a meeting room object from a Microsoft Skype for Business Server 2015 on-premises environment to Microsoft Skype for Business Online

What i cant see and i was looking for is SfB Server support on Windows Server 2016. I check the Supported OS list here and i cant see support yet here

Update 19/05/2017 – Thanks to @tobiefysh on twitter he spotted Window Server 2016 is supported with CU5 or later now

https://support.microsoft.com/en-gb/help/4015888/supports-to-use-windows-2016-as-the-operating-system-in-skype-for

We may just have to wait a little longer.doh!

*** Update*** 19th May -  I found this link on Microsoft Tech Community that notes in the comments  CU5 does not support Windows Server 2016. There some great information on whats new though check it out here

In addition to various bug fixes, several new features are included in this update.

From Microsoft Tech Community – What’s New: 

1. Enable Delegate Management in UCWA (Unified Communication Web API)

2. UCWA scopes based authorization supported for onprem

3. CORS (Cross Origin) supported for onprem

4. JoinLauncher: Port Modern Meeting Join Experience to W16

5. Fix move-csmeetingroom cmdlet for onprem->online move

6. Supporting CallerID policy for hybrid tenants

7. Create New-CsOnPremApplicationEndpoint commandlet (Intune)

Modern Meeting Join Experience

For the JoinLauncher: Port Modern Meeting Join Experience to W16 i thought they might have brought the new Office 365 Meeting Join experience to on premises.

But after installing CU5 i still got the old meeting join page Sad smile tried a restart but the same. Seems we still need to wait for this to come on premises.

Capture

But i managed to work out you need to enable the new meeting experience following CU5 installation ! Check this blog post out here Smile

image

More details on the new SkypeMeetingApp with CU5 in my blog post for enabling from here

Starting with CU5, Skype Meetings App is available as a replacement for Skype for Business Web App. Skype Meetings App offers a simplified browser experience for downloading and installing the app and joining meetings, including one-click join for users of Internet Explorer. Skype Meetings App also has many improvements over the Skype for Business Web App for reliability and the meeting experience.

If Skype Meetings App is enabled, users will download the latest version of the app from the online Content Delivery Network (CDN) rather than from your Skype for Business server.

Skype for Business Server 2015 works with the Skype for Business Web App by default. The Skype for Business Web App is stored on the Front End Server and gets sent to the meeting attendee.

As of Skype for Business Server 2015 CU5 or later, meetings held using Skype for Business Online will no longer send a clientless user the Skype for Business Web App, they will instead be sent Skype Meetings App. As of Skype for Business Server 2015 CU5 or later, if you Enable the simplified meeting join experience and Skype Meetings App, clientless users will be sent Skype Meetings App instead of Skype for Business Web App.

Version Number for this update – 9319.281

Lets dig into some details.

Skype for Business Server CU5 details

Man there’s alot of issues ! This update enables Location-Based Routing to support the Skype for Business mobile clients. It also fixes the following issues

Improvements and fixes in the May 2017 update
Fix and Improvement Symptom / Cause
  • 4020997 Skype for Business Server 2015 Front-End service may crash in Windows Server 2016
When you configure multiple Microsoft Skype For Business Front-End pools on computers that are running Windows Server 2016, the Skype For Business Server Front-End service (RTCSrv.exe process) may be unable to start and crash in crypt32.dll.

This issue occurs because the certificate chain of a certificate that’s used by a Front-End server in a different pool cannot be validated.

  • 4020994 Event ID 36023 is consistently logged on Multiple Front-End servers in a Skype for Business Server 2015 environment that enables CAC

When this issue occurs, the Bandwidth Policy Service event ID 36023 is logged on front-end servers every few minutes.

Note When this issue occurs, there is no actual function effect in Skype for Business Server 2015.

This issue occurs because the delay in call admission control (CAC) verifications for Inter-Cluster mode is set incorrectly.

  • 4020993 DTMF tone isn’t played when some DTMF packets are dropped in the network in Skype for Business Server 2015

Consider the following scenario:

  • You deploy a dual tone multi-frequency (DTMF) based Interactive Voice Response (IVR) application in a Microsoft Skype for Business Server 2015 environment.
  • The application is developed by using Unified Communications Managed API.
  • The application joins a conference.
  • A user connects to the application, and then the user starts pressing DTMF digits.

In this scenario, the DTMF tone is missing.

This issue occurs because the Audio Video Multipoint Conferencing Unit (AVMCU) does not process the DTMF tone when the DTMF packets that carry the end of tone flag are dropped in the network.

  • 4020991 Enables “move-csmeetingroom” cmdlet to move meeting room from on-premises to Online in Skype for Business Server 2015
The update supports administrators to move a meeting room object from a Microsoft Skype for Business Server 2015 on-premises environment to Microsoft Skype for Business Online in Microsoft Office 365 by running the Move-CsMeetingRoom cmdlet.
  • 4020987 The update to OcsMcu.msp can’t be applied when conferencing is disabled in Skype for Business Server 2015
Assume that you have a topology where conferencing is disabled. This means that ASMCU and AVMCU should not be installed. When you try to apply patches to Microsoft Skype for Business Server 2015, you find OcsMcu.msp is not able to be installed.

This issue occurs because OcsMcu.msp tries to find the RTCASMCU and RTCAVMCU services that aren’t present because conferencing is disabled on the topology.

  • 4020984 The ms-client-diagnostics header for application sharing scenario is not correctly formatted in Skype for Business Server 2015
The ms-client-diagnostics header that’s used to troubleshoot application sharing issue is not correctly formatted.

This issue occurs because the incorrect type is put in the MediaType filed in a diagnostic blob that is added to the ms-client-diagnostic.

  • 4020983 “sorry, I didn’t get that…” GVA announcement is triggered by external audio sources in Skype for Business Server 2015
When you have a Microsoft Skype for Business conference call ongoing in a Microsoft Skype for Business Server 2015 environment, participants in the conference call occasionally hear the following Group Virtual Assistant (GVA) announcement:

The GVA announcement is triggered by external audio sources that sound like a dual tone multi-frequency (DTMF) tone.

Note The external audio sources that are identified are as follows:

  • A Windows notification sound that’s confirmed to technically resemble the audio wave of the * DTMF tone.
  • DTMF tones that are played by other phones in speaker mode nearby an audio device that’s connected to a meeting.

  • 4019726 Call remains ringing on a PSTN phone when you click End Meeting in a Skype meeting in Skype for Business Server 2015

Consider the following scenario:

  • You join a Skype meeting in a Microsoft Skype for Business Server 2015 environment.
  • You invite a Public Switched Telephone Network (PSTN) number to the meeting.
  • You click the End Meeting button before the PSTN callee takes the call.

In this scenario, the call continues to ring on the PSTN phone.

This issue occurs because the Audio Video Multipoint Conferencing Unit (AVMCU) cannot send the Cancel request to the Mediation Server.

  • 4019725 Event ID 44005 and 44008 are logged when you try to leave a voicemail in Skype for Business Server 2015
You can’t leave a voicemail until the Skype for Business Front-End service gets restarted in a Microsoft Skype for Business Server 2015 environment.

This issue occurs because the Skype for Business Front-End service cannot connect to Domain Controller to read dial plan records.

  • 4019724 You cannot join Skype meeting after you perform a pool failover in Skype for Business Server 2015

Consider the following scenario:

  • You deploy two paired Front-End pools in a Microsoft Skype for Business Server 2015 environment.
  • You perform a pool failover to fail over to the backup pool.
  • A user creates a Skype meeting.
  • You perform a pool failover to fail back to the primary pool.
  • You join the meeting that’s created by the user.

In this scenario, you can’t join the Skype meeting.

This issue occurs because the conference data is inconsistent between the primary pool and the backup pool.

  • 4019723 Agents in a Response Group can’t receive call after you invoke pool failover in Skype for Business Server 2015

Consider the following scenario:

  • You deploy two paired Front-End pools in a Microsoft Skype for Business Server 2015 environment.
  • You deploy Response Group Service (RGS) in the environment.
  • You perform a pool failover by running the Invoke-csPoolFailover cmdlet between the two paired Front-End pools.
  • After the pool failover, you run the Import-CsRgsConfiguration cmdlet to import the Workflows, Queue and Agents to the paired pool.
  • You make a call to a Response Group.

In this scenario, the agents in the Response Group can’t receive the call.

This issue occurs because the value of the EnterpriseVoiceEnabled parameter isn’t set to True when you run the Import-CsRgsConfiguration cmdlet on the backup pool.

  • 4019722 Event ID 30210 occurs when you try to leave voicemail in Skype for Business Server 2015

You cannot leave a voice mail message until the Skype for Business Front-End service is restarted in a Microsoft Skype for Business Server 2015 environment. Additionally, the following event is logged on the Microsoft Skype for Business 2015 Front End server.

Time: Date/Time
ID: 30210
Level: Warning
Source: LS Applications Module
Machine: SERVER Name
Message: Lync Server application is not responding and is being disconnected.

Application Uri ‘http://www.microsoft.com/LCS/ExumRouting‘ Cause: This can occur if the managed application is slow to respond to messages or if the server is under heavy load or the application has become unresponsive.
Resolution:
If the server load is too heavy, consider getting a faster machine or hosting fewer users on the server. If the application is slow, contact the author of the application.

This issue occurs because the ExUMRouting application is uninstalled from the TrustedServerList.

  • 4015911 Pool failover fails when you have many conference directories in Skype for Business Server 2015

Consider the following scenario:

• You deploy two paired Front-End pools in a Microsoft Skype for Business Server 2015 environment.

• You create many conference directories.

• You start pool failover between the two paired Front-End pools.

• There are many meetings being scheduled during the pool failover.

In this scenario, the pool failover fails.

This issue occurs because a back-end SQL stored procedure takes more than one minute to sync the change of the conference directories.

  • 4015910 Event ID 53106 "Unable to Save Message" occurs in Skype for Business Server 2015 Persistent Chat Server

When you configure the Persistent Chat Compliance service in a Microsoft Skype for Business Server 2015 multiple-server pool environment, the following event is logged on the Skype for Business Server 2015, Persistent Chat server.

Time: Date/Time
ID: 53106
Level: Error
Source: LS Persistent Chat Compliance Server
Machine: SERVER Name
Message: Unable to save message Date/Time PART ma-chan://domain.com/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX X XXXXX to database due to exception:
CmdID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX The server could not restore db connection within the allowed time (00:10:00) using connection string: Data Source=SERVER.domain.com\PCHATDB; Initial Catalog=mgccomp; Integrated Security=SSPI. at
at Microsoft.Rtc.Internal.Chat.Server.ServerCommon.Database.DbCommand.executeUntilSuccessOrTimeout[TR](Fun`2 executeDelegate, RetryInfo retryInfo)
at Microsoft.Rtc.Internal.Chat.Server.ServerCommon.Database.DbCommand.executeImp[TR](Fun`2 executeDelegate, Int32 retryTimeoutInMs)
at Microsoft.Rtc.Internal.Chat.Server.ServerCommon.Database.DbCommand.ExecuteNonQuery(Int32 retryTimeoutInMs)
at Microsoft.Rtc.Internal.Chat.Server.Compliance.ComplianceDataAccess.Save(RawComplianceData data)
at Microsoft.Rtc.Internal.Chat.Server.Compliance.ComplianceServer.Save(RawComplianceData data).

This issue occurs because of a race condition when you update tblComplianceParticipant table entries.

  • 4015907 Update that enables simplified meeting join experience in Skype for Business Server 2015

This update enables the simplified meeting join experience and Skype Meetings App in Microsoft Skype for Business Server 2015.

For more information, refer to the following links:

  • 4015904 Enables UCWA to populate "OTHER CONTACTS" and "FAVORITES" groups at first sign in to Skype for Business mobile app
This update enables Unified Communications Web API (UCWA) to auto populate the OTHER CONTACTS and FAVORITES default groups when you sign in to a Microsoft Skype for Business mobile client for the first time in a Microsoft Skype for Business Server 2015 environment.
  • 4015902 Failed to start MatchMaking service and its dependencies if FIPS for RGS is enabled in Skype for Business Server 2015

This issue occurs when Federal Information Processing Standards (FIPS) for Response Group Service (RGS) is enabled in a Microsoft Skype for Business Server 2015 environment.

Additionally, when you establish application endpoints, you may see the following exception:

sip:RtcApplication-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX@domain.com
sip:RtcApplication- XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX@domain.com
sip:RtcApplication- XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX@domain.com
Exception: System.Reflection.TargetInvocationException – System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
at System.Security.Cryptography.SHA512Managed..ctor()
— End of inner exception stack trace —

at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Security.Cryptography.CryptoConfig.CreateFromName(String name, Object[] args)
at System.Security.Cryptography.SHA512.Create()
at Microsoft.Rtc.Acd.Common.ConsistentHash`2..ctor(Func`2 nodeToHashKeyConverter, Func`2 requestToHashKeyConverter, Int32 virtualNodesMultiplier)
at Microsoft.Rtc.Acd.MatchMaking.PresenceProvider.PresenceComponent.Initialize(IReadOnlyCollection`1 presenceEndpoints, Int32 maxRgsAgentsPerPresenceWatcher)
at Microsoft.Rtc.Acd.MatchMaking.MatchMakingService.Start(IReadOnlyCollection`1 presenceEndpoints)
at Microsoft.Rtc.Acd.AepManager.StartMMAndItsDependencies(IReadOnlyCollection`1 presenceEndpoints)
Cause: Failed to connect to Front End server or the Front End server is misconfigured.
Resolution: Check the Front End server for errors.

This issue occurs because the MD5 and SHA512Managed classes don’t have FIPS enabled.
  • 4015901 Calls to RGS may fail after an in-place upgrade from Lync server 2013 to Skype for Business Server 2015
The Response Group Service (RGS) service fails to start after an in-place upgrade from Microsoft Lync Server 2013 to Microsoft Skype for Business Server 2015 when you apply the May 2017 cumulative update 6.0.9319.281 in certain situations.

In Skype for Business Server 2015, the default design is changed to use three Presence Watcher contact objects (instead of one Presence Watcher contact object in earlier versions). The service startup failure is introduced to prevent an issue in which the service has started, but calls to RGS fail with "500 Internal Server error", because only one Presence Watcher contact object is found after the start of the RGS service.

  • 4015900 Enables “VoicemailOnBusy” ActionType to be set for Exchange Online users in Skype for Business Server 2015 Busy Options

Consider the following scenario:

  • You have enabled Busy Options feature in a Microsoft Skype for Business Server 2015 environment that has Cumulative Update 2 (Version 6.0.9319.235) or later versions installed.
  • You enable a user for Microsoft Exchange Unified Messaging (UM) On-Premises.
  • You move the user’s mailbox to Exchange Online.
  • You enable the user for Exchange UM Online by assigning on-premises hosted voice mail policy.
    Note The on-premises attributes for this user are now set as follows:
    • ExUmEnabled=False
    • HostedVoiceMail=True

In this scenario, you can’t set the BusyOnBusy option to an ActionType of VoicemailOnBusy for this user.

Additionally, you receive the following error message:

PS C:\Users\SfBadmin> Set-CsBusyOptions -Identity "Ken Myer" -ActionType VoicemailOnBusy
Set-CsBusyOptions : Voicemail is not enabled for Identity "Ken Myer".
At line:1 char:1
+ Set-CsBusyOptions "Ken Myer" -ActionType VoicemailOnBusy
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Set-CsBusyOptions], BobException
+ FullyQualifiedErrorId : Microsoft.Rtc.Management.Bob.Cmdlets.BobSetConfigurationCmdlet

This issue occurs because the VoicemailOnBusy action type was designed to support only on-premises Exchange UM deployments.

  • 4015899 "Busy Options" feature doesn’t check the second incoming call in Skype for Business Server 2015

Consider the following scenario:

  • You have enabled Busy Options feature for internal Skype for Business users in a Microsoft Skype for Business Server 2015 environment.
  • You have the following restriction in your manifest file:
    domainSupported="true"
  • You are in a call with another federated user.
  • A user is trying to call you.

In this scenario, you find double toast notifications.

This issue occurs because calls to federated users are not tracked by Busy Options when the domainSupported parameter is set to true.

  • 4015898 RGS agents may stop receiving calls after you run the “Enable-CsTopology” cmdlet in Skype for Business Server 2015
Assume that you enable response group service (RGS) in a Microsoft Skype for Business Server 2015 environment. When you run the Enable-CsTopology cmdlet to have the changes published, some RGS agents can’t receive toast notifications even their presence status is available.

This issue occurs because the presence watcher is reset when the Enable-CsTopology cmdlet is invoked.

  • 4015893 Enables delegate management feature for Unified Communications Web API in Skype for Business Server 2015
This update let you enable the delegate management feature for Unified Communications Web API (UCWA) that’s based on Microsoft Skype for Business Server 2015.

To get this update, install the May 2017 cumulative update 6.0.9319.281 for Skype for Business Server 2015, core components.

Note After you install this update, run the following Skype for Business management PowerShell command to enable the feature:

‘Set-CsPlatformServiceSettings –EnableDelegateManagement $true’

Restart Required

Seems after CU5 its best to restart as the new cmdlets for enabling the new Meeting UX may not display. More great information on this on Randys blog below. check it out.

http://lynciverse.blogspot.co.uk/2017/05/restart-required-after-skype-for.html

There seems to be quite a few components are require updating

image

Databases

Seems like one DB update on rtcxds

DatabaseName  ExpectedVersion InstalledVersion
rtcxds 15.13.11 15.13.10
rtcshared 5.0.1 5.0.1
rtcab 62.42.12 62.42.12
rgsconfig 5.5.1 5.5.1
rgsdyn 2.2.1 2.2.1
cpsdyn 1.1.2 1.1.2
xds 10.15.4 10.15.4
lis 3.1.1 3.1.1
mgc 1.42.1 1.42.1

Download Link

https://www.microsoft.com/en-us/download/details.aspx?id=47690

References

https://support.microsoft.com/en-us/help/3061064/updates-for-skype-for-business-server-2015

https://techcommunity.microsoft.com/t5/Skype-for-Business-Blog/Announcing-the-release-of-Skype-for-Business-Server-Cumulative/ba-p/70921?utm_source=Direct

http://tomtalks.uk/2017/05/improved-skype-business-web-join-experience-skypemeetingsapp-msi/

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s