I first had this happen on just one of my servers. It was annoying and was causing massive numbers of WMI entries in the event logs each time it happened. I tried to just stop and disable the ConfigMgr client, but it would be “reactivated” again by something. Recently at a client site I found it happening an a large number… so time to investigate.
I checked there were no push jobs running, but there was *something* causing it to repeat. Some digging later and I finally found the reason.
There is a scheduled task created by CCMSETUP to retry if it isn’t able to install correctly on the first attempt. Under some circumstances, this task isn’t cleaned up and so the reinstall keeps happening
To find the culprit, open Task Scheduler and look for the “Microsoft\Microsoft\Configuration Manager” folder. I’d say there is a “mistake” somewhere that has caused it to be created in this extra folder, but under normal circumstances it would never be noticed as it would be deleted, or never created in the first place.
get-scheduledtask -taskname "Configuration Manager Client Retry Task"
unregister-scheduledtask -taskname "Configuration Manager Client Retry Task" -confirm:$false
On a “good” client, these folders won’t even appear
I suspect this happens when CCMSETUP has been run and is unable to install, most likely because it can’t contact the MP or DP. When this happens it creates the scheduled task so that CCMSETUP will still run again if the computer is restarted (I have been reminded that CCMSETUP creates a service to handle the reboot survival, so the scheduled task is something else perhaps). If the client is successfully installed at a later time, I expect this task would be deleted (further testing needed to confirm)
If rather than waiting you then run CCMSETUP again, it “stops” the existing installer attempt but doesn’t seem to cleanup the scheduled task. Once the new setup has finished, the client is working but the scheduled task still keeps triggering it again.