Hi All

When running get-csmanagementstorereplicationstatus all the lync servers shows up as true and with the same time stamp.

If I update a user in the lync control panel or just move the user to another pool and then check the cms replication status again the date and time stamp stays the same. If I invoke replication then it updates and all the servers shows the same time and true status again.

On the cms master I have restarted the replication service as well as the master replication service and dont' see any errors in the logs. There are also replication errors on any of the other servers.

I'm thinking of restarting all the servers, but this is a big setup and I was hoping for a quick fix if anyone have any suggestions.

Regards

I'm confused about the issue.  The CMS stores information about topology, configurations and policies.  It does not store user data.  If you modify a user, it won't necessarily then change the up to date status to false for CMS replication.  The user information itself is stored within a separate database, and when a user is moved, this data is copied to the other pool's database.  Additional user information is stored in the form of AD attributes, which are subject to Active Directory replication intervals if changed from another site. 

What is the issue you're experiencing?

Hi danielategan,

Anthony is right.

CMS is a repository to store management data in the form of topology, configurations and policies.

Please have a look at the following article.

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

Best regards,

Eric

Apologies if I had this wrong - the issue i'm experiencing is that when up move a user from a pool or even create a user in the lync control panel then I normaly do a get-csmanagementstoreplicationstatus  and it will then be false for all servers whereas the status were true before the user move/creation. I always thought this is normal? So at the client i'm at I'm not doing any topo changes and only users gets created and move around pools if needed. Even if I create a RGS group it also behaves in the same manner. If this is how it is supposed to work, then apologies for my post.