Screensaver Password Policy Doesn't Work

From: Ryan Provost (ryan_provost@bat.com)
Date: 06/25/02 

From: ryan_provost@bat.com (Ryan Provost)
Date: 25 Jun 2002 07:38:13 -0700

Okay, I'm a bit confused on this one. Let me explain the scenario. I
have about 2000 Windows XP Pro workstations to roll-out in my company,
using a Windows 2000 Active Directory domain in native mode. Corporate
policy requires screensavers on each desktop, and these screensavers
must be password protected. To accomplish this, I have configured the
system policies to password protect the screen saver. It does not seem
to be working. The screen saver, also configured by the policy, does
indeed activate after the set timeout duration, but the console does
NOT lock as it should. I have no idea why this is not working.

After poking around on the internet for some answers, I stumbled
across a few newsgroup posts by people experiencing much the same
problem, yet no answer has been given ... at least that I could find.
So I decided to post for myself in the hopes of stirring up an answer.

I have updated the .ADM templates in Active Directory to the new
Windows XP templates, and most of the XP-specific settings do in fact
work. The policy template sets the following registry key for screen
saver password:

HKCU\Software\Policies\Microsoft\Windows\Control Panel\Desktop
Value: ScreenSaverIsSecure = 1

When I dig into the Windows registry, and search for this same value I
find another duplicate value in a different location.

HKCU\Control Panel\Desktop
Value: ScreenSaverIsSecure = 0

Note that in this location the value is set to 0, or 'Off'. If I
manually set the value to 1, or 'On', the console still does not lock
itself. I cannot figure out what is going wrong here. Is the policy
template setting the wrong value? Is there something else at fault
that I have no considered? Any help that anyone could offer on this
subject would be most appreciated. I am at wits end.

TIA, Ryan Provost

Relevant Pages

  • Re: Screensaver Password Policy Doesnt Work
    ... >> have about 2000 Windows XP Pro workstations to roll-out ... >> policy requires screensavers on each desktop, ... >> I have updated the .ADM templates in Active Directory ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Screensaver Password Policy Doesnt Work
    ... > using a Windows 2000 Active Directory domain in native mode. ... > policy requires screensavers on each desktop, ... The screen saver, also configured by the policy, does ... > Windows XP templates, and most of the XP-specific settings do in fact ...
    (microsoft.public.windowsxp.security_admin)
  • Software Installation works for 2000, not for XP
    ... Used below method to apply win XP templates to Windows ... Directory GPO to support the new Windows XP policy ... settings, Windows 2000-based clients ignore any Windows ...
    (microsoft.public.win2000.group_policy)
  • Re: Screensaver Password Policy Doesnt Work
    ... I've got the same problem on Windows XP Professional computers. ... >> policy requires screensavers on each desktop, ... The screen saver, also configured by the policy, does ... >> Windows XP templates, and most of the XP-specific settings do in fact ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Screensaver Password Policy Doesnt Work
    ... I've got the same problem on Windows XP Professional computers. ... >> policy requires screensavers on each desktop, ... The screen saver, also configured by the policy, does ... >> Windows XP templates, and most of the XP-specific settings do in fact ...
    (microsoft.public.windowsxp.security_admin)
Quantcast