SCOM 2012R@ - Message received during Unit Monitor creation for a Group

Question

Hi Team,

Just need a clarification on this and see what i have done wrong.

I created a Event Monitor and targeted it to a Group.

Then later i was requested to monitor another Event ID on the same Group of servers

So i created another Unit Monitor> Event ID monitor and targeted the same group

And then later I was requested to monitor another Event ID on the same Group

So i created another Event ID unit monitor and targeted to the same group

Is this Method correct?

I received a message pop up during the Unit monitor creation:

Is this something i should be worried about?
Is there a better way to achieve this?

Answer 1

Hi @Saiyad Rahim ,

A good approach is to target your monitors to a class like "Windows Server <version>" , or "Windows Computer", then make sure to leave the monitor disabled (Monitor enabled option must be unchecked), and finally create an override that targets your group (Enabled -> True).

----------

(If the reply was helpful please don't forget to upvote or accept as answer, thank you)

Best regards,
Leon

Answer 2

Hi Leon,

I think I read somewhere in Kevin Holman's Blogs...not to use "Windows Computer" as a target as it is too Broad....and to always try to narrow it down to my "Target"...or am I talking out of context here?

Answer 3

Hi @Saiyad Rahim ,

This is a standard error message and of course it has its explaiantion. You will find many blogs oout there, which covers targeting in SCOM and also targeting basics. I aghev referenced some of them, as well as the related information about targeting a monitor to a group and why this is not a good idea:

From:
SCOM: Objects, Classes, Targeting and You
http://www.opsman.co.za/scom-objects-classes-targeting-and-you/

I’ve included groups in this posting because it can be a common mistake to try and use a group as a target for a rule / monitor this can cause that rule / monitor to not function correctly as the class for a group only exists on a management server, the group will not be enumerated into it’s members from the target selection.

From:
SCOM monitoring basics
https://social.technet.microsoft.com/Forums/systemcenter/en-US/956c237a-0a4e-4cf3-911a-d20768ebecd5/scom-monitoring-basics?forum=operationsmanagerauthoring

In this thread Graham references also some articles, regaridng targeting.

The far bigger problem with this is that the original poster has targetted a rule \ monitor at a group. As we all know, this won't work.

This is also very informative:

OpsMgr Answer This: Do I use classes or groups?
https://opsmgrunleashed.wordpress.com/2008/07/15/opsmgr-answer-this-do-i-use-classes-or-groups/

Last, but not least:

Targeting Series, Part 2: Why targeting a computer group fails
https://techcommunity.microsoft.com/t5/system-center-blog/targeting-series-part-2-why-targeting-a-computer-group-fails/ba-p/340302

----------

(If the reply was helpful please don't forget to upvote or accept as answer, thank you)
Best Regards,
Stoyan

Answer 4

Thanks Leon.
i will change my Group as a Target and replace it with Windows server .

Will read Stoyans resources to get a better understanding of this basic building block of SCOM.
It's so convoluted to us newbies

Answer 5

Thanks Stoyan.
I appreciate the knowledge/guidance i receive in this forum from the likes of Leone and yourself and others who take the time out assist.

And I must say i have picked up a lot from these forums.