What kind of groups can be used to scope User roles?
Hello,
today we made an interesting discovery: We created a group in an unsealed MP with only explicit members. Than we used this group to scope a user role. Afterwards we changed the group and included dynamic members as well (so explicit AND dynamic members).
The group still worked as expected but:
It was not visible in the list of available groups in the user role wizzard anymore, so we could not select it!
As soon as we remove the dynamic membership from the rule, the group was visible (and selectable) again ...
We could not find any documentation about the necessary group structure for beeing used in User role scopes. Can somebody explain this behaviour?
Thank you for any hints,
Dirk
November 16th, 2011 5:03pm
i failed to reproduce your scenario in my lab.
could you share group discovery xml? likely issue is related to type of objects you choose.
do you have any objects which may be associated with any distributed application?
Free Windows Admin Tool Kit Click here and download it now
November 26th, 2011 3:57pm
Hi Pavel,
of course :)
This is the discovery section with the working group (only explicit Members):
>>>>
<Discovery ID="UINameSpacead5005aa367a4b008d94467742429d50.Group.DiscoveryRule" Enabled="true" Target="UINameSpacead5005aa367a4b008d94467742429d50.Group" ConfirmDelivery="false" Remotable="true" Priority="Normal">
<Category>Discovery</Category>
<DiscoveryTypes>
<DiscoveryRelationship TypeID="MicrosoftSystemCenterInstanceGroupLibrary6172210!Microsoft.SystemCenter.InstanceGroupContainsEntities" />
</DiscoveryTypes>
<DataSource ID="GroupPopulationDataSource" TypeID="SC!Microsoft.SystemCenter.GroupPopulator">
<RuleId>$MPElement$</RuleId>
<GroupInstanceId>$MPElement[Name="UINameSpacead5005aa367a4b008d94467742429d50.Group"]$</GroupInstanceId>
<MembershipRules>
<MembershipRule>
<MonitoringClass>$MPElement[Name="Windows!Microsoft.Windows.Server.Computer"]$</MonitoringClass>
<RelationshipClass>$MPElement[Name="MicrosoftSystemCenterInstanceGroupLibrary6172210!Microsoft.SystemCenter.InstanceGroupContainsEntities"]$</RelationshipClass>
<IncludeList>
<MonitoringObjectId>a39d0ea3-2658-b0b4-b567-8d3f29f1a9a5</MonitoringObjectId>
<MonitoringObjectId>2c94c7a9-50d5-e239-8360-0aaf20924505</MonitoringObjectId>
<MonitoringObjectId>b2b16252-b3f1-a412-b485-8418ac23e343</MonitoringObjectId>
</IncludeList>
</MembershipRule>
<MembershipRule>
<MonitoringClass>$MPElement[Name="MicrosoftWindowsClusterManagementLibrary6067200!Microsoft.Windows.Cluster.HostedGroup"]$</MonitoringClass>
<RelationshipClass>$MPElement[Name="MicrosoftSystemCenterInstanceGroupLibrary6172210!Microsoft.SystemCenter.InstanceGroupContainsEntities"]$</RelationshipClass>
<IncludeList>
<MonitoringObjectId>ba9228ae-32f5-b139-e453-7b936916e39c</MonitoringObjectId>
<MonitoringObjectId>9dd51c31-2263-9ea8-e673-457b08a81770</MonitoringObjectId>
<MonitoringObjectId>34cfa0de-9ba1-b0f1-89df-345c7daeccff</MonitoringObjectId>
<MonitoringObjectId>e06d4953-da45-988c-d004-010528d2bc16</MonitoringObjectId>
<MonitoringObjectId>b237065b-f967-907f-47fc-19e9ed028bdb</MonitoringObjectId>
<MonitoringObjectId>7995d9fe-b9a8-4829-8455-3cd73c566f23</MonitoringObjectId>
</IncludeList>
</MembershipRule>
<MembershipRule>
<MonitoringClass>$MPElement[Name="MicrosoftWindowsClusterManagementLibrary6067200!Microsoft.Windows.Cluster.Group"]$</MonitoringClass>
<RelationshipClass>$MPElement[Name="MicrosoftSystemCenterInstanceGroupLibrary6172210!Microsoft.SystemCenter.InstanceGroupContainsEntities"]$</RelationshipClass>
<IncludeList>
<MonitoringObjectId>01b5d45f-bf6b-c3a9-2aa7-42e7f8a75d9b</MonitoringObjectId>
<MonitoringObjectId>7a6fad75-2106-b5fc-b2e7-ea095b9f9ea9</MonitoringObjectId>
<MonitoringObjectId>30f4b555-12af-c794-0b2a-1d571bc955c0</MonitoringObjectId>
</IncludeList>
</MembershipRule>
</MembershipRules>
</DataSource>
</Discovery>
</Discoveries>
</Monitoring>
<<<<<
And this is the Discovery with the dynamic Membership (a Cluster with Name XXXYYYZZZ):
>>>
<Discovery ID="UINameSpacead5005aa367a4b008d94467742429d50.Group.DiscoveryRule" Enabled="true" Target="UINameSpacead5005aa367a4b008d94467742429d50.Group" ConfirmDelivery="false" Remotable="true" Priority="Normal">
<Category>Discovery</Category>
<DiscoveryTypes>
<DiscoveryRelationship TypeID="MicrosoftSystemCenterInstanceGroupLibrary6172210!Microsoft.SystemCenter.InstanceGroupContainsEntities" />
</DiscoveryTypes>
<DataSource ID="GroupPopulationDataSource" TypeID="SC!Microsoft.SystemCenter.GroupPopulator">
<RuleId>$MPElement$</RuleId>
<GroupInstanceId>$MPElement[Name="UINameSpacead5005aa367a4b008d94467742429d50.Group"]$</GroupInstanceId>
<MembershipRules>
<MembershipRule>
<MonitoringClass>$MPElement[Name="Windows!Microsoft.Windows.Server.Computer"]$</MonitoringClass>
<RelationshipClass>$MPElement[Name="MicrosoftSystemCenterInstanceGroupLibrary6172210!Microsoft.SystemCenter.InstanceGroupContainsEntities"]$</RelationshipClass>
<IncludeList>
<MonitoringObjectId>a39d0ea3-2658-b0b4-b567-8d3f29f1a9a5</MonitoringObjectId>
<MonitoringObjectId>2c94c7a9-50d5-e239-8360-0aaf20924505</MonitoringObjectId>
<MonitoringObjectId>b2b16252-b3f1-a412-b485-8418ac23e343</MonitoringObjectId>
</IncludeList>
</MembershipRule>
<MembershipRule>
<MonitoringClass>$MPElement[Name="MicrosoftWindowsClusterManagementLibrary6067200!Microsoft.Windows.Cluster.HostedGroup"]$</MonitoringClass>
<RelationshipClass>$MPElement[Name="MicrosoftSystemCenterInstanceGroupLibrary6172210!Microsoft.SystemCenter.InstanceGroupContainsEntities"]$</RelationshipClass>
<IncludeList>
<MonitoringObjectId>ba9228ae-32f5-b139-e453-7b936916e39c</MonitoringObjectId>
<MonitoringObjectId>9dd51c31-2263-9ea8-e673-457b08a81770</MonitoringObjectId>
<MonitoringObjectId>34cfa0de-9ba1-b0f1-89df-345c7daeccff</MonitoringObjectId>
<MonitoringObjectId>e06d4953-da45-988c-d004-010528d2bc16</MonitoringObjectId>
<MonitoringObjectId>b237065b-f967-907f-47fc-19e9ed028bdb</MonitoringObjectId>
<MonitoringObjectId>7995d9fe-b9a8-4829-8455-3cd73c566f23</MonitoringObjectId>
</IncludeList>
</MembershipRule>
<MembershipRule>
<MonitoringClass>$MPElement[Name="MicrosoftWindowsClusterManagementLibrary6067200!Microsoft.Windows.Cluster.Group"]$</MonitoringClass>
<RelationshipClass>$MPElement[Name="MicrosoftSystemCenterInstanceGroupLibrary6172210!Microsoft.SystemCenter.InstanceGroupContainsEntities"]$</RelationshipClass>
<IncludeList>
<MonitoringObjectId>01b5d45f-bf6b-c3a9-2aa7-42e7f8a75d9b</MonitoringObjectId>
<MonitoringObjectId>7a6fad75-2106-b5fc-b2e7-ea095b9f9ea9</MonitoringObjectId>
<MonitoringObjectId>30f4b555-12af-c794-0b2a-1d571bc955c0</MonitoringObjectId>
</IncludeList>
</MembershipRule>
<MembershipRule>
<MonitoringClass>$MPElement[Name="MicrosoftWindowsClusterManagementLibrary6067200!Microsoft.Windows.Cluster.NodeRole"]$</MonitoringClass>
<RelationshipClass>$MPElement[Name="MicrosoftSystemCenterInstanceGroupLibrary6172210!Microsoft.SystemCenter.InstanceGroupContainsEntities"]$</RelationshipClass>
<IncludeList>
<MonitoringObjectId>75afec93-9224-1284-3c68-91a52b06284e</MonitoringObjectId>
<MonitoringObjectId>e048dd10-9157-e397-56fc-2e06b4357c26</MonitoringObjectId>
</IncludeList>
</MembershipRule>
<MembershipRule>
<MonitoringClass>$MPElement[Name="MicrosoftWindowsClusterManagementLibrary6067200!Microsoft.Windows.Cluster.Network"]$</MonitoringClass>
<RelationshipClass>$MPElement[Name="MicrosoftSystemCenterInstanceGroupLibrary6172210!Microsoft.SystemCenter.InstanceGroupContainsEntities"]$</RelationshipClass>
<IncludeList>
<MonitoringObjectId>466186b6-da3d-d7d6-f668-2b87e4384afe</MonitoringObjectId>
<MonitoringObjectId>a015e40c-19c5-c265-2bd7-37602a2ad905</MonitoringObjectId>
<MonitoringObjectId>42cca344-7089-31ed-b41e-823d824d878e</MonitoringObjectId>
</IncludeList>
</MembershipRule>
<MembershipRule>
<MonitoringClass>$MPElement[Name="MicrosoftWindows2003ClusterManagementLibrary6067200!Microsoft.Windows.2003.Cluster.Monitoring.Service"]$</MonitoringClass>
<RelationshipClass>$MPElement[Name="MicrosoftSystemCenterInstanceGroupLibrary6172210!Microsoft.SystemCenter.InstanceGroupContainsEntities"]$</RelationshipClass>
<IncludeList>
<MonitoringObjectId>a4831108-3959-c0f2-52ad-67b75e88b967</MonitoringObjectId>
<MonitoringObjectId>fcad6008-3de3-b4d4-218c-d40c2ddda3fc</MonitoringObjectId>
</IncludeList>
</MembershipRule>
<MembershipRule>
<MonitoringClass>$MPElement[Name="MicrosoftWindowsClusterLibrary6172210!Microsoft.Windows.Cluster"]$</MonitoringClass>
<RelationshipClass>$MPElement[Name="MicrosoftSystemCenterInstanceGroupLibrary6172210!Microsoft.SystemCenter.InstanceGroupContainsEntities"]$</RelationshipClass>
<Expression>
<RegExExpression>
<ValueExpression>
<Property>$MPElement[Name="MicrosoftWindowsClusterLibrary6172210!Microsoft.Windows.Cluster"]/Name$</Property>
</ValueExpression>
<Operator>ContainsSubstring</Operator>
<Pattern>XXXYYYZZZ</Pattern>
</RegExExpression>
</Expression>
</MembershipRule>
</MembershipRules>
</DataSource>
</Discovery>
>>>
We don't use DAs so far, so none of the objects is part of a custom DA.
Dirk
November 27th, 2011 2:22am
the same, i constructed group with the same population rule, can't reproduce.
when your group disappears, can you see it in SCOM authoring>groups?
and can you see it from powershell?
Get-MonitoringObjectGroup | %{$_} | select DisplayName
Free Windows Admin Tool Kit Click here and download it now
December 10th, 2011 4:01pm
the same, i constructed group with the same population rule, can't reproduce.
when your group disappears, can you see it in SCOM authoring>groups?
and can you see it from powershell?
Get-MonitoringObjectGroup | %{$_} | select DisplayName
December 10th, 2011 4:01pm
This topic is archived. No further replies will be accepted.
Other recent topics
