The Skype for Business Server management experience has introduced some very useful commands and processes. Firstly, the In-Place upgrade process itself, which introduced you to the Smart Setup and the Start-CsPool command, all which on their own reduce the operational loads significantly!
In this post, I will walk you through the simplified process of performing maintenance on your Skype for Business Enterprise Edition Front End Servers.
Now to summarise the overall process, I will let these two images do all the talking, on the left is the Lync Server 2013 Patching Process, on the right the same for Skype for Business Server 2015
Good News – Skype for Business Server 2015 RTM components have been released!!
Bad News for some – VLSC\MSDN Subscription required at the moment 😦
As I haven’t created a walkthrough post yet, I thought there would be no better time to get one on the board and kick off with my experience whilst migrating Lync Server 2013 to Skype for Business Server 2015.
Now an unfortunately a lab demon haunted me (in the form of a Windows Update to Server Technical Preview) on release day (1st May) that completely killed my lab, I did have mirrored databases along with persistent chat and an OWA farm deployed and it would have been interesting to see the Persistent Chat process.
For the purposes of this walkthrough this is what I will be starting off with:
Microsoft released KB on Saturday 2nd May via its FAST PUBLISH process, so clearly there is some urgency behind this patch.
So what’s the issue?
As we know, when migrating from one pool to another, to maintain scheduled conference IDs we leverage the Conference Directory structure (in addition to SQL).
Prior to KB3062801, if administrators leverage the Lync Server 2013 Management Shell to complete the conference directory move to a Skype for Business pool, there is the potential for data to be lost, which will not provide a pleasant experience to your end users.
Friday 1st May was a very good day for the Unified Communications community, particularly if you are pro-Microsoft, as Skype for Business RTM components released to MSDN/VLSC customers. Keep an eye out for a constant steady stream of new information as Microsoft Ignite is also currently underway – so a lot of information will soon be going from NDA to public domain classification – I can already see the blog posts currently in draft mode 😉