Screensaver Password Disabled but still requiring password

I have a problem with the screensaver that keeps requiring a password to get
back to the desktop. I have GPOs in place to disable the screensaver
password, and the GPResults wizard and RSOP both show that the password is
disabled, but on some machines, it still locks and a password is required.

Here's what we have:
Windows Server 2003 R2 SP2 domain
Windows XP SP2 clients (all computers get the same standard image)

Group Policy 1 on users' OU for all users that:
* enables the screensaver
* sets the marquee screensaver
* sets the timeout period to 10 minutes
* password protects the screensaver

Group Policy 2 on specific workstation OU that:
Computer Settings:
* User Group Policy loopback processing mode enabled, set to Merge
User Settings:
* set the timeout period to 30 minutes
* screensaver password protect is disabled

Like I said, the gpresults wizard and RSOP both show that Group Policy 2 is
applying the screensaver settings, and that the password requirement is
disabled. But, some machines still lock (not a frozen lock, but a
ctrl-alt-del lock) and require a password. By the way, ctrl-alt-del is
disabled everywhere.

Any ideas what could be causing the screensaver locks? If you need any more
information, please let me know.

You might look at the registry setting.

HKEY_CURRENT_USER\Control Panel\Desktop
Type Reg_Sz
ScreenSaverIsSecure
values 1/0 (0=disabled)

This is the exact same problem we're having with some of our machines. Most work correctly. Unfortunately the registry settings you refer to are set exactly that way - ScreenSaverIsSecure = 0. A co-worker suggested an intermittent latency issue would cause the GPOs to not be processd correctly. However, rebooting these machines is a regular occurrance throughout the day. Any other suggestion?

Quote:

---

Originally Posted by taylok11

This is the exact same problem we're having with some of our machines. Most work correctly. Unfortunately the registry settings you refer to are set exactly that way - ScreenSaverIsSecure = 0. A co-worker suggested an intermittent latency issue would cause the GPOs to not be processd correctly. However, rebooting these machines is a regular occurrance throughout the day. Any other suggestion?

---

I think that you have to link the GPO to the OU which contains the TS account, and configure loopback processing of the policy, with the http://support.microsoft.com/?kbid=231287. You can also deny administrators the right to "apply this policy" in the security filtering of the GPO. See: http://support.microsoft.com/?kbid=816100