We are running SCOM 2012 SP1 and 2016 dual-homed with AD MP Version 6.0.8321.0 for Server 2008 and above, and version 10.0.0.0 for 2016. Receiving “AD Replication is occurring slowly” alerts for 3 of our DC’s (92 total), repeat count increases by 3-4 every 1-2 minutes. All three are running Windows 2012 R2 Standard, AD, DNS, and Are GC’s. Followed this article to increase max latency to 60 (from 15) for the environment:
Found the pattern of AD Object attribute adminDescription in OpsMgrLatencyMonitors for each of these DC’s had not updated as does the rest of the environment. This was checked on the three DC’s local copy of the directory. For instance, DC03 and DC04 from the same site, same subnet, one updates adminDescription, one does not. It seems the part of the script which is supposed to update this Object in AD every 6th run (according to the above referenced article) is not doing so. DC03 updates ok, DC04 does not . Both agents are running as Local System, both are dual-homed, running agent v 8.0.10918.0., both in a healthy state. Alerting DC’s alert in both 2012 SP1 and 2016 environments.
Is there a way to 1) assure that the AD replication scripts are running,and if not, why, 2) If the script is running, why is it not updating the attribute adminDescription? and, 3) How do I figure out which DC object in the local directory copy is triggering the slow replication during the running of the script?
Has the OOMADs components being install on the DC’s too. There are some things that don’t run properly on DC’s without it.
you will also find that this is an issue in mixed environments. Primarily as it depends where the agent looks for oomads being installed which is different depending on whether it is installed in C:\Program Files\System Center Operations Manager or C:\Program Files\Microsoft Monitoring Agent. I have witnessed this occurring in an environment recently where it is mixed 2007 R2 and 2016. All upgraded agents have this issue in 2007 but not in 2016 alerting.