Move SFB CMS Stuck

Question

Hello,

I tried to upgrade from SfB 2015 to 2019 and final step was to move Central Management Server via Move-CsManagementServer to another pool that ended up with error. Trying running this cmdlet again says the following:

This cmdlet moves Central Management Server to the pool that contains this computer.
Current State:
Central Management Server Pool: "NEW POOL FQDN"
Central Management File Store: "\NEW FILESTORE"
Central Management Store: "NEW SQL CONNECTION"
Central Management Store SCP: "NEW SQL CONNECTION"
Proposed State:
Central Management Server Pool: "NEW POOL FQDN"
Central Management File Store: "\NEW FILESTORE"
Central Management Store: "NEW SQL CONNECTION"
Central Management Store SCP: "NEW SQL CONNECTION"
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?
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"):

So it looks like management server has moved, BUT if I hit Y I got following error (-force switch is helpless):

###50020:XdsPublishItems:This central management store is being moved to another location. No changes can be made until this move is completed

Running cmdlet Set-CsManagementServer -Identity "ManagementServer:NEW_POOL_FQDN" ended up with:

Set-CsManagementServer : The role "ManagementServer" is not present on pool

All changes like adding/altering/removing users ends up with

###50020:XdsPublishItems:This central management store is being moved to another location. No changes can be made until this move is completed

despite changes are made. Also users cannot make changes to their contact lists.

Is there a way to override this status or complete the move and install ManagementServer role?

Answer 1

Hi @MaximEgorov-2315,

To make sure you have moved the CMS successfully to the new pool, you should meet these two requirements:

1.CMS data did get moved to the new database

2.Active Directory get updated to point to the new SQL server

So you can try to change the CMS configuration point and Active Directory SCP object forcefully by running the following command:

Set-CsConfigurationStoreLocation -SQLSERVERFQDN “SQLFQDN2.domain.com” -SQLINSTANCENAME “sqlinst2” -Verbose

Set-CsManagementConnection -STOREPROVIDER sql -CONNECTION “SQLFQDN2.domain.com\sqlinst2” -Verbose

---

If the response is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.