Don't Set CCMClient to Provisioning mode if running Compat /SCANONLY option
Currently, anytime you run the upgrade OS step, it set the client into provisioning mode, despite the options you're choosing. Could this be changed, that if you pick "Compatibility scan without upgrade" it would NOT put the client into provisioning mode.
I've had users reboot the computer when the scan was running (silently in the background), and then the client was in provisioning mode.
Updating Status to completed. This was addressed in our 1806 release – thanks for the suggestion and feedback
As this item is now closed we’ll likely miss any new comments, to report issues see https://docs.microsoft.com/en-us/sccm/core/understand/find-help
re: Gary Blok
Which version of SCCM are you using? We have multiple checks to reset ProvisioningMode to false in event of Rollback.
Would you be ok with contact to gather logs from one of the rollback and some other info.?
Gary Blok commented
Thank you, so glad to hear this is started. Since you're doing this, can you add the command to remove a computer from Provisioning mode to the SetupRollBackTemplate.cmd file? Currently I add that line into the Template at the start of the TS, so if the machine rolls back (and we see this happen a lot sadly), it runs the command to pull it out of provisioning mode. (During actual Upgrade Task Sequence). Currently we have a lot of rollbacks, and before I added a few failsafe's into the process, machines were consistently being stuck in provisioning mode after a rollback.
We have also hit this when performing a silent compat scan!
Marc Graham commented
I 100% back this idea as I have had several clients with this challenge in their environment. Gary is spot on w/ this suggestion and also his solid "RunOnce" workaround: https://garytown.com/configmgr-client-provisioning-mode
Gracias brother Gary!!!