Moving Central Management Server from Lync Server 2010 Standard Server to 2013 Standard Server

Similar to one of my previous posts:

Moving Central Management Server from Lync Server 2010 enterprise front end pool to 2013 enterprise front end pool
http://terenceluk.blogspot.com/2013/01/moving-central-management-server-from.html

… this post serves to demonstrate the process of moving the Central Management Server from a Lync Server 2010 Standard server to a Lync Server 2013 Standard Server:

Documentation on how to do this can be found at the following URL:

http://technet.microsoft.com/en-us/library/jj688013.aspx

Prepare Standard Edition Front End Server

Begin by logging onto the Lync Server 2013 Standard front end server that you will be moving the CMS to and launch the Deployment Wizard:

Proceed through the wizard:

Now open up the Lync Server Management Shell and execute the following:

Install-CsDatabase -CentralManagementDatabase -SQLServerFQDN <FQDN of your Standard Edition Server> -SQLInstanceName <name of instance – RTC by default>

Since I’m using the Default RTC instance, the cmdlet I will be executing will look like the following:

Install-CsDatabase -CentralManagementDatabase -SQLServerFQDN svrlyncstd02.domain.internal -SQLInstanceName RTC

Once completed, confirm that the Lync Server Front-End service is Started.

-------------------------------------------------------------------------------------------------------------------------------------------------------------------

Note that prior to running the Install-CsDatabase cmdlet above, the databases on the RTC instance are as follows:

• cpsdyn
• rgsconfig
• rgsdyn
• rtcab
• rtcshared
• rtcxds

… now that the Install-CsDatabase cmdlet has been successfully executed, you should see the following databases on the RTC instance:

cpsdyn

lis

rgsconfig

rgsdyn

rtcab

rtcshared

rtcxds

xds

lis and xds are the databases that were additionally installed.

-------------------------------------------------------------------------------------------------------------------------------------------------------------------

Move CMS from Lync Server 2010 to 2013

With the new CMS installed on the destination server, proceed by publishing the topology with Enable-CsTopology:

Once Enable-CsTopology has successfully executed, proceed with moving the CMS with Move-CsManagementServer:

Once the Move-CsManagementServer completes, open up the Deployment Wizard on the new CMS server (Lync Server 2013) and click on Install or Update Lync Server System:

Run the Setup or Remove Lync Server Components:

Open up the Deployment Wizard on the old CMS server (Lync Server 2010) and click on Install or Update Lync Server System:

Run the Setup or Remove Lync Server Components:

From here, it’s important to confirm that replication with the new Central Management store is occurring so proceed by using the cmdlet:

Get-CsManagementStoreReplicationStatus

… to confirm that replication is in good health:

Note that the replication process shouldn’t take long (usually no longer than 5 minutes) and there were situations where I’ve noticed that the Lync Server File Transfer Agent service wasn’t running:

… so if you’ve been waiting for 10 minutes or more, check to make sure that the Lync Server File Transfer Agent service is running.

Remove Lync Server 2010 Central Management store files

With the CMS moved and replication confirmed to be in working order, proceed with removing the CMS files from the old Lync Server 2010 by using the following cmdlet:

Uninstall-CsDatabase -CentralManagementDatabase -SqlServerFqdn <FQDN of SQL Server> -SqlInstanceName <Name of source server>

Since this is a Standard server, the server hosting the CMS will be the Standard itself and cmdlet to execute will be as follows:

Uninstall-CsDatabase -CentralManagementDatabase -SqlServerFqdn svrlyncstd01.domain.internal -SqlInstanceName RTC

Once the cmdlet successfully executes, we will now have the CMS completely moved to the new Lync Server 2013 pool and removed from the old Lync Server 2010 pool.