how to create an alert base in an unexpected shutdown
What would be the best approach to achieve this. Creating alerts based on events ID? or--I was wondering if SCOM already has a MP that monitors this events. Thank you
June 13th, 2012 12:57pm

Catching the specific event is the best way to achieve this: http://gaionlinekb.blogspot.be/2009/10/scom-2007-unexpected-shutdown-where-is.html There is no out-of-the-box monitor/rule for this, so you have to author it.
Free Windows Admin Tool Kit Click here and download it now
June 13th, 2012 1:31pm

Now how to create an event type monitor to look for event 6008?
June 13th, 2012 4:12pm

The TechNet documentation can help you out on this one: http://technet.microsoft.com/en-us/library/bb309597.aspx
Free Windows Admin Tool Kit Click here and download it now
June 13th, 2012 4:24pm

Well, I have been reading about this topic in different forums and, I'm really confuse. how come by default SCOM dos not have a way to alert me if a server --not a client machine--goes down. If I do the event ID, SCOM will alert me after the event had happened. What about if the server stays down. I ran a test with one of my servers and I toked it down for a few minutes to see if SCOM will generate an alert but, no love. I so the server been gray out in the Monitoring section but no alert. By default, alerts for missed heartbeats and computer not reachable are disabled for client operating systems. To receive alerts for client operating systems, override the Health Service Heartbeat Failure and Computer Not Reachable monitors for the class Windows Client Operating System to set the Generates Alert parameter to True. So how to solve this issue. Please help
June 14th, 2012 11:21am

SCOM waits default for 3 minutes before generating an alert, this is calculated by the heartbeat interval and the allowed missed heartbeats. Default this is 1 minute intervals and 3 allowed missed heartbeats, so 3 minutes. Did you wait at least this long for an alert to be generated? The alert should be generated after 3 minutes, by the health service watcher object of the tested server. If it doesn't, check if your SCOM server is in maintenance mode, which disables alert-generation entirely.
Free Windows Admin Tool Kit Click here and download it now
June 14th, 2012 11:24am

SCOM waits default for 3 minutes before generating an alert, this is calculated by the heartbeat interval and the allowed missed heartbeats. Default this is 1 minute intervals and 3 allowed missed heartbeats, so 3 minutes. Did you wait at least this long for an alert to be generated? The alert should be generated after 3 minutes, by the health service watcher object of the tested server. If it doesn't, check if your SCOM server is in maintenance mode, which disables alert-generation entirely.
June 14th, 2012 11:27am

Jan, Thank for the keep posting. I double check the settings for the heartbeat == 3 missed allowed heartbeat intervals == 30 seconds I'm about to shutdown a server for 5 minutes lets see if I get an alert
Free Windows Admin Tool Kit Click here and download it now
June 14th, 2012 11:51am

Thank you for keep posting
June 14th, 2012 11:51am

It's been 20 minutes and no alert
Free Windows Admin Tool Kit Click here and download it now
June 14th, 2012 12:23pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics