10-13-2005 02:48 PM - edited 03-09-2019 12:43 PM
I've tried creating a user-state policy in CSA 4.5 which makes the Agent UI available for a specific group called "PC Admins", but it does not work.
If I list the user accounts individually, then the policy does work.
I'm refraining from using the built in "Administrators" (local admins) group defined by CSA because some machines in our environment require local admin rights for a REGULAR end user due to legacy applications, but I don't want them to have the Agent UI available.
That is why we have a separate PC Admins group.
Has anyone gotten User-State policies to work with groups?
10-14-2005 02:00 PM
bump
10-17-2005 12:05 AM
Maybe you could show us your group definition in the user state policy that you created, that would help in finding the problem. Also, check the diagnostic in the host view on the csamc to see if the client has detected that it is in that specific group.
10-26-2005 02:30 PM
i have the user state set configured as:
users matching:
groups matching:
10-28-2005 11:05 AM
Use the windows SID for the group not the name of the group.
10-28-2005 11:08 AM
i've tried this. does the sid have to be in brackets?
ex. <"sid">
or just the sid?
11-01-2005 11:12 AM
bump
11-02-2005 05:11 AM
i don't think you need brackets, either for the sid or the groupname option
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide