I have a new Active Directory Forest deployed all on Windows Server 2012 R2 DCs. I have a total of 5 DCs deployed in two sites. 3 DCs in my primary datacenter and 2 DCs at my DR Site. I’m now installing System Center Operations Manager 2012 R2 into the environment. I have the SCOM server installed and pushed out the SCOM agents on all 5 domain controllers. The three in my primary datacenter appear to be working perfectly.
However, the two DCs in my DR Site are both having the same issue. I am getting the following alerts for both DCs: Health Service Heartbeat Failure.
Now, if I understand this alert correctly, it is saying that the agents on my two DCs are not sending the expected heartbeat messages to the SCOM server. The network between the two datacenters is 100Mbps, and is performing very well, and currently under a light load. I’ve double checked all the communications between the servers, and everything is functioning perfectly.
I then tried to restart the “Microsoft Monitoring Agent” Service. This is where the issue is, I just don’t know what to do about it!!! When attempting the stop the service, it takes several minutes of trying and then it will finally come back with an error indicating that the service did not respond to the command in a timely fashion. However, despite the error message, the process does eventually get stopped or killed (not sure which one). Then, if I start the service back up, the above Alert will be removed from the SCOM console. But then the alert will eventually occur again. Sometimes just minutes later, sometimes hours later.
I have also tried replacing one of the domain controllers in the DR site with a new one. No difference. The new DC does the exact same thing.
Does anyone have any ideas? Please note that I am new to SCOM.