Move-CsManagementServer failed / Cannot move Central Management Server.

Description

You get the following error message when trying to move the Lync 2010 CMS to another server:
> Move-CsManagementServer

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

Current State:
Central Management Server Pool: "oldserver.local"
Central Management File Store: "\\oldserver.local\share"
Central Management Store: "oldserver.local\rtc"
Central Management Store SCP: "oldserver.local\rtc"

Proposed State:
Central Management Server Pool: "newserver.local"
Central Management File Store: "\\newserver.local\share"
Central Management Store: "newserver.local\rtc"
Central Management Store SCP: "newserver.local\rtc"


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\kobi\AppData\Local\Temp\2\Move-CsManagementServer-ed47b4e0-f64b-4a00-
8f89-6a70ce5402ef.html".
Move-CsManagementServer : Cannot move Central Management Server. The new Central Management Store located at "newserver.local\rtc" is not accessible.
At line:1 char:24
+ Move-CsManagementServer <<<<
+ CategoryInfo : InvalidData: (:) [Move-CsManagementServer], Exce
ption
+ FullyQualifiedErrorId : Move not supported.,Microsoft.Rtc.Management.Dep
loyment.MoveCms.MoveCmsCmdlet

Solution

Run the following PowerShell command on the new Lync server:
Install-CsDatabase -CentralManagementDatabase -clean -sqlserverfqdn server.fqdn.local -sqlinstancename rtc

And then re-run the Move-CsManagementServer command again.

Affected software:

Microsoft Lync Server 2010
Microsoft Lync Server 2013




Comments:

Comment #1 from Marty [Username: Guest] at 07/07/2011 14:42
Way to go on this essay, hleped a ton.
Comment #2 from James Maxwell [Username: Guest] at 14/08/2011 15:42
Can I add when I tried this command, the "sqlinstance rtc" section had to be "-sqlinstancename rtc" (without the quotes).

I have yet to do the rest of the set-up and move the management server so will let you know if I find any other changes I had to do that other users might find useful as alternatives if the original guide does not work.
Comment #3 from Kobi Shmueli [Username: Kobi_S] at 17/10/2011 16:59
James: You are correct. I have fixed the KB. Thanks!
Comment #4 from Will [Username: Guest] at 22/03/2013 19:47
Still helpful for Lync 2013. Thanks.
Comment #5 from Kobi Shmueli [Username: Kobi_S] at 26/03/2013 17:52
Will: Thanks! I have updated the KB to include Lync Server 2013.
Comment #6 from Jordan Zielin [Username: Guest] at 18/05/2013 03:26
Thank you sir! :)
Comment #7 from Johan [Username: Guest] at 08/08/2013 14:07
Superb! Thank you for sharing your knowledge.
Comment #8 from Ben [Username: Guest] at 19/08/2013 18:29
Thanks for his article, worked for me! Worth noting that I had to change sqlinstance name from rtc to our instancename as we do not have the default name.
Comment #9 from Philip D'Ath [Username: Guest] at 08/05/2014 08:22
I was following the TechNet article on how to move the database, ran into this error, and your article resolved my problem.

http://technet.microsoft.com/en-us/library/jj688013.aspx
Comment #10 from Dennis [Username: Guest] at 23/12/2014 18:04
Same as Philip. Your technote was perfect. THANKS!
Comment #11 from Josh Ferguson [Username: Guest] at 25/09/2015 20:20
Thank you! Thank you! I'm guessing I was missing the -clean argument when I tried on my own. Works great now!
Comment #12 from alex [Username: Guest] at 14/10/2015 13:26
Thanks. This helped with a Lync to SkypeForBusiness migration.
Comment #13 from Bob [Username: Guest] at 24/01/2017 19:56
This resolved my issue. Thank you!!


Add new comment
Name:
Anti-Bots verification code (just write 1234):