It’s my understanding that membership in a manual group is governed by a specific client setting that happens to share the name of the manual group. For instance, creating a manual group called “New Manual Group” with specific members actually creates actions in the background that push out a setting called
__Group_0_New Manual Group to the clients in the group. This is why you see manual groups in the registry.
I do not believe automatic group membership is actually stored in the registry.
Here is some relevance that will get you the names of all the computer groups the computer is a part of:
values of headers "subject" of relevant fixlets whose (value of header "X-Fixlet-Type" of it = "ComputerGroup") of sites
You can modify
sites to be more specific with
site <string> (the name of the site).
This breaks down into pulling the sites in memory on the client:
Get the relevant fixlets in the site:
relevant fixlets of <site>
Filter out everything except for computer groups:
relevant fixlets whose (value of header "X-Fixlet-Type" of it = "ComputerGroup") of sites
We now have all of the groups the computer is a member of (relevant groups).
Get the title of the computer groups:
values of headers "subject" of <fixlet>
You should be careful doing this – normally a reason people try to do this is to put computer groups in fixlet/baseline relevance instead of targeting the group.
In addition, by using the name of the group instead of the ID you run into a particularly volatile situation that folks may not be use to where changing the name of something in the console can actually break something on a client.