Make sure it is available in an emergency – it is your get-out-of-jail card in the event things go horribly wrong. Take that file and store it outside of your Lync/Skype4B servers. *shakes head*…īefore you make a single change in your environment, back up the CMS data using the built-in Management Shell cmdlets: Export-CsConfiguration -Filename 'D:\temp\20160112.zip' -Verbose
You’ve already got this data backed up right? The ZIP file stored safely away on a location for a rainy day? What’s that…you say you back up the databases using T-SQL?…. Hopefully the information presented will help you move CMS in the most pain-free and seamless way possible! Step 1 – Backup CMS Data Use this information only if you are going between non-paired pools within the same server version (2013 to 2013, for example) or if you are moving CMS from one server version to another (2010 to 2013, for example). Please note that the following information does not apply if you are moving CMS between pools that are already paired. In one way or another, each post has information missing that can leave you scratching your head at why CMS doesn’t seem to replicate anymore and send you into a frantic troubleshooting frenzy. If you perform a quick web search you’ll find loads of additional results as well, but I can speak from experience that not all steps are accounted for in all of the documentation. Move the Lync Server 2010 Central Management Server to Lync Server 2013 To be truthful, yes, Microsoft does have Technet documentation for moving the Central Management Store: I know…I know…you’ll look at the title and say “bah humbug – Microsoft has that documented already… SQUIRREL!“.