Re: Screensaver GPO

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: David Levine (davidlevine_at_hotmail.com)
Date: 03/01/04


Date: Mon, 1 Mar 2004 11:26:30 -0500

Hi Debbie,

And for other readers, let me make this more specific.

In this GPO we have a total of 5 settings:

1. Computer
Config/WindowsSettings/SecuritySettings/LocalPolicies/SecurityOptions-Intera
ctivelogon:do not require CTRL-ALT-DEL- Disabled (this is to counteract a
local policy setting that was part of our ghost image)
2. UserConfig/AdminTemplates/ControlPanel/Display Password protect the
screensaver-Enabled
    3. Screensaver- Enabled
    4. Screensaver executable name- logon.scr (which we know to be in the
same location (C:\Windows\system32) on every system.
    5. Screensaver timeout- Enabled- 900 seconds

The first setting in this GPO is working properly- we have observed its
effect and can see it when the RSoP is run. But not the rest.
So, it's weird, huh?

thanks,
Dave

"Debbie" <daluebb@monsanto.com> wrote in message
news:492401c3ff9b$7ff8ee60$a001280a@phx.gbl...
> Dave,
> We've been trying to decide how to configure this setting
> for our office as well. A couple of things I've found.
> 1. If you enable the password protect policy, but the
> local computer doesn't have a screen saver selected, it
> will not take effect. 2. If you select a screen saver
> from the policy, that screen saver must exist in the same
> directory on every computer for it to work.
> Hope this helps some.
>
> >-----Original Message-----
> >I've seen plenty of postings on this, but no
> solutions ... We have an AD
> >domain with mostly 2000 Server SP4 servers and a mixed
> environment of 2000
> >and XP Pro clients. We don't have a lot of domain GPOs
> but the ones we do
> >have are working properly. We tried to set up a policy
> that would activate a
> >password protected screensaver to lock down machines that
> people neglect to
> >log off from. I think we enabled all the necessary
> policies properly in the
> >User Config/AdminTemplates/ControlPanel/Display but none
> of these are
> >propagating down to the systems that we moved into this
> OU (which is a
> >sub-OU of an existing OU). We then added to this same GPO
> a setting in
> >ComputerConfig/WindowsSettings/SecuritySettings/Local
> >Policies/SecurityOptions/disable CTRL-ALT-DEL
> requirement. The RSoP on a
> >system in this sub-OU shows this setting. So what the
> heck? I've seen
> >postings saying that this is known "bug" acknowledged by
> Microsoft. Does
> >anyone know what the deal is here?
> >
> >tia, Dave
> >
> >
> >.
> >



Relevant Pages

  • Re: Ideas on screen saver oddity
    ... convoluted group policy. ... Thanks for the response again and for the heads-up on that one registry ... Under your Screen Saver tab, do you see On resume, password protect or On ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Cached GPOs
    ... seen to caching occurs when you're editing a GPO. ... Template policy to ... > It may have been that at one time when the users were off network they ... >>> would still have the screen saver tab hidden because none ...
    (microsoft.public.windows.group_policy)
  • Re: Screensaver Password Policy Doesnt Work
    ... the registry key modified by the ... GPO is not effective with Windows XP! ... Policy MMC. ... All users get screen saver but only some get passowrd protection. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Screensaver Password Policy Doesnt Work
    ... the registry key modified by the ... GPO is not effective with Windows XP! ... Policy MMC. ... All users get screen saver but only some get passowrd protection. ...
    (microsoft.public.win2000.security)
  • Re: Cached GPOs
    ... set a domain-based policy that removed run from the start menu. ... the local GPO isn't processed at all. ... > When a machine is off the network, and powered on, it ... > would still have the screen saver tab hidden because none> of the existing GPO have modified the related registry> setting for the screen saver tab? ...
    (microsoft.public.windows.group_policy)