Task sequence fails in Configuration Manager if software updates require multiple restarts
I am using CM 1802 and deploying Windows 10 1803. Used install software updates as part of the OSD TS. The TS fails even though I use SMSTSWaitForSecondReboot - 120 Seconds. The TS waits but eventually it fails saying 'Task Sequence environment not found.' leaving client in provisioning mode.
Jeroen Bakker commented
I suspect the variable may give the desired results if you expand the wait time to a value between 300 and 600 seconds. The second reboot will usually not occur within 120 seconds after boot.
I've had good results with this option in my task sequences but the correct wait time may require some testing to find. Don't configure it to narrow beacuse some months the required time may be longer than others.