Extend the Task sequence error timeout duration
Can I Extend the Task sequence error timeout duration? Can I make the error window stay open infinitely (never timeout)? My technicians are imaging large numbers of machines every summer and they tend to start them and walk away. When they come back 30 minutes later the machines are all at the login screen whether they finished successfully or not, since the error timeout has expired and has rebooted the machine. I realize there are log files and that they can just check to see if the last software item in the task sequence has completed, but they aren't. I just need a slightly more foolproof way to show them something failed. Thanks in advance. Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
August 8th, 2011 9:29am

If they start imaging manually they could also press F8 (enable commandline support on Bootimagefirst) when PE is started before leaving the workplace. This way the machine would not reboot. Miguel Rodriguez
Free Windows Admin Tool Kit Click here and download it now
August 8th, 2011 9:32am

If they start imaging manually they could also press F8 (enable commandline support on Bootimagefirst) when PE is started before leaving the workplace. This way the machine would not reboot. Miguel Rodriguez Thanks for the idea, but we have built in reboots during the task sequence which would not be able to occur with the command-line interface open. Therefore this won't work.Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
August 8th, 2011 9:36am

So a little more searching and I found: SMSTSErrorDialogTimeout When an error occurs in a task sequence, a dialog box is displayed that is dismissed automatically after a default time-out value. Use this variable to specify a time-out value in seconds other than the default of 15 minutes. My new question is can I set this globally or must it be set in each task sequence?Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
Free Windows Admin Tool Kit Click here and download it now
August 8th, 2011 9:38am

Just setting a collection variable (SMSTSErrorDialogTimeout) should do the trick for all the systems in that particular collection. To set globally choose the all systems collection. Miguel Rodriguez
August 8th, 2011 10:07am

Testing that now. The technet article I found did not give me valid range information. I put 28800 (8 Hours) to start. Does 0 (zero) equal "never"? Is there somewhere anyone knows of that gives valid values for the variable? Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
Free Windows Admin Tool Kit Click here and download it now
August 8th, 2011 10:20am

36.000 worked for my testing, which equals 10 hours. 0 expands to 71.000.000 minutes (infinite), so you could use that.Miguel Rodriguez
August 8th, 2011 10:31am

Just setting a collection variable (SMSTSErrorDialogTimeout) should do the trick for all the systems in that particular collection. To set globally choose the all systems collection. Miguel Rodriguez That worked.Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
Free Windows Admin Tool Kit Click here and download it now
August 8th, 2011 12:19pm

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

Other recent topics Other recent topics