(imported topic written by suresh.h@techsa.net)
Hi Team,
we are still observing that systems are not added to the automatic group which is created based on the subnet.
kindly help.
Regards
Suresh
(imported topic written by suresh.h@techsa.net)
Hi Team,
we are still observing that systems are not added to the automatic group which is created based on the subnet.
kindly help.
Regards
Suresh
(imported comment written by PeterLoer)
Hi Suresh,
Is there a previous thread on this topic you could point me to for context?
If not, could you outline what steps you are taking to create this automatic group and how it is failing?
thanks,
peter
(imported comment written by MBARTOSH)
The problem I have is that computers don’t always drop out of an automatic group when they are supposed to. I have to create a new group in order to get rid of the computers that are not supposed to be in the group.
(imported comment written by brolly33)
Keep in mind that group membership is processed on the endpoint. If the last time the endpoint sent a report to the server, it was a member of the group, then the console will continue to show that endpoint as a member until the endpoint sends a report to the server indicating otherwise.
(imported comment written by MBARTOSH)
Yes but if the endpoint is online it should eventually send the information that it is no longer a member, but I often see machines online that are not dropping out of a group.
(imported comment written by PeterLoer)
Probably the first step to debug this would be to create a retrieved property with the same relevance that is being used to determine the automatic group membership, and see if that is coming back as expected for the computer in question. (for instance, it could be that those machines still think they are in the subnet in question)
If that doesn’t help point to the issue, you may want to contact support for assistance with step-by-step debugging.
cheers,
peter
(imported comment written by suresh.h@techsa.net)
Hi Team,
thanks for reply
Crated new group subset property same issue
all machine are same subnet
steps you are take to creating the automatic group (
tools
create automatic group name xxxxxxx computer property select Subnet address
Contains
and 10.0.0.0 it the subnet address unable to report pc in the group
(imported comment written by PeterLoer)
Hi Suresh,
Hmm… we just ran through what I think are the same steps here in the lab and everything seemed to work fine for us. We had a bunch of machines all in the 10.10.50.0 subnet, created an automatic group with “contains 10.10.50.0” for the subnet property, and then if we change the subnet on one of the machines it drops out of the group as expected.
One thought that did occur to me… is it possible that perhaps some of your machines are in multiple subnets? If that were the case (due to having multiple physical or virtual network adapters), you might have changed the subnet on one of the adapters, but the machine would still be relevant to the group due to other adapters still being in the specified subnet.
(I’ve attached a screenshot showing a computer list in which we created this situation with one of the computers and so the Subnet Address retrieved property shows … you can then hover over to see the list of different subnets the computer is in).
cheers,
peter
(imported comment written by suresh.h@techsa.net)
Hi peter,
Thanks your reply.
In my organization we have created 20 groups. Some of the machine is reporting properly in the group.
We created 4 groups property selected OS it’s reporting perfectly no issue.
I know that
multiple result
will not report to the group.
I thing so it’s bug.
Kindly help
Regards
Suresh H
(imported comment written by PeterLoer)
Sounds like it might be something trickier than we will be able to get to the bottom of here, then. I would recommend contacting support for help on this.
cheers,
peter