So, I have a GPO, which runs a quick start up script to delete locally installed IP printers from all machines on our AD domain during computer start up. This works great...the issue appears when we try to exempt a few machines from this (a few small offices without print servers.)
I have created a global security group, and put the computer accounts (since this is a startup, not a login script) into the group. I then set permissions on the GPO to deny access to that group. For some reason, this has no effect. It also has no effect if I set deny permissions for that group on the script itself.
Interestingly, though, if I cut out the group, and set deny permissions on the GPO or script for the computer account directly, permissions are denied properly.
These issues persist across multiple "gpupdate /force" commands, as well as reboots.
Am I missing something about how computer accounts group group sids? Why are the group based deny permissions not working?
I then set permissions on the GPO to deny access to that group.
Wait, what? Explain that, please.gpresult /R
show? You can update your question with the relevant output.