- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
01-25-2024 04:54 AM
We have a privilege management policy that has an AD group as target. Any devices in that group should have this policy active.
We notice lately that apparently the agent is not able to determine group membership and activates this policy event though that device is not a member of that group. A Request Settings or reboot solves the problem, but this situation should not happen. This policy should never be active if the AD group can not be solved.
Anybody else has this problem?
01-25-2024 05:56 AM
There is a Known Issue (bug) that has been around for a while that is related to this. See KI#00017163: The policy won't apply if the agent cannot resolve the selected AD group (site.com). While that bug indicates that the policy is not applied if the agent can't resolve the AD group, I would not be surprised if there is more to the bug and it also causes the behaviour you are seeing in some instances. My recommendation to you would be to open a support case providing all the specifics of your issue (including a SupportInfo trace from an impacted agent) but also mention this similar Known Issue article. Hopefully Support can help determine if it's the same bug, this is a new bug, or just something specific to your configuration that can be resolved.
-rwm
PS. I have not personally seen this occur in my setup.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

