I am using a task sequence to deploy a handful of applications in a specific order. The second application exits with code 1310 which tells the SCCM client to (soft) reboot because the application is configured to determine behavior based on return codes.

The reboot itself is not a problem, however the prompt is only visible for 30 seconds in spite of the fact that my client settings specify a much longer reboot timeout. I have also tried adding the variable to my collection, SMSTSRebootDelay, however that doesn't work either.  Is there any way to get this type of reboot prompt to last longer than 30 seconds? 

Hi,

You could use the Built-in Variable SMSTSErrorDialogTimeout to accomplish this.

For a complete description of the method mentioned above, check out this article:

SCCM 2012 R2 Speed up and slow down reboot in one step!

http://sccmfaq.wordpress.com/2014/01/23/sccm-2012-r2-speed-up-and-slow-down-reboot-in-one-step/

More info:

Task Sequence Built-in Variables in Configuration Manager

http://technet.microsoft.com/en-us/library/hh273375.aspx

Note: Microsoft provides third-part contact information to help you find technical support. This contact information may change without notice. Microsoft does not gurantee the accuracy of this third-party contact information.

I am at a conference and will not be able to test this out for a little while. I'll reply back to this thread once I know if your advice is helpful.

Thank you.

I found a way to suppress the reboot completely.  This allows me to use a separate step in the task sequence when I need to reboot and I can then specify a specific timeout in that step which is more than 30 seconds.

Here is the information that helped me.

http://www.petervanderwoude.nl/post/working-with-the-restart-behavior-of-applications-in-configmgr-2012/

• Marked as answer by Cristopher_WPU 18 hours 45 minutes ago

I found a way to suppress the reboot completely.  This allows me to use a separate step in the task sequence when I need to reboot and I can then specify a specific timeout in that step which is more than 30 seconds.

Here is the information that helped me.

http://www.petervanderwoude.nl/post/working-with-the-restart-behavior-of-applications-in-configmgr-2012/

• Marked as answer by Cristopher_WPU Thursday, April 30, 2015 12:59 PM

I found a way to suppress the reboot completely.  This allows me to use a separate step in the task sequence when I need to reboot and I can then specify a specific timeout in that step which is more than 30 seconds.

Here is the information that helped me.

http://www.petervanderwoude.nl/post/working-with-the-restart-behavior-of-applications-in-configmgr-2012/

• Marked as answer by Cristopher_WPU Thursday, April 30, 2015 12:59 PM

Hi,

Glad to hear that and thanks for your feedback.

Have a nice day.