Add Retry Count and Delay between to Task Sequence
Add a retry count and delay between retry properties to at least the most critical task sequence steps, if not all, so that we can make task sequences more resilient when there are hiccups to servers or network.
SMSTSMPListRequestTimeout – Specify how many milliseconds a task sequence waits before it retries to install an application after it fails to retrieve the management point list from location services. By default, the task sequence waits 60 seconds before it retries the step 3 times
SMSTSDownloadRetryCount – Controls the number of times that Configuration Manager attempts to download content from a distribution point. By default, the client retries 2 times.
SMSTSDownloadRetryDelay – Controls the number of seconds that Configuration Manager waits before it retries to download content from a distribution point. By default, the client waits 15 seconds before retrying.
I’ll close this item out once our 1902 release is completed.
during apply os, usmt backup or full drive backups, those often take a while; we've seen some worse case scenarios of 16 hours for a replace scenario. if there is any interruption, on the network or the dp in use, the task sequence will fail.
that is unless you add your own catches in the task sequence to handle that, which limits retries to have many catches you want to add, making for a long ugly task sequence.
The product already supports Retry count for Install application step and Install updates step. Currently delay is available for Run cmdline. Also we have configurable retry and delay for the download failures. Can you please give more info on where else you would like to see the retry counts and delays.