Group Policy

Microsoft Windows vista business w/sp1
April 20, 2010 at 05:51:06
Specs: Windows Vista
I cannot get group policy to initiate the screensaver on one of our windows vista machines. I've done extensive research and found only solutions that revolve around updating the HID-compliant mouse driver. Now, the machines we have do not use wireless mice and all of them are nearly identical. I've looked through the event viewer but cannot find any sort of task that comes from group policy that locks the machine. I did find eventID 124 "Task triggered by locking the workstation" but its not clear that this is coming from group policy. Regardless, the machine in question never has a log in the event viewer about this task.

I would love to provide anymore info I can for those that can help.

See More: Group Policy

Report •

April 20, 2010 at 13:52:07
Hmm, not have the same problem. I did have problems with logon scripts not firing see.

As for the screen saver locking the computer, we did ours under...

User Configuration -> Administrative Templates -> Control Panel -> Display ->
- Screen Saver Timeout.
- Password Protect Screen Saver

Report •

April 20, 2010 at 14:40:15
Ours are under the same. The same policy works on other vista machines, but not this one for some reason.

I'm starting to think its more of an issue with the screensaver just not starting than it actually being a group policy issue. I have an idea how to test this tomorrow but for now I'll just pursue the idea that its the screensaver not starting for some reason.

Anyone have any ideas as to why that would happen?

Report •

April 21, 2010 at 09:40:16
Sounds like the machine has lost its token on the Domain. Try dis-joining it from the domain, delete its OU on your Active Directory and rejoining to the domain and see if the GPOs are running again.

Report •

Related Solutions

April 26, 2010 at 09:56:48
The group policy is working I believe.

I ran a gpresult /h and stored the result for viewing. It has the policy, the screensaver just isn't firing for whatever reason. Any ideas?

Report •

April 26, 2010 at 16:17:17
You may have locked down your system32 directory too much. My guess is that Domain Users do not have execute rights to the screensaver.

Report •

April 27, 2010 at 05:56:22
Hmm, thats an interesting idea. This is only happening on one of our 50 or so Vista machines but its possible. I'll check back in a few. Thanks ace.

Report •

Ask Question