Move CMS from Lync 2010 to Lync 2013

After upgrading from Lync 2010 to Lync 2013 I was not able to move the CMS from the Lync 2010 front-end server to the Lync 2013 front-end server using the Move-CsManagementServer command. It constantly returned this error:

PS C:\Users\administrator> Move-CsManagementServer

Confirm

This cmdlet moves Central Management Server to the pool that contains this computer.

Current State:

Central Management Server Pool: “lyncpool.exchangelabs.nl”

Central Management File Store: “\\t-sql02.wesselius.local\Lync”

Central Management Store: “T-SQL02”

Central Management Store SCP: “T-SQL02”

Proposed State:

Central Management Server Pool: “lync.exchangelabs.nl”

Central Management File Store: “\\t-sql03.wesselius.local\lync2013”

Central Management Store: “t-sql03.wesselius.local”

Central Management Store SCP: “t-sql03.wesselius.local”

Do you want to move the Central Management Server, Central Management Store, and File Store in the current topology and assign permissions for computers in Active Directory? (Note: Please read the help provided for this cmdlet using the Get-Help cmdlet before you proceed.)

[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help

(default is “Y”):y

WARNING: Move-CsManagementServer failed.

WARNING: Detailed results can be found at

“C:\Users\administrator.HOSTEDAPPS-T\AppData\Local\Temp\Move-CsManagementServer

-9707ba55-076a-4f51-a153-304e9add4e6b.html”.

Move-CsManagementServer : Cannot move Central Management Server. The new Central Management Store located at “t-sql03.wesselius.local” is not accessible.

At line:1 char:1

+ Move-CsManagementServer

+ ~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : InvalidData: (:) [Move-CsManagementServer], Exception

+ FullyQualifiedErrorId : Move not supported.,Microsoft.Rtc.Management.Deployment.MoveCms.MoveCmsCmdlet

PS C:\Users\administrator>

Banged my head on my desk for some time. The error says “The new Central Management Store is not accessible”, but it was fully accessible, could do anything I want on the box.

But it’s not the server, it’s the Central Management Store that’s not available. During an upgrade from Lync 2010 to Lync 2013 this is easy to forget. The CMS is running on Lync 2010, but the CMS (the actual databases!!) are not running on Lync 2013. So, the first thing is to create the Central Management Database on the new SQL Server that will host the CMS for Lync 2013:

Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn t-sql03.wesselius.local –SqlInstance –clean

The –clean parameter will prepare the databases on the new SQL server and make sure they are in a predictable state.

Now when you move the Central Management Store using the Move-CsManagementServer command it will succeed. It will generate some warnings though, but these are more follow-up items like the removal of the Lync services from the old front-end server.

PS C:\Users\administrator > Move-CsManagementServer

Confirm

This cmdlet moves Central Management Server to the pool that contains this

computer.

Current State:

Central Management Server Pool: “lyncpool.exchangelabs.nl”

Central Management File Store: “\\t-sql02.wesselius.local\Lync”

Central Management Store: “T-SQL02”

Central Management Store SCP: “T-SQL02”

Proposed State:

Central Management Server Pool: “lync.exchangelabs.nl”

Central Management File Store: “\\t-sql03.wesselius.local\lync2013”

Central Management Store: “t-sql03.wesselius.local”

Central Management Store SCP: “t-sql03.wesselius.local”

Do you want to move the Central Management Server, Central Management Store, and File Store in the current topology and assign permissions for computers in Active Directory? (Note: Please read the help provided for this cmdlet using the Get-Help cmdlet before you proceed.)

[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help

(default is “Y”):

WARNING: The move completed successfully but the following additional steps are required:

Run local setup on the following computers to remove Central Management services that are no longer defined in the topology:

– t-lyncfe01.wesselius.local

WARNING: “Move-CsManagementServer” processing has completed with warnings. “1” warnings were recorded during this run.

WARNING: Detailed results can be found at “C:\Users\administrator.HOSTEDAPPS-T\AppData\Local\Temp\Move-CsManagementServer-0c1d1d93-1f92-42c6-845c-003058397fdd.html”.

PS C:\Users\administrator >

Once the follow-up items are performed you’re done!

One thought on “Move CMS from Lync 2010 to Lync 2013”

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com 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 )

Google+ photo

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

Connecting to %s