RE: ScreenSaver timeout problem via GPO



Hi scott7.

I have exactly the same sort of issue, and have had both myself and another
network person (including a security instructor), and while we all seem to
have come to the same conclusion that we need loopback processing to make
this sort of thing work, we haven't been able to get it to work.

I'm going to list what I have done (which seems almost the same as you
scott), and I hope that someone will point out the blundering error that we
are missing.

- Like you we have a subset of our machines that we don't want the
screensaver polity to run. Loopback processing seems like that is what it is
designed for.

-Like you, I have my users (and computers) organized into different OUs.

-Like you, I have a screensaver policy that is filtered by security groups.
But since those groups contain pretty much everyone, everyone gets the
screenscaver policy.
Here are the settings:

Administrative Templates
Control Panel/Display
Pollicy Setting
Password protect the screen saver Enabled
Screen Saver Enabled
Screen Saver executable name Enabled
Screen Saver executable name scrnsave.scr

Policy Setting
Screen Saver timeout Enabled
Number of seconds to wait to enable the Screen Saver
Seconds: 900



- I made an "anti-screensaver" policy. For testing purposes, I filtered it
based on my work computer. Its not REALLY "anti-screensaver" right now cause
I'm just trying to make the loopback work and want to see a difference in the
screensavers. So I selected a different screensaver to use. Here are the
settings for that policy:

Administrative Templates
System/Group Policy
Policy Setting
User Group Policy loopback processing mode Enabled
Mode: Merge


Administrative Templates
Control Panel/Display
Policy Setting
Password protect the screen saver Disabled
Screen Saver Enabled
Screen Saver executable name Enabled
Screen Saver executable name ssstars.scr

Policy Setting
Screen Saver timeout Disabled


- When I run the modeling wizard, I use my active directrory account and my
computer name, and set it to simulate loopback processing with merge (as it
is in the policy). It comes back and says that both policies are being
applied. However, it is the screen saver policy that is "winning". The
"anti" screen saver policy doesn't override it.

I would apprecate feedback from anyone who knows more about this than I do
(which is not loads), as we are desprate to get this to work.

Thanks in advance
Chuck


"scott7" wrote:

I have about 4 laptops at my company with special needs. I need the screen
saver to be totally disabled on these 4. They are used for PowerPoint and
special assignments and the screen needs to stay on and never lock. Let me
give you some facts about these laptops so you know the situation.

.



Relevant Pages

  • Re: Screensaver lockout in Group Policy
    ... What exact policy setting are you working with? ... off of the top of my head I think you are saying you 'lock the workstation' ... In policy you have "Hide Screen Saver", which hides the screen saver tab ...
    (microsoft.public.win2000.group_policy)
  • Re: Loopback processing not working
    ... Well you could just deny the right to apply the policy for the screen saver ... I understand that loopback processing within a policy is the route to go ... Policy Setting ... Password protect the screen saver Enabled ...
    (microsoft.public.windows.server.active_directory)
  • Re: Reverting GPO settings back to Default
    ... Well, keep in mind that Screen Saver policy is per-user, so if the user account isn't moving to a different OU as well, then nothing is going to change for that user, regardless of where their laptop computer account resides. ... Speed Group Policy Troubleshooting with the NEW GPHealth Reporter tool at http://www.sdmsoftware.com/products.php ...
    (microsoft.public.windows.group_policy)
  • RE: ScreenSaver timeout problem via GPO
    ... Number of Seconds to wait to enable the Screen Saver = Enabled at 0 Seconds ... give you some facts about these laptops so you know the situation. ... This policy is not enforced so if a lower OU blocks inheritance it ... loopback processing and it would still run if in the correct order. ...
    (microsoft.public.windows.server.active_directory)
  • RE: ScreenSaver timeout problem via GPO
    ... Loopback processing seems like that is what it is ... I have a screensaver policy that is filtered by security groups. ... Password protect the screen saver Enabled ... Screen Saver timeout Disabled ...
    (microsoft.public.windows.server.active_directory)