| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Retired Forums
Forum: UD Windows Agent Support [Read Only]
Thread: Force run while logged off to override web schedule? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 5
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello, I am trying to optimize the Windows UD WCG installs on the computers I manage. The goals are:
Run only 8 hours overnight Run when the user is not in the office that day. The first goal will be met by running UD as a service and using the web console schedule. But, is there some way to override the schedule and run during the day if the user is not logged in? Could I: Run only when logged off and on a schedule to avoid network maintenance times? Maybe using Task Scheduler to run "at system startup" combined with web schedule? "Run as screen saver" by replacing the logoff screen saver with UD??? Isn't that logoff screen saver disguised as a .DLL file? Use a logon script to kill UD.exe, and a logoff script to restart it? Again, web scheduling to avoid network maintenance times. Use some other combination of web scheduling, task scheduler, running as a service, scripting, or otherwise... I don't want UD to run when the user is at their computer because I have noticed a slight lag when running it 24/7 on my machines. I don't mind the lag, but I don't want to hurt my users. And I don't want UD running during network maintenance, which consists of scheduled virus and spyware scans, backup operations, and patch deployment. Thank you for your help. |
||
|
|
RT
Master Cruncher USA - Texas - DFW Joined: Dec 22, 2004 Post Count: 2636 Status: Offline Project Badges: 
|
Scratching head.... What time of day is the "network malignance times"?
----------------------------------------It seems to me that you could get close by setting your profile to not run during the network maintenance times - what you are calling "web console schedule" I suppose and then mark each agent as run as a screensaver only.. And then set the screensaver in windows to "blank page". I have never heard of anyone trying this combination and I never have so I do not know if it will work. Please note that it does not restrict the agent to running 8 hours at night ...it would run any non network maintenance times when the user was not using it but was logged on. Now going back to running as a service so as to run when no user was logged on, if you are doing that, and all of the above, then it might get close to what you were after...if I understand it correctly and if some of my assumptions are correct. As I said earlier, I have never known of anyone trying that combination. So, if you try that - set profile to avoid scheduled maintenance times, set agent to run only as screen saver, set windows screen saver to blank and leave it running as a service... I would really be interested in the results. It just might run all the time except when the user is using the computer and during maintenance which is a bit of a modification of your original objective. Finally, there may be a “trump card” in there somewhere that makes this scheme unworkable. Please, if you don’t mind, let us know what happens when/if you try this. Regards and Season’s Greetings. |
||
|
|
Viktors
Former World Community Grid Tech Joined: Sep 20, 2004 Post Count: 653 Status: Offline Project Badges: 
|
I think that if you set it to run as a screen saver only, and have the screen saver be blank, then it will never run. The process running it as a service is probably goint to pause waiting for the screen saver to kick in, which it would never do.
What if you simply use the device profile on the web site to set the hours of unallowed operation for any times when it just must not run. Then set the agent to run as a pre-logon screen saver so that it would only run when a user is not logged in. Remove the agent from the start-up folders for the users so it doesn't run while a user is logged in. This might satisfy your requirements. However, running as a pre-logon screen saver is not officially supported and might not work under some circumstances. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Here is a method over on grid.org for only running while otherwise idle. It does not meet all your requirements, but is interesting.
http://forum.grid.org/phpBB/viewtopic.php?p=320929#320929 |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thanks for the suggestions. I'll research them and see what I can implement.
----------------------------------------I thought of a more clear goals and solutions for this: Goal - When logged off, run constantly, but don't run during network maintenance. Solutions: Run as pre-boot screen saver! (thanks for the suggestion) Or, run as service using profile schedule to avoid network maintenance, where logon script exits service and logoff script enables it. Goal - When logged on, don't run, but run for 8 hours overnight. Solutions: Task Scheduler starts and stops client/service corresponding with profile scheduling. This assumes the user's Task Scheduler starts at logon and stops (running tasks too?) at logoff. This frees the CPU as the user works, but allows crunching overnight if the user stays logged in. And it crunches all day if the user is logged off. However, if the user is logged in and not using the computer, it looses potential crunch time. Now, I just need those two Windows 2000 Resource Kit files to create the service..... [Edit 1 times, last edit by Former Member at Dec 23, 2005 10:19:55 PM] |
||
|
|
|