Screensaver and Power Setting Issues

G

Guest

Hello,

I seem to be having some screensaver and power setting issues with all of my
users. We were using WinExit.scr fine until a few weeks ago when it
mysteriously stopped working. We've also been using EZ_GPO to put our
systems into Stand-by and/or Hibernation also well, but that doesn't seem to
be triggering either.

I've done the following so far:

1) Verified the users and workstations have the correct screensaver settings
via RSoP.
2) Logged in as a restricted user and verified the screensaver is set
correctly. Pressing the "Preview" button initiates WinExit correctly and
logs the user out.
3) I ran "powercfg.exe /query" and verified all the power settings are
correct.
4) I read that some optical mice will trigger from a reflective surface and
reset the idle clock. I tried various mousepads without successs... I even
wrote a program in C# that hooked all mouse coordinates, mouse inputs, and
keyboard inputs... despite hours with no activity, the screensaver/power
settings do not activate.
5) I read that you can get a HID update from the Windows Update site, but
there was nothing available for my machines...
6) Oddly the logon.scr will run, so I wrote a script that I could execute
from a remote workstatoin to query how long any machine's logon.scr had been
running. Despite running for hours, the power settings would never put the
machine in stand-by or hibernation.


I'm not sure if anyone out there has the experience to help me with this
issue... I'd rather not deploy another 3rd party app since WinExit and EZ_GPO
used to work fine. Any pointers on what the problem may be or how to debug
what is preventing the screensaver from launching would be much appreciated!

Many Thanks,

Grant
 
G

Guest

Still no solution for this... I guess it's not easy being green!

I can query the idle timer using SysInternals PsLOGGEDON utility and it
clearly shows a value much higher than the current Power Profile settings, so
I still don't understand why the lower power states aren't triggering. I'm
guessing it's another Microsoft bug...

In the mean time I've just been using a script and the Task Scheduler to
shutdown all systems at night. It's not as good as shutting down idle
systems, but it is working until a guru and help me with a solution!

Grant
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top