Solved

GPO Not Updating for Users

Posted on 2013-12-11
2
362 Views
Last Modified: 2013-12-30
Windows server 2003, R2 policy change (screen saver time out) via GPO not updating down to users. The screen saver time out was changed from 1800 seconds (is working) to 900 seconds. The gpo update was forced. PC's have been restarted since change.
Users still set at 1800 seconds.

Double checked the policy in use, users looking to that policy (when run query report via GP editor) and 1800 seconds still working but settings do reflect 900 seconds.

AV checked (tested with disabled), event viewer doesn't show any issues.

Any suggestions on what might be causing this to keep from updating?
0
Comment
Question by:TSB14883
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 37

Accepted Solution

by:
Mahesh earned 400 total points
ID: 39712159
If 1800 seconds is working, I have not seen any reasons for not applying 900 seconds

Just run gpupdate /sync command on PDC with elevated command prompt and reboot the server once, and check on client computers by running gpupdate /force

If above doesn't work, then just remove screen saver setting from GPO, run gpupdate /force on PDC and client computers as well and check if setting is removed from client computers or not

If clients still showing old 1800 seconds, then probably you need to create new GPO as old GPO is not applying or corrupted somehow.

Mahesh
0
 
LVL 16

Expert Comment

by:Dirk Mare
ID: 39712322
Sorry..

I removed my comment.
0

Featured Post

Salesforce Made Easy to Use

On-screen guidance at the moment of need enables you & your employees to focus on the core, you can now boost your adoption rates swiftly and simply with one easy tool.

Question has a verified solution.

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

by Batuhan Cetin In this article I will be guiding through the process of removing a failed DC metadata from Active Directory (hereafter, AD) using the ntdsutil tool in a Windows Server 2003 environment. These steps are not necessary in a Win…
Recently, I had the need to build a standalone system to run a point-of-sale system. I’m running this on a low-voltage Atom processor, so I wanted a light-weight operating system, but still needed Windows. I chose to use Microsoft Windows Server 200…
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…

628 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