Blog Post

Skype for Business Blog
2 MIN READ

Released: Skype for Business Server 2019 CU1!

Rohit_Gupta_25's avatar
Jul 24, 2019

Earlier this month, we released the much awaited first Cumulative Update for Skype for Business Server!  Please find the update here. We’ve been hard at work to ensure adherence to the high levels of stability that you expect from us. Now that CU1 (July 2019) has been released, we hope you’ll give it a try. Besides several bug fixes, this update also contains some of the features that you may have seen us talking about at our presentation in Ignite 2018.

 

The most notable feature is a React-based, Silverlight-less version of the Server Control Panel. If you’ve been working with the Skype for Business Server for some time, there most likely have been moments where you’ve wished the Control Panel was more modern, more sleek, and more reliable. With the first phase of the Control Panel included in this update, we’ve taken the first step towards improving the Control Panel experience. Please find more information about the Control Panel here. As always, we’re happy to get feedback on the Panel as we work on the next phase.

 

The next feature is also one that the Skype for Business community has been requesting for a while now – SEFAUtil cmdlets in PowerShell! We’re certain that this tool needs no introduction. We’ve gone ahead and built the SEFAUtil functionality directly into standard cmdlets that you can run from the PowerShell console. Please find more information about the cmdlets here.

 

Last but not the least, we’ve also built-in the ability to include RGS data in the standard Server backup feature. You will no longer have to manually export and import RGS data to back it up! Please find more information on this here.

 

In conclusion, we’d like to assure you that the Skype for Business Server product team is fully committed to supporting the product, and we’d love to keep getting feedback so we know which improvements to prioritize in order to improve the community’s experience with the Server. So, please keep the feedback coming!

 

On behalf of the product team,

Rohit Gupta

Program Manager, Skype for Business Server

Updated Jul 24, 2019
Version 2.0
  • Brady2020's avatar
    Brady2020
    Copper Contributor

    Hi Team,

     

    We recently upgraded from Lync 2013 to Skype for Business 2019 Server CU3.

    We have a requirement to redirect calls that are unanswered back to reception after 15 seconds.

    Previously, I used SEFAUtil in a powershell script to achieve this, so I was excited to try the new SEFAUtil commands in Powershell.

     

    Unfortunately, I discovered a bug using the -UnansweredToOther switch in the "Set-CsUserCallForwardingSettings" command.

    It appears to work (the output looks correct) but when testing it doesn't recognize the setting and rings out.

    It works if I manually make this setting on the Skype for Business client which is not feasible with 600+ users.

     

    This same bug is highlighted in this link - https://www.myteamslab.com/2019/08/skype-for-business-2019-call-forward.html

     

     

     

     

     

     

     

    Are there any plans to fix this bug in the next CU?

     

  • TimLB's avatar
    TimLB
    Steel Contributor

    SEFAUtil in Powershell!!! Woo! Time to merge up scripts

  • Great feature additions thanks!

  • Unfortunately have encountered this UCMA bug during a contact centre migration to Skype for Business Server 2019 with CU1:

    ----

    The Audio/Video Conferencing Server has failed to create a conference. Conference URI:

    sip:announceportX@contoso.com;gruu;opaque=app:conf:focus:id:ay6yytcw Exception: Media Processor instance is not available to service this request

     

    Resolution: Check that the administrator policy allows the creation of audio/video conferences.

    ----

    https://support.microsoft.com/lo-la/help/4503584/the-audio-video-conferencing-server-has-failed-to-create-a-conference

     

    We have had to re-deploy a 2015 front-end on the July 2018 CU to work around the issue.