In the last post we discussed about event based monitoring options SCOM provides with Monitors. You can find it here: SCOM Event Based Monitoring – Part 1 – Monitors In this post we are going to discuss the event based monitoring options using SCOM Rules. Basically the highlighted options in the image below: As we
In this post I’m discussing about the possibilities SCOM provides with event detection monitoring using monitors. I’ve written a similar blog for creating services, which you can see here: SCOM BASIC SERVICE MONITOR VS. WINDOWS SERVICE TEMPLATE Alright, so just go to Authoring -> Expand Management Pack Objects -> Monitors -> Create a Monitor ->
Every now and then I’ve seen questions regarding this on the Technet forums. The most usual question is “A service XXX failure alert is being generated by a server where this service isn’t even present! What’s going on?” The Basic Service Monitor: This is a simple monitor that simply puts an instance of the monitor
I am working on one of the projects and as a part of it I needed to create some console tasks that would run a Powershell script to do the stuff I want. I knew that it was no problem for a script a line of two long, but any more than that and it
Here we’re going to talk about something very important and basically the root of everything. Without this your SCOM does not exist. Essentially, this is what your whole SCOM setup is called – The Management Group. Yet, this is not something you’d work with daily. In fact, in most environments it’s just an install-and-forget kinda
