Prevent users from bypassing screensaver policy via REGEDIT

We have a GPO that defines screen saver settings for our users, and prevents them from modifying those settings via the Windows GUI. However, some of our users have figured out that they can update the settings to those of their liking via REGEDIT.

We are looking for ways to prevent them from modifying these keys, or if this cannot be prevented, a mechanism to automatically revert the keys back to their original values if they are modified. We'd prefer not to use any third party software to do this. The keys in question are:

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Control Panel\Desktop]
"ScreenSaverIsSecure"="1"
"ScreenSaveActive"="1"
"SCRNSAVE.EXE"="Policy.scr"
"ScreenSaveTimeOut"="900"

Any suggestions would be appreciated.
LVL 1
TWCMILAsked:
Who is Participating?
 
oBdAConnect With a Mentor Commented:
By default (and for the obvious reasons), users are not allowed to write in the "...\policies\..." registry keys (just chekc the permissions on HKCU\Software\Policies - only Administrators and System have write access).
That means that your users are local administrators on their machines, and that means that you can't prevent them from doing what an administrator is supposed to do on a machine: anything they want.
Yes, you can block reg.exe and regedit.exe. It'll take them about half a day to figure out that the registry can be changed with a VB script.
The GPO will by default be reset about every 90 minutes. Hopefully, after changing the settings back manually often enough, they'll just get tired of it.
0
 
Stewart BeelConnect With a Mentor Senior Technical AnalystCommented:
In a GPO set the following to enabled:

User Configuration > Administrative Templates > System > Prevent access to registry editing tools

This will prevent users from being able to start regedit
0
 
networkadminkjmcCommented:
also user permissions on the local machine,
0
 
AwinishCommented:
Domain user should not be allowed to modify registry settings.
Block it using GPO.

http://www.ehow.com/how_6056513_disable-tools-per-group-policy.html
0
 
TWCMILAuthor Commented:
Thanks for the help, and sorry about the delay. Blocking the reg editing tools will help, but oBdA made a good point about Admin rights -- ultimately that is the issue we need to address.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.