

I actually havent tried using a SfB Edge 2019 with a older pool but I am going to perform an upgrade this weekend of a SfB Edge 2015 to 2019 and will report back as to whether the SfB FE 2015 can use it. I’m not sure if this is the behaviour when performing an in-place upgrade to Skype for Business, but assuming it is. Skype for Business Server 2015 supports an in-place upgrade from Lync Server 2013. Installing Skype For Business Server 2019 Front-End Server. I couldn’t see it in the migration documents (nor thought I should look for it!) but the Microsoft planning document for Skype for Business Server 2015 states very clearly vaguely that “ When you migrate response groups from a prior version to Skype for Business Server, the type is set to Unmanaged.” I thought it was a bug, but no – it’s by design. I thought it was just a misconfiguration but then I checked the “Get-CsRgsWorkflow” export we did earlier (Never underestimate documenting!) and all workflows that were set to “ Managed: True” are now set to “ Managed: False“. 2 Comments on Microsoft Announces Skype for Business Server 2019 It’s day 2 at Microsoft Ignite Orlando, and we’ve had the announcement many of us in the industry have been waiting for: Skype for Business Server 2019 will be released towards the end of 2018. Opening the Workflow – I can’t see the managers and the workflow is set to “Unmanaged”. In LyncSkype for Business Server, Microsoft Teams. The next week I’m getting a phone call saying the Response Groups’ managers can’t change some of the settings they used to be able to. We tested and confirmed that calls are coming through and the response groups are all working as expected – that was easy. Lync Server 2013 (Server 2008 r2) Skype for Business 2015 (Server 2016) Edge Server (2008 r2) My question is in regards to the Edge server. In summary you stand up your new SfB servers and add these to your existing Topology.


I was double-checking my self against Greig Sheridan‘s very detailed guide and as expected, everything worked just fine. The migration method is the same as Lync 2010 to Lync 2013 so there should be plenty of documentation available. Noticed something weird during a recent upgrade to from Lync Server 2013 to a new Skype for Business Server pool.
