Software Restrictions not working on one lab, denies every program
I'm implementing Software Restriction Policies for student accounts in our school and I'm having issues with one of the labs.
So far, here's what I've done. I've created an initial test policy with the default rule as disallow, and then added paths as needed [such as network application UNC paths and Program Files, and the default system paths]. These work great on every other lab and system in the school. Using a student test account with that policy enabled, I'm allow to only run what's installed already on the computer, and I can't run any executables from USB drives, student H drives, my documents folder, desktop, user profile, and other locations besides Program Files and application drives.
On this one lab however [all lab computers are the same image, different image per lab], the computers won't allow a student with this policy enabled to run ANY application. Internet explorer works, and that's about it. Everything else, including Notepad, fails to launch and says that there's a software restriction policy preventing it. I logged into another computer in the lab just to make sure there wasn't something going on with that exact computer, but I got the same results on the next machine.
When I log onto the machine as a local administrator and pull up the Event Viewer, I see the following entry for Software Restriction:
Access to C:\Documents and Settings\Test-Student\Start Menu\Programs\Accessories\Notepad.lnk has been restricted by your Administrator by the default software restriction policy level.
Sure, .LNK is an extension that's included in the default designated file types list in the policy, but why isn't it affecting any other system builds in the school?
I really want to roll this out because students are starting to use tor for web browsing and playing games brought in via USB drives. This would work perfectly for preventing all of that, and it works for every system. But this lab of 10 computers doesn't work with it, so I can't roll out the policy until I find out what's causing it. Any advice would be greatly appreciated. Please let me know if anyone needs more information.