Allow "Retry on unexpected restart" for the "Upgrade Operating System" task sequence steps.
We are seeing a number of unexpected restarts during the "Upgrade Operating System" Windows 10 feature update that causes the task sequence to fail. These restarts are happening during the "setup.exe" phase of the process. Allowing the task sequence to continue would resolve this issue.
Anonymous
shared this idea
2 comments
-
Anonymous
commented
is this fixed or still open item?
-
Gary Blok
commented
Agree... I see this hundreds to thousands of times per upgrade cycle. The CM Client is left in a very unhealthy state when this happens. Often requires manual intervention. We use custom scheduled tasks and PowerShell scripts to repair the client and make it able to attempt upgrade again.
I would note, I'd rather not have it retry, but repair the client and report that it was Unexpected Rebooted", and then have it try to upgrade during the next MW or Deadline.
I think if it were to retry, the user would just continue to reboot the machine, or potentially cause an endless loop if the reboot was due to a BSOD or other action. I'd just like the client repaired and have the failure logged.