Something odd when I was done. Everything went perfectly. No errors at all and went as expected. I noticed though after everything was done and I had not yet uninstalled the CMS from Lync 2010 that two services on the Lync 2010 were stopped but in an Automatic
startup state. They are the "Lync Server File Transfer Agent' and the "Lync Server Master Replicator Agent'. Thought it was odd they were both stopped. I am sure it had something to do with the CMS move and all the scripting that goes on. The rest
of the Lync services are running.
I am thinking though if they were supposed to be stopped, why not disable them. Why leave them at Automatic. I am not seeing any errors or warnings at all on the Lync 2010 or 2013 servers. Application, System and Lync Server logs are clean. Everything appears
to be OK.
Thing that concerns me though is when I run the Get-CsManagementStoreReplicationStatus on the 2013 FE, the databases all come back looking good with UpToDate = True but the last replication was last night (about 8-9 hours ago) shortly after I completed the
procedure.
I want to just uninstall the CMS on Lync 2010 which is the last step but I want to make sure everything is OK before I do. Not sure if I should start those services. I never rebooted the 2010 server after moving the CMS. Seems if I did, those services would
have tried to start. Very confused here.
Wanted to add also that I have both the above services on the 2013 FE server and they are both running. And, when I run Get-CsManagementStoreReplicationStatus -CentralManagementStoreStatus on my Lync 2013 FE, it says it is the active master and active file
transfer agent so maybe that is why the services are stopped? If so, what if I had rebooted the 2010 server. Those services would have tried to start because they are set to Automatic.
I guess the real question here is how often should the Lync servers being updating their replicas with each other. We have a very small environment right now with only a few hundred users.