MP Authoring / Group Creation weirdness

I've been creating an MP in XML and have come across a very weird problem. I was creating a static membership Group that will contain one server. Seems easy enough right.... here is part of the code I was using (the important part for this blog anyway)...

Now the strange part happens after I import the MP into the console.

Look at the Group Membership rules in the UI (remember this is a static entry membership group):

OpsMgr sees this rule as a Dynamic Entry rule not a static membership rule, and what more is it's using the Relationship type as the Qualifier for the group, not the server name in the <MonitoringObjectID> tags. This group membership is empty.

Now if I change the <MonitoringObjectID> tag from the server name to the GUID of the object I'm trying to add to the group look what happens:

Here's the change...

Here's the outcome...

It now sees the Group membership correctly, as a static entry not a dynamic one, and it adds the correct server to group.

What this means to all the MP authors out there, is that as you create your MPs if you need a static membership group (and of course you are building your MP in XML) make sure you use the GUID of the objects you want in the Group, not the server name.

Interested in our training offerings, see http://infrontconsulting.com/

Read the complete post at http://david-stclair.spaces.live.com/Blog/cns!112A71B19678F08D!347.entry