Solved

Screen Saver Lockout Policy not applying to client

Posted on 2014-02-12
5
475 Views
Last Modified: 2014-03-03
Hello All,

Environment: Windows 7, Windows 2003 DC and Windows 2008 DC

I have setup the ScreenSaver lockout on my Default Domain policy. The Policy is applying properly to all clients except for one (so far).

I have opened the RSOP.msc on this particular client and verified that all settings were there. I have also checked on the Group Policy events on the Event Logs and all the policies are applying without errors. I have specified a screensaver file on my policy and I have verified that this file is working properly on this client by executing it.

Does someone has an idea of what might be happening?

What can I do next to further troubleshoot this issue?
0
Comment
Question by:LuiLui77
  • 3
  • 2
5 Comments
 
LVL 19

Expert Comment

by:Patricksr1972
ID: 39854443
Can you show 2 printscreens?

1x GPO Settings for the policy?
1x GPO Scope settings?
0
 

Author Comment

by:LuiLui77
ID: 39854561
The Policy is very large so I printed portion of the Screen Saver settings. The Scope is also attached.

Let me know anything else you may need.
Policy.docx
0
 
LVL 19

Expert Comment

by:Patricksr1972
ID: 39854601
Clear. Please try this.
Get the policy out of domain policy and create a new one.
Your settings look ok except the security filtering as i remember correctly.
Please try to filter it by an indivudal user account instead of security group.
0
 

Accepted Solution

by:
LuiLui77 earned 0 total points
ID: 39864764
Hey Patricksr1972, I have taken the policy out of the Default Domain Policy and created another one with the Screen Lock out settings and applied it to a test OU were I have placed the workstation, still did not work.

I recalled it was a computer that I had replaced recently and started to install all pending updates. After I rebooted a couple of times to apply the updates, left the workstation 15 idle and the screensaver kicked in with the lockout.
0
 

Author Closing Comment

by:LuiLui77
ID: 39900008
I recalled it was a computer that I had replaced recently and started to install all pending updates. After I rebooted a couple of times to apply the updates, left the workstation 15 idle and the screensaver kicked in with the lockout.
0

Featured Post

Swamped with email signature updates?

Have you been given a load of changes to make to your users’ email signatures? Having to manually implement multiple signatures for every department? Let Exclaimer save you from being swamped with email signature updates!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

OfficeMate Freezes on login or does not load after login credentials are input.
When you try to share a printer , you may receive one of the following error messages. Error message when you use the Add Printer Wizard to share a printer: Windows could not share your printer. Operation could not be completed (Error 0x000006…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

920 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now