Hi All Today we have received lot of Heartbeat failure alert normally restarting the health service solves our problem but for today it's not worked. We have also repair the agent, change the primary management server but no luck. When we checked OpsMgr Event log we found Event ID 20070 with Source OpsMgr Connector is generated. Any Help Greatly Appreciated.Thanks|Amit Haridas|

Is there a firewall between the agents having issues and the RMS? Can you telnet to port 5723?

Hi Jeremy Yes, I am able to ping and telnet all my Management Servers and RMS server.Thanks|Amit Haridas|

Hi Amit, I recently had the same problem in a customer environment. Normally the scom heartbeat monitoring works very well. The only change that occured around the time the problem raised, was a certificate rollout. I did not find a solution, but i suggest you reset the Heartbeat monitor to healthy. Then you stop and start the agent service on of the servers to see if the heartbeat alert raises and is closed automatically as it is supposed to. For the future i would keep an eye on this behaviour. Greetings Yannick

Hi, May I know the topology of your environment? Is this agent connecting to the RMS directly or via other MS? Is this agent in a workgroup or DMZ? At this time, please try the following: 1. Regarding Event ID: 20070, please check the Primary DNS Suffix: 1) Run ipconfig /all. 2) In the output, “Primary Dns Suffix” value should match the Domain name; if not, please change the value “Primary DNS suffix of this computer” to the Domain name in System Properties. 2. Please also refer to the methods in the following posts: Fixing troubled agents http://blogs.technet.com/b/kevinholman/archive/2009/10/01/fixing-troubled-agents.aspx Getting headaches trying to figure out why you are seeing the 'Not Monitored' state for Management Servers or Agents? http://blogs.technet.com/b/momteam/archive/2008/03/10/getting-headaches-trying-to-figure-out-why-you-are-seeing-the-not-monitored-state-for-management-servers-or-agents.aspx Hope this helps. Thanks. Nicholas Li - MSFT Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

If you received a HB alert from most or all agents, this is indicative of a RMS unavailability issue. RMS unavailable can be caused by many things, but common issues related to this is insufficient resources or hardware configuration is not optimal.HTH, Jonathan Almquist - MSFT