Noticed this morning on twitter from @uclobby there’s been a hotfix for December 2017 CU seems the Jan 2018 is CU6 HF1 . This cumulative update replaces the December 2017 cumulative update 6.0.9319.510 for Skype for Business Server 2015, Front End Server and Edge Server.
Seems to get your paws on this you need to open a support ticket! perhaps its not fully tested for GA yet.
It notes this is an CU hotfix it seems for the Front End and Edge Servers roles.
This cumulative update fixes some issues that occur in Microsoft Skype for Business Server 2015, Front End Server and Edge Server. The version number of this update is 6.0.9319.514
Update Version is now 6.0.9319.514
Whats the fixes and improvements ?
The first link i found only had 3 fixes two for LBR and one for Caller ID for Phone System if using Phone System via on premises deployment.
BUT
then i found another link and theres a ton of stuff it seems !!!
- Fixes for deployments
- Mac client fix for joining meetings
- Support for new-CsCallingLineIdentity for SfB Hybrid
- and more !! check it out below
MAC Users
For Mac users theres some updates as well
-
Support for location-based routing of phone calls
Your administrator can control how calls to or from people outside of your organization are handled based on the location of the parties in the call.
-
Display IM disclaimers
Skype for Business on Mac will display a disclaimer message at the beginning of every IM conversation if your organization specifies them.
Microsoft Advices for this CU seems to be below:
Microsoft recommends that you install this update only if you need these features or experience any of the issues described in the "Improvements and fixes" list for the release. When the update is installed, users of Skype for Business on Mac will see the following improvements:
How to get update ? – THIS SEEMS TRICKY FOR SOME REASON !
Seems at the moment you have to request this update from Microsoft. Perhaps its early days and it seems to provide fixes only for specific situations for LBR or Caller ID for Phone System (Cloud PBX) with On premises PSTN connectivity .
To obtain this update, submit a request to Microsoft Customer Service and Support through the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Ive tried but it seems i have to pay to get hold of it. Perhaps its not fully ready yet.
Full details on Fixes
This cumulative update fixes the following issues:
Fixes | Cause and Fix |
Found these 3 here | https://support.microsoft.com/en-us/help/4074701/january-2018-cumulative-update-6-0-9319-514-for-skype-for-business |
Assume that you are Location-Based Routing (LBR) enabled on a LBR enabled network site in Microsoft Skype for Business Server 2015. Then, you start a public switched telephone network (PSTN) call. When you right-click and then select the Skype Calloption to add a non-LBR enabled user from a Skype for Business mobile client, the user is added to the PSTN call successfully. However, the user should not be added to the PSTN call successfully because the call is from a LBR enabled gateway.
To fix this issue, install the January 2018 cumulative update 6.0.9319.514 for Skype for Business Server 2015, Front End Server and Edge Server. |
|
Assume that you are Location-Based Routing (LBR) enabled on an LBR enabled network site in Microsoft Skype for Business Server 2015. Then you start a call with a public switched telephone network (PSTN) user. When you try to transfer the PSTN call to another user who is only Enterprise Voice (EV) enabled on a non-LBR enabled network site, the PSTN call can be transferred successfully. When the non-LBR user isn’t available, the call will be routed to his voicemail. The call transfer should be failed because the call is from an LBR enabled gateway.
To fix this issue, install the January 2018 cumulative update 6.0.9319.514 for Skype for Business Server 2015, Front End Server and Edge Server. |
|
In a Microsoft Skype for Business Server hybrid deployment with on-premises Public Switched Telephone Network (PSTN) connectivity, when a Microsoft Skype for Business Online user makes an outgoing PSTN call, the on-premises trunk translation rules take precedence over the user’s line URI in the following scenario in Skype for Business Server 2015:
For all other scenarios, no overrides occur, and the caller ID would be defined by CallerIDSubstitue.
To apply this update, install the January 2018 cumulative update 6.0.9319.514 for Skype for Business Server 2015, Front End Server and Edge Server. |
|
FOUND THESE ADDITIONAL on | https://support.microsoft.com/en-us/help/3061064/updates-for-skype-for-business-server-2015 |
|
When a user tries to join a Skype meeting with Skype for Business on Mac by clicking the meeting link in Outlook, the Skype meeting can’t be joined.
When Skype for Business on Mac tries to join a meeting, the client passes the meeting URL to Unified Communications Web API (UCWA). In some cases, there can be additional parameters in the URL that are not recognized by Skype for Business Server. Therefore, the meeting can’t be joined. |
|
Consider the following scenario:
In this scenario, you can only hear the ringtone when picking up the call. Unified Communications Web API (UCWA) doesn’t work correctly for this scenario. |
|
This update enables you to use the New-CsCallingLineIdentity cmdlet to create a new Caller ID policy in a hybrid environment of Microsoft Skype for Business Server 2015. You can either change or block the Caller ID (also known as a Calling Line ID) for a user. By default, the Skype for Business user’s phone number can be seen when the user makes a call to a PSTN phone, or when a call comes in. You can create a Caller ID policy to provide an alternative displayed number, or to block any number from being displayed. |
|
A user can’t join a Skype meeting after you run the following cmdlet in PowerShell in a Microsoft Skype for Business Server 2015 environment.
|
|
Assume that you try to remove Microsoft Skype for Business Server 2015 or run the bootstrapper.exe /scorch command in a Skype for Business Server 2015 environment. Then a NullReferenceException occurs and the uninstallation fails together with the following call stack: at Microsoft.Rtc.Management.Deployment.Roles.WebServices.ConfigIISAppWindowsAuth() server.vdomain.com(server.vdomain.com): at Microsoft.Rtc.Management.Deployment.Roles.WebServices.LocalDeactivate(IService service, Fqdn fqdn, Boolean complete) server.vdomain.com(server.vdomain.com): at Microsoft.Rtc.Management.Internal.Utilities.LogWriter.InvokeAndLog[T1,T2,T3](Action`3 action, T1 arg1, T2 arg2, T3 arg3) server.vdomain.com(server.vdomain.com): at Microsoft.Rtc.Management.Common.Reporting.LogWriterImpl.InvokeAndLog[T1,T2,T3](Action`3 action, T1 arg1, T2 arg2, T3 arg3) server.vdomain.com(server.vdomain.com): at Microsoft.Rtc.Management.Deployment.Tasks.HostLocalDeactivateTask.Action() server.vdomain.com(server.vdomain.com): at Microsoft.Rtc.Management.Internal.Utilities.LogWriter.InvokeAndLog(Action action) server.vdomain.com(server.vdomain.com): at Microsoft.Rtc.Management.Common.Reporting.LogWriterImpl.InvokeAndLog(Action action) server.vdomain.com(server.vdomain.com): at Microsoft.Rtc.Management.Deployment.DeactivateMachineCmdlet.InternalProcessRecord() server.vdomain.com(server.vdomain.com): at Microsoft.Rtc.Management.Deployment.DeploymentCmdlet.CmdletProcessRecord() server.vdomain.com(server.vdomain.com): — End of inner exception stack trace — server.vdomain.com(server.vdomain.com): at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input) server.vdomain.com(server.vdomain.com): at Microsoft.Rtc.Internal.Tools.Deploy.Tools.PowerShellRunner.RunCmd(String script, Collection`1& errors) server.vdomain.com(server.vdomain.com): at Microsoft.Rtc.Internal.Tools.Deploy.Tools.PowerShellRunner.RunCmd(String script) server.vdomain.com(server.vdomain.com): at Microsoft.Rtc.Internal.Tools.Deploy.Tools.InPlaceDeploymentSteps.PrepareForUpgrade(Object param) server.vdomain.com(server.vdomain.com): at Microsoft.Rtc.Internal.Tools.Deploy.ViewModels.DeploymentStepViewModel.Action(Object param) server.vdomain.com(server.vdomain.com): at Microsoft.Rtc.Internal.Tools.Deploy.Commands.RunDeploymentCommand.RunSteps(Object obj) SkypeServerUpdateInstaller.exe Error: 0 : server.vdomain.com(server.vdomain.com): System.Exception: Installation failed with code 10 Note This issue occurs after you apply December 2017 cumulative update 6.0.9319.510. |
|
Assume that the encryption for Skype for Business Server 2015 is disabled. When you try to join an Audio Video Multipoint Conferencing Unit (AVMCU) meeting, you may experience a delay or a failure.
Removing a muted user with disabled encryption can introduce the delay or failure in the AVMCU. |
|
Assume that you have a Unified Communications Managed API (UCMA) application that sends a dial-out request to the Audio Video Multipoint Conferencing Unit (AVMCU) in Microsoft Skype for Business Server 2015. Then the dial-out goes to a UCMA back-to-back (B2B) application, and is finally sent to a Skype for Business user. When you try to add a video to the dial-out conference, the video can’t be added by the B2B application.
The escalation, which is from an audio to video conference, fails because the addEndpointMedia level achieves an incorrect state from MediaUASession. |
|
Assume that you run step 2 (Install or Update Skype for Business Server System > Setup or Remove Skype for Business Server Components) in Microsoft Skype for Business Server 2015 Deployment Wizard in Windows Server 2012 R2. You may find the Deployment Wizard can’t check the prerequisite of KB2982006. Prerequisite not satisfied: Before you install Skype for Business Server 2015, you must Install an update for Windows Server 2012 R2. For details about the update, see Microsoft Knowledge Base article 2982006, "IIS crashes occasionally when a request is sent to a default document in Windows 8.1 or Windows Server 2012 R2" at http://go.microsoft.com/fwlink/?LinkId=519376." This issue occurs because the WMI query result of the prerequisite of KB2982006 isn’t reliable. |
Install Pre reqs!
To apply this update, you must have Microsoft .NET Framework 4.5.2 (Offline Installer or Web Installer) installed.
When i get the update ill post more !
References
https://support.microsoft.com/en-us/help/3061064/updates-for-skype-for-business-server-2015
More information is here
What’s new in Skype for Business?