Why? Ever want to run a few tasks after upgrade, or more importantly, ensure a few things happen if the upgrade goes south and rollsback? Why not hitch a ride on what ConfigMgr is doing natively and add a few things you need.
Supported? Highly unlikely. Please test, and please don’t say “Gary did it” as rationalization when someone asks why you decided to do this.
Do you do it? Heck yes I do, in my lab. Need to get a little more test results before implementing in Production
How do you use it? I’m not telling! Oh wait, that’s why I’m blogging. I modify the SetupRollback.cmd to ensure the machine is pulled out of provisioning mode when it the upgrade rolls back, and to set a registry key for our reporting, and trigger hardware inventory.
Update 2020.09.23 – Added Post about how Windows 10 calls SetupComplete.cmd
More background.
ConfigMgr has two files in the c:\windows\ccm folder that it uses:
- SetupCompleteTemplate.cmd
- SetupRollbackTemplate.cmd