Issue after CMS move

HI all,

Been following this guide to move CMS from 2010 to 2013: http://uc-dude.com/2013/02/07/moving-central-management-server-from-lync-2010-to-lync-2013-front-end/

So far everything looks good and in topology 2013 pool is shown as CMS store.

When i run Get-CsManagementStoreReplicationStatus all status shows as healthy,but when i run

Get-CsManagementStoreReplicationStatus -CentralManagementStoreStatus it still says that the following still has old Lync 2010 server as master:

ActiveMasterFqdn
ActiveFileTransferAgentFqdn
ActiveReplicas (shows list of Lync 2010 servers only).I did run setup or remove component and step 2 on Lync 2010 Frontend server,but have not remove it yet,.Should i do this before it will show the new 2013 pool as master?

t

May 9th, 2015 11:53am

All steps seems fine at your end. I don't see any harm to run deployment wizard on lync 2013 pool members to force update to CMS store and then check
Free Windows Admin Tool Kit Click here and download it now
May 9th, 2015 12:20pm

Hi Anil and thanks for reply,

it has already been done and CMS shows new pool as CMS store in topology.My question is why it still shows old pool as master when i run Get-CsManagementStoreReplicationStatus -CentralManagementStoreStatus .

Shouldnt it be showing the new pool instead?

May 9th, 2015 12:29pm

Hi,

when i run Get-CsManagementStoreReplicationStatus the last update was yesterday on all servers.

Both mail servers (trusted application servers) have status failed.

If i restart Lync Server Master Replicator Agent and run Get-CsManagementStoreReplicationStatus, then it is updated.

Still when run Get-CsManagementStoreReplicationStatus -CentralManagementStoreStatus it shows old lync server as master,even i did uninstall the cms database yesterday.

I suspect something is wrong,but how can i fix so cms replicates as often as it should, and that master is shown to new pool?

thanks!

Free Windows Admin Tool Kit Click here and download it now
May 10th, 2015 8:13pm

Hi,

Did you run the Lync command Move-CsManagementServer on Lync Server 2010 or on the Lync Server 2013 FE Server/FE pool?

On Lync Server 2013 FE Server, please run the following Lync Server Management Shell firstly: Enable-CsTopology

If Enable-CsTopology is not successful, resolve the problem preventing the command from completing before continuing. If Enable-CsTopology is not successful, the move will fail and it may leave your topology in a state where there is no Central Management store.

Then run Move-CsManagementServer on the Lync Server 2013 FE Server again and check the result again.

More details:

https://technet.microsoft.com/en-us/library/jj688013(v=ocs.15).aspx

Best Regards,
Eason Huang

May 11th, 2015 2:37am

Hi Eason and thanks for reply,

i finally managed to fix it by re-creating CMS database on the New pool.

Even after enable-topology and enable-cscomputer didnt help.

Now it seems like the replication is not running.When i run Get-CsManagementStoreReplicationStatus last updated status was last night,around the time i re-created the CMS database.

If i restart master replication service or manual invoke,then it gets updated.

If im not wrong it should auto replicate every 5 minutes?All Frontend servers have been restarted without help.

Any ideas?

Free Windows Admin Tool Kit Click here and download it now
May 11th, 2015 6:38am

Hi, it wont replicate every 5 minutes, only when there is a configuration change will it initiate replication. As long as the replication is true for all servers then your looking good.

To test you can use invoke-csmanagementstorereplication from Management shell then use get-csmanagementstorereplicationstatus to check the replication status.You should see all servers set to false straight after the invoke then keep trying the get command and you should see it say true.

Thanks,

Martin

September 1st, 2015 3:41am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics