This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

New to DA

Hi I've just started a new job and my first project is to get desktop authority up and running efficiently. We have a training session booked in next week but ideally id like to have my issues resolved before then.

Basically what I'm trying to do is set up USB rules for certain users, so far i've got it working in the sense that if i log on or my test user logs on we both get a different set of permissions. but if i try and add "everyone" and set their permissions as different from the other 2 it forces "everyones" permissions on myself and my test user overriding any other settings.

Also it only upgrades the agent on the PC's when I log on. Could that be due to the fact that the profile created is called "user-myloginname"? 

Thanks

Parents
  • if the USB lockdown will be by sets of people (such as students and staff, or admins and everyone else) then the rule can be by OU also. You could set the validation logic to: if the user is in the Admin OU then they get no lockdown. If the user is NOT in the Admin OU then they get a lockdown. For large numbers, managing OU's can be easier than group memberships.
Reply
  • if the USB lockdown will be by sets of people (such as students and staff, or admins and everyone else) then the rule can be by OU also. You could set the validation logic to: if the user is in the Admin OU then they get no lockdown. If the user is NOT in the Admin OU then they get a lockdown. For large numbers, managing OU's can be easier than group memberships.
Children
No Data