Stopping scheduled tasks that run too long - Server 2008 vs. Server 2003

In Server 2003, we could configure tasks to be stopped if they ran for 10 minutes.  In 2008, this setting seems to have a lowest value of 30 minutes.  We have limited time in the night to run these tasks and 30 minutes may cause our tasks to collide.  We've noticed that we can manually enter 10 minutes in the combo box and it seems to stick, but are unsure as to whether this will work or is even wise to attempt.

Are missing something, is 30 minutes truly the lowest value, or can we manually enter 10 and sleep soundly.  Thanks
2030pennAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jason WatkinsIT Project LeaderCommented:
I think you'll be fine with just entering a manual time value. 10 minute values exist as options in other parts of the creation script.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
str8jacket29Commented:
According to MSDN, the capability is built in. "Specify a time when a task must time-out to prevent the task from running for too long."

http://msdn.microsoft.com/en-us/library/bb756979.aspx


New Task Settings
Task Scheduler uses settings to run the task with respect to conditions that are external to the task itself. Task settings specify how a task is run, stopped, or deleted. You can use task settings to:

•Schedule what actions to take if a task fails to run.

•Retry a task if it fails.

•Specify how many times to retry a failed task.

•Ensure that a task runs when the machine is powered on if the machine is powered off when a task is scheduled.

•Specify a time when a task must time-out to prevent the task from running for too long.

•Run a task as soon as possible after a scheduled start is missed.

•Force a task to stop if it does not end when requested.

The following illustration shows the settings for the Defrag task in the Task Scheduler Library.
0
2030pennAuthor Commented:
I doubled points and split because Firebar was first, but str8jacket29 pointed to a more complete explanation.  After digging through the initial link offered, I found these, which are confirmation enough for me.

http://msdn.microsoft.com/en-us/library/aa382678

http://www.w3.org/TR/xmlschema-2/#duration

Thanks for the assistance
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.