Hello, I shutdown one of the test servers: Pinging OPMGRACS1.ad.medctr.ucla.edu [10.32.188.27] with 32 bytes of data: Reply from 10.32.188.25: Destination host unreachable. Reply from 10.32.188.25: Destination host unreachable. Reply from 10.32.188.25: Destination host unreachable. Reply from 10.32.188.25: Destination host unreachable. Ping statistics for 10.32.188.27: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), but the Ping Status remains Healthy as all items 14 hours after the shutdown,... something is wrong? I tried a "Reset Health" and a "Recalculate Health" everything is healthy the server is still down !!!! but all green in the console...!!! I shutdown a second server it took 30 minutes to get the ping status down!!! Any idea? Thanks, DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Guessing these are not agent managed servers since an agent heartbeat would catch this more reliably.Microsoft Corporation

Hello Dan, The server OPMGRACS1 is listed under Administration > Device management > Agent Managed as Healthy (not grayed out... not red...). Any previous status (Healthy) of the server needed to make it different from the current status and send the alert? Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

"I shutdown a second server it took 30 minutes to get the ping status down!!!" i read in another post of you, that you set the number of missed heartbeats to 30... so this alert is entirely as configured! When the heartbeat monitor goes critical it triggers the ping. here's 2 screenshots of what does impact the time before you get alerts: http://jama00.wordpress.com/2010/07/14/what-is-the-optimal-setting-for-my-environment-when-it-comes-to-missed-heartbeats/. maybe the blog is helpful as well, allthough if you set it to 30x 60secs, dont complain it takes too long before scom notices a server down.Rob Korving http://jama00.wordpress.com/

Hi Rob, Sorry I was incorrect, thnaks for catching my mistake. Ping Status is set to: - Frequency: 300 - Response Time Threhold 5,000 Administration > Settings > Agent > heartbeats : 60 Administration > Settings > Server > heartbeats : 3 What has changed was the number of samples in Monitors (Total CPU Utilization Percentage, etc... ) My mistake for not giving details earlier. I ran the queries: number of alerts for “Health Service HeartBeat Failure” and “Failed to Connect to Computer” with a closed status. alertstringname Number_of_alerts Failed to Connect to Computer 8 Health Service Heartbeat Failure 8 and the number of heartbeat failure alerts which were closed within 2 minutes after creation alertstringname Number_of_alerts Failed to Connect to Computer 4 Health Service Heartbeat Failure 4 this does not seem too bad. Also in my test group the server having this "latency" is the ACS (Audit Control Server) server in the SCOM Architecture is it a special one... heartbeating, ping, etc... ? Thanks for helping. Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager