Rule hierarchy

I helped out in a problem the other day with rule hierarchy and assigning different computer groups.

The problem was that 4 computer groups had been created with specific rules for each group. They were placed under a master rule group and each rule group had the appropriate computer group applied. However the top rule group had a couple of rules in it and a computer group that contained the other 4 computer groups was assigned to this rule group. The theory being that those 2 rules had to go to all the servers. What happened was that all the rules in each rule group went to every server across all 4 rule groups.

rg-and-cg.jpg

Putting the computer group at the top meant that all the groups underneath inherited this computer group. Although it looks like only one computer group assigned to each rule group there is in fact an invisible group that is inherited from the top. The trouble with the rule group hierarchy in MOM is that it is not really a hierarchy but SQL tables that are displayed like one. Some things are not inherited but computer groups are.

The answer was to create a new sub rule group for all computers and assign the top computer group to that and move the rules into that sub group.

 rg-and-cg-2.jpg

If you look at the Microsoft rules you will see that none of the rule groups have rules at the top level. And that is why.

Advertisements

Comments are closed.

%d bloggers like this: