task sequence time question
We have a task sequence that has 10 application packages inside of it. It does not do any OSD, just software installs. Each package is set to the default 120 min run time. If you push this task sequence to an office with a very slow link at what point does the package timer start? Example: The first package is over 50MB and if it takes 120 min to get copied down to the target machine will all of the following packages time-out? Or does the 120 min timer start when the package actually gets started? mqh7
June 20th, 2012 12:40pm

I beleive the timer starts when the advertisement starts the download. I have had a few applications that take literally seconds to install timeout after 10 minutes because the link maxed out.
Free Windows Admin Tool Kit Click here and download it now
June 20th, 2012 2:23pm

The time will be based on each step in the task sequence. Once a new step in the task sequence starts it will read the time-out value and then start the counter.
June 20th, 2012 2:28pm

ChadCarroll, do you have any documentation that supports that?mqh7
Free Windows Admin Tool Kit Click here and download it now
June 20th, 2012 3:14pm

Hi, With regular software deployments, the maximum runtime value is used to determine if the program will be run within a given maintenance window. If your clients in slow network, you can have the program's maximum run time set to unknown. And as I known, when client start to run the advertisement it will download the package to client cache if it is configured to then run the program. So if a maintenance window hits, and maintenance window remaining time is longer than this program's maximum run time it was allowed to run. Then client will try to download the package content and with slow network it will not finished downloading and this program will failed with run time exceeded error the status message with ID 10070 is generated that says something like this: The program for advertisement "<advertisementID>" ("<package ID>" "<Program name>") exceeded the maximum allowed run time of XX minute(s). Systems Management Server (SMS) has stopped monitoring the program, and is unable to determine the status of the program. SMS will not automatically attempt to run this program again. Hope this will help. Thanks
June 26th, 2012 4:37am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics