/build/static/layout/Breadcrumb_cap_w.png

TaskTimeout Modification Script

TaskTimeout allows you modify the timeout period of the task engine with K2000 version 3.6 and higher. The task timeout period starts immediately when a task is run.  When the timeout period is reached, the task will fail and then either display the task error screen or continue to the next task, depending on the option chosen.

The task timeout period is stored in config.xml, which gets copied to the x: drive in KBE immediately after the initial deployment begins. Config.xml gets read immediately prior to every task that is run. By default, the timeout period is set to 8 hours.

The task timeout script can be be run multiple times to change the timeout period in KBE as a pre or midlevel task or in Windows as a postinstall task.

*Note: It is recommended that you use the task timeout script as a mid-level or post install task.  This is because the "Apply Image" task also uses the task timeout period.  If you don't give the image enough time to apply, then the image deployment will fail.

Usage
=====
The /min: switch must be specified and followed by the desired number of minutes for the timeout period. The value must be between 10 minutes and 960 minutes (16 hours). An example of a proper command is:
task_timeout.exe /min:30

There are 2 executables included in the download, task_timeout.exe and task_timeout_x64.exe.

task_timeout.exe should be used for:
- Any Preinstall TaskTimeout task within a 32 bit KBE
- Any Midlevel TaskTimeout task within a 32 bit KBE
- Any Postinstall TaskTimeout task inside of Windows (regardless of x86 or x64)

task_timeout_x64.exe should be used for:
- Any Preinstall TaskTimeout task within a 64 bit KBE
- Any Midlevel TaskTimeout task within a 64 bit KBE
- Any Postinstall TaskTimeout task inside of Windows x64 only

 

Download here.
*Note: you must be a member of the K2000 ITNinja Community to download this file.


v. 1.0.0.1 [06-06-14]
-fixed issue with not reading timeout minutes correctly


v. 1.0.0.0 [02-03-14]
-initial release


Corey A. Serrins
Patrick Warme
John Cutler

 

Back to K2000 Deployment Workbench Page


Comments

  • I really wish this could be implemented at either the Image level or at least the task level. - swalker804 4 years ago
    • I agree. There does seem to be a config.xml per image within \\k2000\peinst\scripts. - idavidson0212 4 years ago
This post is locked
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ