?
Solved

Screen Saver Lockout Policy not applying to client

Posted on 2014-02-12
5
Medium Priority
?
510 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 23

Expert Comment

by:Patrick Bogers
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 23

Expert Comment

by:Patrick Bogers
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

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

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

Wouldn't it be nice if objects in Active Directory automatically moved into the correct Organizational Units? This is what AutoAD aims to do and as a plus, it automatically creates Sites, Subnets, and Organizational Units.
Transferring FSMO roles is done when an admin wants to split roles between certain Domain Controllers or the Domain Controller holding the Roles has been forcefully demoted using dcpromo / forceremoval
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …
This video shows how to use Hyena, from SystemTools Software, to update 100 user accounts from an external text file. View in 1080p for best video quality.
Suggested Courses

612 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