Moving Central Management Server from Lync 2010 to Lync 2013 Front End

Howdy all,

so I decided to upgrade my Lync Server 2010 to Lync 2013 that I have now deployed Exchange 2013.

Updated: 20-10-2014

so my lab now have Lync 2010 up and running where the CMS is hosted, and a Lync 2013 also up and running (co-existence), an overview of the steps are

  • install Central management store database on the server
  • migrate CMS from 2010 to 2013
  • remove the old CMS database

Install Central Management Database

using Lync Management Shell on the Lync 2013 server run the following

C:\> Install-CsDatabase -CentralManagementDatabase -SQLServerFQDN “Front End FQDN”

or in case it is hosted on a dedicated SQL Backend (Enterprise Edition Deployment), make sure to put the “SQL backend Server FQDN” and Instance name in case you have multiple instance running on the machine

C:\> Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn “SQL Server” -SqlInstanceName “Instance name you created for Lync”

2

Move the CS database to the new created one.

  • once complete now we need to publish the topology
  • Run the following command line

C:\> Enable-CsTopology

3

  • Now the big Move, Moving the CS database from Lync 2010 FE to Lync 2013 FE, use the following command line

C:\>  Move-CsManagementServer4

  • it will give you a lovely warning “this cmdlet moves Central Management server to the pool that contain this computer”, just select “Yes”.
  • Now on Each Frontend 2013 and 2010 server in your Topology run the Installation Wizard
  • Start the step “Install or Update Lync Server System”
  • run step-2 “Setup or Remove Lync Server Components” on Each server.

52

  • Click on “Setup or Remove Lync Server Components”.

54

  • Once finished click “Finish”.

Remove the old CS database from 2010 FE server

DO NOT CARRY THIS STEP UNLESS YOU MADE SURE REPLICATION IS DONE AND HEALTHY

  • Make sure that replication with the new Central Management store is occurring and healthy by using the following cmdlet

 

C:\> Get-CsManagementStoreReplicationStatus

Now go to the old Lync Server 2010 Front End Server.

  • Start “Lync Server 2010 Deployment Wizard”
  • now we do the same as last steps click on “Setup or Remove Lync Server Component”
  • Click Next
  • Once done click Finish.
  • once you are sure that replication is healthy we need to run one more command line on Lync 2010 Front End server to uninstall the CS database.

C:\> Uninstall-CsDatabase -CentralManagementDatabase –SqlServerFqdn “FQDN of old CMS server” -SqlInstanceName RTC

That’s it now you are done. you can run topology builder and download current topology to make sure that CS store is using the new Lync 2013 Front end.

Author: Lyncdude

A Senior Microsoft Unified Communications Consultant with more than 9 years of experience in Microsoft Exchange and Microsoft Lync Server / Skype for Business. Egyptian guy lives and works in Frankfurt - Germany. Worked Closely with Microsoft Dubai for 3 years designing , building and supporting Exchange and Lync Infrastructures. A Microsoft Certified ITP in Lync, Exchange and also attended Microsoft Partner Primer Filed Support Engineer T1 Training for Microsoft Lync 2010.

7 thoughts on “Moving Central Management Server from Lync 2010 to Lync 2013 Front End”

  1. Will the Lync 2010 server still operate with users on it after moving the CS Management Database and changing it to the Lync 2013 server? I still have users on Lync 2010 while we migrate to Lync 2013.

    1. Sorry for the late answer,
      you can move the CMS database with no problem or effect on the Lync 2010 users, but recommendation is to do this step after moving all users to Lync 2013, but no problem doing it before migrating the users

  2. I am glad to have this document with me, It worked like a charm.

    one thing I would like to add, in Step ” Now go to the old Lync Server 2010 Front End Server.” , it asked for installation of SQLexpress old version and I clicked on “RUN” for two times and once the task got finished, I restarted Lync 2013 (new server) and Replication worked like a charm.

    Thank you,
    Tejas

    1. Hi,
      no need to restart the server after moving the Database, but it is highly recommended to do this task and plan it during scheduled downtime.

      and don’t forget to backup your database before starting the process

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s