Tasks Interrupting Screensaver

ryley2637 · 24 Apr 2016

I have a file server that has several tasks running every minute that run batch and vbs files to ensure software is still running. I also want to make sure the server stays locked so after I use it, it will lock itself if I forget to. I had a screensaver set up before making all these tasks, but when the tasks run it prevents the screensaver from running because the tasks make Windows think it is being used. I can create another task to lock the computer, but this means when I am actually using the computer, the task will still force the computer to lock. How can I either prevent the tasks from cancelling the screensaver, or can I make the lock task not run when I'm actually using the computer (including via TeamViewer)? Thanks!

bro67 · 24 Apr 2016

There should be no screensaver running. It should be a "Headless" system (no keyboard, mouse and monitor".

There is no need for a file server to have something like a Screensaver running, since it eats up CPU cycles.

I use Crush FTP on my Windows 10 system that I test software on and have no issues. My NAS is a Lenovo ix2-4, ehich is a great system for a NAS. Personally your File Server should be running FreeNAS on its own machine.

Berton · 24 Apr 2016

If the Server is running 24/7 there is no need of a screensaver on modern monitors, might be better to just set the Power Options in Control Panel to turn the monitor off after a selected time period. My choice would be to also disable Sleep and Hibernate, tend to cause more problems for a lot of folks.

RolandJS · 24 Apr 2016

It's possible that GRC, Gibson Research SomethingOrOther has a Wizmo exe, a utility with many many switches. That might do what you want; I would recommend eliminating all of those lock-attempt auto-commands before trying Wizmo.

bro67 · 27 Apr 2016

Forget everything that Gibson states on his website. No third party utility is needed to stop the screensaver. The OP just needs to disable the screensaver, disable sleep and hibernate and just let it run. Turn off the monitor or do not even have one, just use RealVNC or a KVM switch over Ethernet.

I run a headless Raspberry Pi 2 and 3 for servers. If I need to go in and do something, it is over Putty, since there are no GUI's on them.