Groups and nested groups

(imported topic written by mcalvi91)

Would it be possible to include the groups that a nested group is a member of? For example, we have regions made up of various networks. We include multiple regions in a rollout group. So our grouping is as follows.

Location by Subnet (rgn-branch) -> region wkstns -> rollout grp.

It would be good to know from region wkstns group which rollout group it is a part of.

(imported comment written by SystemAdmin)

I’m not sure what you are refering to by “nested group”? Is this a computer group?

Could you elaborate a bit more?

(imported comment written by mcalvi91)

for example, I have 2 automatic groups called ATMs and one called XYZ Region Systems. The ATMs group has a membership property of “Computername Contains ATM”. The XYZ Region Systems group has membership property of “Is not a member of ATMs”. This is how we pull all of the systems that are in a location, except systems with different requirements, for software rollout, patches, etc.

It would be useful to know before deleting or modifying a group to know what other groups that will affect.

(imported comment written by SystemAdmin)

Sounds like you want to look at a list of computers in a particular group and know what other group each of those computers also belong to?

for example, ATM101 in region 500 belongs to two groups. the ATMs group and the 500 Region group.

If you look at performing an action on the ATMs group. You’d want to know that the 500 Region group is affected to?

(imported comment written by mcalvi91)

close, but looking for more of a if I change the ATMs group, what other groups will it affect.

(imported comment written by SystemAdmin)

Ah i understand now, and my example was wrong according to your description, sorry bout that. ATM101 would never become a member of the 500 Region group because it is already a member of the ATMs group.

and since you have the second group setup as a dependancy of the ATMs group, if you change or delete the ATMs group it will expose alot more computers to becoming a member of the Region groups.

I’ll look at the different situations:

Action: You delete the ATMs group.

Result: all the groups that have the dependancy “Is not a member of ATMs” would register everyone because this would equat to true for everyone.

Action: You change the qualifications of being a member of the ATMs group.

This is the action that you want to know what computers will remain and the ones that don’t which group they move to?

(imported comment written by JackCoates91)

another way to think of automatic group memberships is that they are actually tags. You can certainly define them so that they are nested, inclusive, or exclusive of each other, but you can also choose not to.

not real code, just an example:

Region 500: network gateway == router500

ATM: os == XPE

ATMs in Region 500: group membership == “Region 500” and group membership == “ATM”

non-ATMs in Region 500: group membership == “Region 500” and group membership != “ATM”

If your groups are defined in this way, deleting the ATM group would remove the ATM group membership from all XP embedded systems. This would not affect the Region 500 group, but would empty the group “ATMs in Region 500” because it would no longer be relevant for any machines. “non-ATMs in Region 500” would be unaffected.