After adding a computer to an OU in Active Directory to have it be exempt from going into screen saver mode, the system still goes into screen saver mode.

All other systems that the Sys admin put in that particular OU takes effect, except this particular system. Verified on the client system that it is in correct OU, by running gpresult.exe. Already had admin do a gpupdate.exe on there end. I rebooted system and re-authenticated back to the domain, but still to no avail. Anything I can try from the client side of things, or maybe even the server side? Already gave it a couple of days to replicate across domain, but still to no  avail. The client OS is Windows XP Pro.
unemployedsysadminAsked:
Who is Participating?
 
Mike KlineCommented:
The screen saver is a user setting so it won't apply to the computer unless you use loopback
Check out OBDA's comments in this post  http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_26192611.html
He has corrected me on that in the past too :)
 
Thanks
Mike
0
 
Dhiraj MuthaLevel DCommented:
Try removing it from domain and rejoining it. If no luck then remove the system from domain and change the hostname and then rejoin to the domain and have a check. Are you using Ghost to deploy OS on your systems?
0
 
Dhiraj MuthaLevel DCommented:
Also try running Microsoft's tool called NEW SSID and have a check, - http://www.brothersoft.com/newsid-156113.html
 
0
 
59calCommented:
in a command prompt from the machine in question, run GPUPDATE /force

this should force a reapply of the gpo's on that machine
0
 
Chris DentPowerShell DeveloperCommented:
This question has been classified as abandoned and is being closed as part of the Cleanup Program.  See my comment at the end of the question for more details.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.