You may also want to run RSOP and compare the results... (Resultant Set of Policy)
Main Topics
Browse All TopicsI have set up an OU to standerdise the screen saver on all machines (simple eh!?)
Problem: The GP works on some machines (Any user) but not others (Any user). i.e. any user can log onto PC1 and it works, but if any of those users log onto PC2 it doesn't work.
I have checked the following:
- User and their computer in Active directory has only this policy
- The policy has "no Override Selected"
- The policy properties, security has the user and machine listed with "Apply Group policy ticked"
- Userenv has been run in Verbose mode on both machines (GP working and not) and both match, some differences but nothing important
- Userenv shows that the GPO GUID is the same on both machines, although they come from diffent DC's (so it's the correct GPO being run, and the DC's are replicating correctly)
- GPresults on both machines are almost the same, some differences but nothing important.
I've now run out of Microsoft documentation to look at.... please help.
Regards
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
No the article states
CAUSE
The problem occurs because this policy is now applied in the registry to the following key: WRONG
HKEY_CURRENT_USER\Software
Instead of directly to the following key: CORRECT
HKEY_CURRENT_USER\Control Panel\Desktop
and the machine that works has exactly the same (the CORRECT one)
:) No, it's vice versa.
Read this whole sentence more carefully:
---
The problem occurs because this policy is now applied in the registry to the following key:
HKEY_CURRENT_USER\Software
Instead of directly to the following key:
HKEY_CURRENT_USER\Control Panel\Desktop
But the user code component (Win32k.sys) was not modified to check the policy key location when reading the screen saver information.
---
I.e. problem occurs because policy key has ben changed to comply common policy location in registry but unpatched win32k.sys still checked old path.
And as i said Resource Kit documentation says the same.
Regards,
4auHuk
And this may be actually your case. It may be that you created policy using old System.adm template.
---
Also, the original Group Policy snap-in System Administration template (System.adm) sets the ScreenSaveActive and ScreenSaverIsSecure values using REG_DWORD values instead of REG_SZ values, therefore the user mode component (Win32k.sys) does not apply the screen saver policy unless the policy is created by using the new updated System.adm administration template.
---
I see how it can be read that way, however the machine that works only has HKEY_CURRENT_USER\Control Panel\Desktop
and doesn't have HKEY_CURRENT_USER\Software
Although I have now found the ANSWER!!! or at least a work around!!!!
Basically the machine that doesn't work, get it to join a workgroup instead of the domain and then re-join the domain again.. hey presto !!! the policy is applied.
Amazing how just rejoining the Domain again works for so many issues...!!! Many years ago, when I was just a project manager and did not know beans about how computers work, I used to go to our IT admin and complain that such and such was broken on my computer.. He would say "reboot" ... And sure enough, that was all it took... Rejoining the domain and the appliction of computer policy is the same way... Should have suggested it earlier, eh..??
Glad you got the workaround and it is fixed..!!
FE
Do you have any machines running W XP or W2K3..?? If so, download the new GPMC from MS.. It will help you with those GPO's...
http://www.microsoft.com/w
Business Accounts
Answer for Membership
by: 4auHukPosted on 2004-03-05 at 04:21:48ID: 10521832
moof_man,
om/default .aspx?scid =kb;EN- US; 257939
What is service pack level on your workstations?
Read this MSKB article (if you didn't already)
Screen Saver Policy May Not Be Applied:
http://support.microsoft.c
If it does not help you can use logon script to apply registry settings related to screen saver directly.
Best,
4auHuk