Task Sequence Steps – Prepare ConfigMgr Client for Capture
This post is part of our Task Sequence – Beyond the Docs series.
This step is essential for a build and capture task sequence. It is closely related to the Prepare Windows for Capture Step. To see the full impact of this step, we really have to see how it interacts with the remainder of the TS after it’s called, which is why if you scroll down, you see a pile of logs. This post is really stealing the thunder from the Prepare Windows step.
When you create a default build & capture TS, it places the step in the correct place for you.
step starts phase 1
- osdpreparesmsclient.exe runs
- step triggers restart to clear any pending operations
- machine restarts back into task sequence
step continues into “phase 2”
- system check
- clears CM Cache
- stops ccmexec service
- removes policy and unassign client
- resets root key
- deletes instance of CCM_CLient
- deletes any TS execution requests
- deletes any maintenance tasks
- resets registration to “not registered”
- disables provisioning mode
- cleans up TS Policy
- deletes polcies in WMI
- sets SMSTSUninstallCCMClient variable to TRUE
- returns “SMS CLient has been successfully prepared for OS capture”
The step is then complete. The Client is then uninstalled at the end of the Prepare OS step just before it reboots to capture.
I’m going to go pretty heavy on the logs here to show the entire process, and to actually see the entire process. Here at the start you see the Prepare CM Client step run, where it triggers and restarts the machine, then when the machine comes back to life, starts to do a lot of the prep work as I listed above.
At this point, the machine can be captured as it ran Prepare steps beforehand.
Recently I used this step for creating our Non-Persistent VDI Image. It worked brilliantly to have the client removed at the end of the TS in a supported way.
<div class=”NOTE alert alert-note”><h5>NOTE</h5><p><p>The SMSTSPostAction variable does NOT work if you have the client removed.</p>
If you add the step into a normal OSD task sequence, a non-build and capture, but OSD task sequence, it does bad things.
It will not uninstall the CM Client by default, but when you finally get into the full os, the CM Client is completely crippled and not assigned to any site. The Task Sequence will complete, but hang for about 30 minutes for a timeout.
If you cheat and set SMSTSUninstallCCMClient to TRUE before that step, then the Client will actually uninstall directly after the reboot that the step initiates.
The Task Sequence dies at this point and exits out to Windows. The CM Client is gone and just a few logs are left behind.
Hopefully this information was helpful, often times you won’t need to troubleshoot this step, but it is nice to know what is going on behind the scenes.
More Task Sequence Steps – Beyond the Docs
Find all of our Task Sequence – Beyond the Docs series posts here.