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.
Rom
shared this idea
Thanks for all your suggestions and feedback, updating status to completed.
SCCM 1902 fast Ring released today
Blog: https://techcommunity.microsoft.com/t5/Configuration-Manager-Blog/Update-1902-for-Configuration-Manager-current-branch-is-now/ba-p/376516
Docs: https://docs.microsoft.com/sccm/core/plan-design/changes/whats-new-in-version-1902
3 comments
-
Bellson
commented
What is with the trend of mods on TechNet and other sites like these replying with links that do not pertain to the original question?
-
Rom
commented
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.
Thanks!