policy bugs in 4.1.0

[Ian]

Hey guys. Love the program, having some difficulties with permanent policies though. Just so you know before I start, I'm talking about XP Pro sp2 machines on a windows domain, and not using roaming profiles.

Having trouble with applying permanent policies that restrict students to running programs located only on c:\*. We are trying to prevent the running of games from flash drives that students plug in (but not deny access to these drives altogether). Every now and then, winlogon.exe is denied by abtutor and causes problems. With this same policy, we have machines that will randomly start to reboot themselves (logged in or not), without being so gracious as to allow students to save their progress before closing their programs. This last problem also occurs with a similar policy which explicitly denies access to programs on d:\*, e:\*, f:\* etc.

Also, sometimes after logging out we have machines that have the username and password fields "greyed out" and must also be rebooted before anyone can log in.

Any help would be much appreciated. Thanks.

[meastaugh1]

I realise this doesn't address the ABTutor issue, but since you're running a domain with XP clients, you might want to take a look at [url=http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/rstrplcy.mspx]Software restrictions policies[/url]: policies which allow you to specify which locations/executables are allowed/prohibited. That should do what you want.