On Thu, Nov 29, 2012 at 1:28 PM, Mike Copeland <[email protected]> wrote: > Thanks Matt. > > The problem I'm running into is that this program that needs to run every 5 > minutes will throw an error if it runs after 5pm.
here are more examples: http://technet.microsoft.com/en-us/library/cc725744%28v=ws.10%29.aspx It looks like this does what you want but instead of 'off hours' you of course can choose 'during hours'... "The following command schedules a security script, Sec.vbs, to run on the local computer every 100 minutes between 5:00 P.M. and 7:59 A.M. each day. The command uses the /sc parameter to specify a minute schedule and the /mo parameter to specify an interval of 100 minutes. It uses the /st and /et parameters to specify the start time and end time of each day's schedule. It also uses the /k parameter to stop the script if it is still running at 7:59 A.M. Without /k, schtasks would not start the script after 7:59 A.M., but if the instance started at 6:20 A.M. was still running, it would not stop it. schtasks /create /tn "Security Script" /tr sec.vbs /sc minute /mo 100 /st 17:00 /et 08:00 /k" -- Matt Jarvis Eugene, Oregon USA _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/capt54rb98z+0f9jckqkomdlj8ekdz34hjkbbxrtkgboufog...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
