That tells us to use the Move-CsManagementServer cmdlet with the “ -TargetFqdn” parameter from a Skype 2015 server. Just like “Enable-CsTopology”, the “Move-CsManagementServer” PowerShell command cannot be run from a Lync 2013 Server, it errors out and this time the log file is quite descriptive about what’s wrong and what needs to be done: There are a few hiccups that I ran into which I will detail below.
Remember this was’nt possible in a Lync 20 co-existence. Bonus : You can move it back to Lync 2013 and still not break a thing. The second and more interesting part(hopefully), is that you can move the CMS from a Lync 2013 to a Skype pool while still keeping your Lync 2013 pools running. Neither does the stack trace on Global Activation in the log file.Īnytime you need to run “Enable-CSTopology”, it has to be from a Skype 2015 server. If you do try it, it throws an error that doesn’t tell you much about why it’s failing: The first thing to note is that in a Lync and Skype co-existence/mixed mode scenario, you cannot modify the topology(via topology builder) or run Enable-CsTopology on any of your Lync 2013 Front Ends. Please note that the information given below applies to Enterprise Edition Front End pools only, while some of the information could be used with Standard edition pools, the procedure will differ significantly.
Other posts that recommend using the migration guidance for Lync 2010 to Lync 2013 ignore that a CMS move may be needed outside of a migration scenario – maintenance, DR, etc. This Technet article here has good details on the prep and procedure but it assumes you’re moving the CMS between Skype 2015 pools. Quite a few articles recommend to reuse the Lync 2010 to Lync 2013 CMS move guidance but I have found that to be a tad bit different. This post stems from part incomplete and part confusing guidance available on moving the Central Management Store(CMS) in an environment that contains both Lync 2013 and Skype for Business 2015 servers.
0 kommentar(er)
