• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1014
  • Last Modified:

How to Configure Alerts in Microsoft SCOM 2012 for Windows Servers

How to Configure Alerts in Microsoft SCOM 2012 for Windows Servers.

I need Alerts or Notification from SCOM 2012 System when any windows servers is down or Up or not ping able.

Kindly help me step by step as I am new to Microsoft SCOM 2012.

Thanking you in advance.
Kind Regards,
Syed Abdulbasith
Syed Abdulbasith
  • 2
3 Solutions
btanExec ConsultantCommented:
the forum is good place to search for SCOM related matters
the "Quick Reference" to SCOM tasks will be handy, note that for systems or device to be monitored, SCOM has to discover them first https://technet.microsoft.com/en-us/library/hh230738.aspx
the "How Objects Are Discovered and Monitored" section depict the required workflow

At first installed, only the features of the Operations Manager infrastructure such as management servers, reporting servers, and databases are monitored. Monitoring of the infrastructure is provided by the Monitoring Pack for SCOM.

 But for your use case, there is management pack (MP) for Windows Server and you need to  import the MP so that SCOM will have the information required to identify and monitor those platform. There can be need for more MPs (for 'discover', 'monitoring', 'library' and 'reports etc) to be downloaded as well - see run through steps http://www.windows-noob.com/forums/index.php?/topic/8615-scom-2012-sp1-in-a-lab-configuration-part-b-import-management-packs/

 After importing, you should be able to see Microsoft Windows Server folder, and within there it has a Windows Server State view that shows the status of the server(s). SCOM can now start Alerting to issues that it can detect and monitor wrt to the MP imported under this new server import. You can list out the alert using SCOM command shell (e.g. in the “Get-Alert” section in the table below)

 There should be already a set of services monitored by default by agent deployed to the systems e.g. DNS Client, DHCP Client, RPC, etc. Under each monitor, it has the alert already configured. This example show one instance of alerting when particular service not running.
I do not supposed you need any customisation for now and try out to setup the basic first to see if it fit the use case.
Viral RathodConsultantCommented:
Powershell: PingCheck, a simple script to ping a list of servers and alert via email

Here is a simple script that Pings a set of DNS Names / IP addresses and if one of them goes down then its sends an email. Run this as a schedule on any computer at any interval. Just have to make sure that computer has relay permissions on the smtp server.

$servers = "microsoft.com","google.com"
$servers | %{
     if (test-Connection -ComputerName $_ -Count 2 -Quiet )  {
         echo "$_ is online!"
     } else {
         $emailFrom = "PingCheck@yourdomain.com"
         $emailTo = "you@yourdomain.com"
         $subject = "$_ Is down!"
         $body = "Holy shit, you should do something about this."
         $smtpServer = "your smtp server"
         $smtp = new-object Net.Mail.SmtpClient($smtpServer)
         $smtp.Send($emailFrom, $emailTo, $subject, $body)
btanExec ConsultantCommented:
SCOM has the Health Service Heartbeat Failure monitor which is of interest to your use case
When an agent fails to send a heartbeat 4 times, a Health Service Heartbeat Failure alert is generated and the management server attempts to contact the computer by using ping. If the computer does not respond to the ping, a Failed to Connect to Computer alert is generated.
The properties pages for alerts, rules, and monitors will depict useful information and actions that you can take too. https://technet.microsoft.com/en-us/library/hh212798.aspx

Also use Health Explorer to find out which monitor is reacting and to review knowledge about the monitor and possible causes for actions related to it. https://technet.microsoft.com/en-us/library/hh212766.aspx

There is time to to tune the Health Service Heartbeat Failure and Computer Not Reachable monitors further too. The use case of not being flooded by alerts (in the link) due to WAN link connectivity or going to specific group of servers is another common case if server monitored over wide networks...http://myitforum.com/myitforumwp/2013/05/03/scom-heartbeat-failure-alert-tuning-2/
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now