How can I keep the screensaver from starting or control the screensaver when its settings are configured by the LAN?

[rafaelboudec]

Hi all,

How can I keep the screensaver from starting or control the screensaver when its settings are configured by the LAN?

I tried to use the lvwutil32 (Screen saver control) but it doesn't work when I'm logged.

I also tried to catch the wm_syscommand using the windows_messaging_que.vi’s to answer -1, but I don’t know how to give the reply. This would work?

Could somebody help me?

Thanks,

Rafael Marc Le Boudec

[smercurio_fc]

Are you saying your domain admin actually set up a group policy to enforce that screensavers run? I have no idea why they would do that unless they're still under the mistaken impression that screensavers "save" monitors from burn-ins. This side-effect pretty much only applied to very old monitors. Screensavers are just pretty to look at. That's about it. If you actually do have a group policy set you can try to

• set the timeout really really large, if that's allowed under the group policy
• set the screensaver to the blank (none) screensaver (not sure if you'll be able to do this)
• point out to your system admin that they're a little cooky (either that or just a control freak - not sure which is worse)
  

[RavensFan]

I've tried to find a way to programmatically simulate activity like simulate a mouse to prevent the screensaver from coming on, but have not been successful.

Smercurio, we also have group policies on screensavers that we can't override unless we beg and plead with our IT gods,  I mean admins.  The screensaver is set up with password protection and a 15 minute timeout.  You have to log back in in order to clear the screensaver.  They do that for security so that a computer that is left unattended for more than 15 minutes can't be jumped onto by an unauthorized user.

I bet Rafael is dealing with a similar scenario.

[smercurio_fc]

Good point. Of course, if that's the policy, then the OP may be committing a security policy violation by trying to get around the policy like that.

How about just moving the screensaver programs to someplace else? Basically all the .scr files in the Windows directory.

[AnalogKid2DigitalMan]

We ran into this a few months ago with new IT policy that force a logout/login screen saver.

Attemps to gain leverage via LabVIEW were fruitless.

However, " in theory " it was postulated that running of an application such as Windows Media player could hypothetically prevent such aforementined screensaver from activating. Furthermore, running in the repeat loop mode of an audio file like Beethoven's 9th with a shortcut to the file strategetically placed in the preferred username's startup folder could facilitate circumvention of such policy.

But it's just a theory that one might want to prove or disprove for sake of argument. I for one would not condone such practices, like advising someone to code in C....

-AK2DM

[AnalogKid2DigitalMan]

Hopefully in about 15 minutes we will have some results?