Re: Screensaver Password Policy Doesn't Work
From: Josh Bell (josh.bell@guidancesoftware.com)
Date: 08/28/02
- Next message: Kyros: "Help! I need to put back my default Administrator account!"
- Previous message: Jeff: "Removing e-mail pop-ups, Help!"
- In reply to: Eric Perlin [MS]: "Re: Screensaver Password Policy Doesn't Work"
- Next in thread: Mike Dwyer: "Re: Screensaver Password Policy Doesn't Work"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Josh Bell" <josh.bell@guidancesoftware.com> Date: Tue, 27 Aug 2002 19:11:17 -0700
This is a MAJOR oversight on Microsoft's part. When will
the fix be released? If we're going to have to wait until
SP1 comes out, when will that be?
How can we be expected to embrace Windows XP when such a
basic, security-centric feature doesn't work? And is
there a knowledgebase article on this? I've done search
after search with no luck, it would seem from what I've
found here that Microsoft is aware of the problem but
isn't admitting it publicly.
>-----Original Message-----
>That's a bug in XP. SP1 will take care of it.
>
>--
>Eric Perlin [MS]
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>"Ryan Provost" <ryan_provost@bat.com> wrote in message
>news:700a0e64.0206250638.24f4e682@posting.google.com...
>> 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
>
>
>.
>
- Next message: Kyros: "Help! I need to put back my default Administrator account!"
- Previous message: Jeff: "Removing e-mail pop-ups, Help!"
- In reply to: Eric Perlin [MS]: "Re: Screensaver Password Policy Doesn't Work"
- Next in thread: Mike Dwyer: "Re: Screensaver Password Policy Doesn't Work"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
