I have seen issues where the SMSTSPostAction step is not executed as expected. If this happends make sure your SMSTSPostAction set step is the last one in the sequence (yes, the very very last)
When doing deployments with SCCM there are a couple of nice to have settings that I always put in and I thought I would share them here.
First off this in it self is nothing new but just a place to collect them in one place.
Lets get started. Create a new group at the top of your Task Sequence, this is not needed but it helps keep the Task Sequence clean and when you create a new one you can just copy the group and get all settings transfer to your new Task Sequence.
In that group create three Task Sequnce variables with the following settings.
Explanation: To decrease deployment time in SCCM checks and retry values where changed. This can cause issues with timeouts and application deployments. This increases the retry count from 2 to 5.
Explanation: To decrease deployment time in SCCM checks and retry values where changed. This can cause issues with timeouts and application deployments. This increases the retry delay to allow NIC more time to initialize before failing.
Value: Shutdown.exe /r /t 15
Explanation: The SMSTSPostAction will launch whatever command you type at the end of the Task Sequence but not inside of the Task Sequence. So in this setting a reboot will be done. This is to make sure the client will do a clean reboot and include all GPOs and other settings applied (since GPO is suspended while running Configuration Manager Task Sequences).
The end result should be something like this