Any harm in not removing the CMS from Lync 2010 after migrating to 2013?

Here is my situation. We have moved all our users over to 2013. At this time, we just us IM and Presence. No conferencing. I have a single 2010 Std Edition server with a local CMS. I moved the CMS to 2013 last week but a replica is still on 2010. The Microsoft article that I used to move the CMS to 2013 says I should remove the CMS from 2010.

Here is the thing though. We are still using the 2010 Edge box as we have not had a chance to update it yet. Our next hop on the Edge is 2013 so 2010 should be out of the picture. I was afraid to remove the CMS from 2010 thinking that the Edge still needs it. Our 2013 FE is now the Master replicator so the Edge is getting its update from it.

I know it sounds silly but I did not want to disturb the Edge in any way even though it is not used that often. Not sure if I should wait until I decommission the 2010 Edge and move to 2013 before I remove the CMS from 2010 and decom the 2010 FE?

February 27th, 2014 8:34am

You can move it, it shouldn't cause any problems,  I normally leave moving the CMS until last out of habit, however I have done it earlier too a couple times and it didn't appear to cause any issues. It just means you have to keep your Lync 2010 front end server up and running until you're ready to move. 

So either way, its up to you. If you leave it, just remember to move it before you remove your 2010 environment or you'll end up with a lot of headaches :) It's probably worth taking a backup of it - just in case. (Export-CsConfiguration/Export-CsLisConfiguration)

Here's a reference where someone else did the same: http://social.technet.microsoft.com/Forums/lync/en-US/eaaabe82-5bc0-4501-b9e7-831409f16fe0/moving-lync-central-management-store-to-2013?forum=lyncinter

February 27th, 2014 9:12am

Thanks. I am not talking about moving the CMS though. That has already been done. I am talking about removing the replica from 2010. That article talks about moving the CMS to 2013 but it does not mention removing the 2010 replica.

Like you said, I really don't think it matters until you decide to decommission the 2010 box completely. Only reason I bring it up is because I have read in several articles stating that after you move the CMS to 2013, you should remove the 2010 replica. Even the MS article states that.

I was all set to do it and then got a bit nervous because we still use the 2010 Edge. What the CMS has to do with the Edge I have no idea. I just don't know Lync well enough to make that decision.

You might be able to answer this however. If we decide to stay with the 2010 Edge indefinitely, do we need to keep the 2010 FE around? I think the two servers are independent of each other but again, not sure.

Thanks for taking the time to reply.

February 27th, 2014 9:56am

As long as your 2010 Edge is pointing to the 2013 Front End as the next hop and when you check replication status it is showing coming from the 2013 edge you should be fine.  When I perform migrations like this I normally just shutdown the 2010 Front End as a final testing procedure to validate communication flow. 
Free Windows Admin Tool Kit Click here and download it now
February 27th, 2014 11:09am

Thanks. I think you meant 2013 FE, not Edge when you talk about replication. Right? I don't know of any way to tell how the 2010 Edge is getting its updates but I did use powershell to for a replication between the 2013 and the 2010 Edge and then looked in the event log on the 2010 Edge and saw the successful update. Other than that, I really don't know of any way to see how a server is getting its updates. There is no replmon like in AD.
February 27th, 2014 11:55am

As long as your 2010 Edge is pointing to the 2013 Front End as the next hop and when you check replication status it is showing coming from the 2013 edge you should be fine.  When I perform migrations like this I normally just shutdown the 2010 Front End as a final testing procedure to validate communication flow. 
Free Windows Admin Tool Kit Click here and download it now
February 27th, 2014 7:03pm

Hi,

This process of transferring information updates from master to replica is called replication. The replication process consists of copying information between directories from the master to the replicas, applying the changes received to the replica and report status back to the master.

The MASTER generates the data package containing new changes to CMS and stores a copy in each to-replica directory for every replica.

The data package must be copied to all replicas. All Lync Server 2013 servers, except the Edge Server, uses the Windows file copy SMB[4] protocol mechanism to push the data package from the CMS master to the replica.

For Edge servers, since Edge servers is not a member of domain, the file copy is performed over an HTTPS channel. The Edge Server runs a Web Service on the port specified for the ManagementServices in the topology document. The default port is 4443. The Web Service, ReplicationWebService, does not require IIS to be installed on the Edge Server. It is implemented as part of the REPLICA service.

You can refer to the link below, it is for Lync server 2010 but similar for Lync server 2013:

https://blogs.technet.com/b/jenstr/archive/2010/10/13/what-is-central-management-store-cms.aspx

Best Regards,

Eason Huang

March 3rd, 2014 8:48pm

Hi,

This process of transferring information updates from master to replica is called replication. The replication process consists of copying information between directories from the master to the replicas, applying the changes received to the replica and report status back to the master.

The MASTER generates the data package containing new changes to CMS and stores a copy in each to-replica directory for every replica.

The data package must be copied to all replicas. All Lync Server 2013 servers, except the Edge Server, uses the Windows file copy SMB protocol mechanism to push the data package from the CMS master to the replica.

For Edge servers, since Edge servers is not a member of domain, the file copy is performed over an HTTPS channel. The Edge Server runs a Web Service on the port specified for the ManagementServices in the topology document. The default port is 4443. Even you Move CMS store and CMS Master service from 2010 to 2013, the replication is a logical concept so you can replicate CMS information with the help of Lync server 2013 CMS master service.

You can refer to the link below, it is for Lync server 2010 but similar for Lync server 2013:

https://blogs.technet.com/b/jenstr/archive/2010/10/13/what-is-central-management-store-cms.aspx

Best Regards,

Eason

Free Windows Admin Tool Kit Click here and download it now
March 4th, 2014 4:45am

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

Other recent topics Other recent topics