SCOMfaq.ch

I don’t like to clean up very much, but there are certain cases where it really makes fun to clean up. Especially if there a Non-Microsoft product, Powershell and SCOM involved.

In my case a customer decided to replace his Nagios system through SCOM 2012. Cool!!!

Because Nagios also uses an agent for monitoring, one of my first things I did was to write a script to uninstall the Nagios agent from several windows systems.

The idea is to provide a text file containing server names which the script will use to check if the Nagios agent (service) is installed or not. If the service is installed it will uninstall the software. I don’t delete the source files though. I found the sources in the C:\NagiosClient\WindowsClient directory. The “NSClient++.exe” is the actual installation file for the Nagios agent.

Continue reading →

Have you ever wanted being notified about new Operations Manager KB article? Your answer will be yes I already have RSS-Reader and stuff like that. But is that cool? Is that the geeky way to do things? Hmm…no. Because I wanted to fool around with Orchestrator and SCOM so I built a Runnbook which sends me an alert if there is a new KB article .

Continue reading →

There is at least one Runbook each SCOM responsible must have. Are you wondering which? Well, I am sure you are always aware of what kind of alert you are closing. Is this alert beeing generated by a rule or by a monitor. If it is generated by a rule you just can close the alert and you don’t have to care about anything. But if the alert is being generated by a monitor you always facing the problem that if you just close the alert itself your monitor will often stay in a critical or warning state. A good practice to close alerts from monitors is to fix the problem itself in your IT infrastructure and then go to the health explorer and reset the monitor. After that the alert will also close.

A similar problem occurs in a more advanced situation. Let’s assume System Center Operations Manager is generating incident tickets in System Center Service Manager through the connector. After the ticket has been closed in Service Manager the alert in Operations Manager will also close. But what if the alert has been generated by a monitor? Well, Service Manager does not reset the monitors in Operations Manager.

For both situation you could build a Runbook in System Center Orchestrator .

Continue reading →