Answered by:
Client is uninstalling itself every 5 hours

Question
-
On one of my SCCM 2012 R2 clients, the client uninstalls and reinstalls itself every 5 hours.
It sounds like there's a "Install client" stuck somewhere with the "uninstall first" option chosen. I'm open to ideas to troubleshoot and hunt this sucker down.
Tuesday, January 28, 2014 10:05 PM
Answers
-
I've found the reason and how to resolve, I'm still testing to find the exact cause though.
When CCMSETUP runs, if it is unable to install for some reason (e.g. can't connect to DP/MP) it creates a Scheduled Task to retry again later, this allows it to survive a reboot. Once it has successfully run it should cleanup that task. I suspect that if you then run CCMSETUP again manually at some point, it starts as a whole new setup and "forgets" to cleanup that scheduled task
- Proposed as answer by Scott Williams - IP1 Monday, January 12, 2015 11:13 PM
- Marked as answer by DragonSpeed Tuesday, January 13, 2015 12:05 AM
Monday, January 12, 2015 11:13 PM
All replies
-
The client agent won't uninstall itself. There must be something else involved like possibly the ccmeval task.
Have you reviewed ccmsetup.log and the other logs in ccmsetup\logs?
Jason | http://blog.configmgrftw.com
Wednesday, January 29, 2014 12:41 AM -
I've seen the install loop when someone tries to manually install a client, but does it many times. It just keeps looping. That's not the case for you because it is waiting 5 hours.
I think your install is failing along the way. Check the CCMSETUP and CCMEVAL log that Jason suggested, and post a snip here if you have any questions.
Best, Jacob I'm a PC.
Wednesday, January 29, 2014 1:45 AM -
I noticed in my ccmsetup.log that it was trying to install, and felt it needed to UNINSTALL before installing, so I have actually uninstalled (ccmsetup /uninstall) and then manually installed. I am monitoring now to see if it has broken its cycle.
- Proposed as answer by Stanislav ZhelyazkovMVP Tuesday, December 2, 2014 4:47 PM
Wednesday, January 29, 2014 5:16 PM -
I've found the reason and how to resolve, I'm still testing to find the exact cause though.
When CCMSETUP runs, if it is unable to install for some reason (e.g. can't connect to DP/MP) it creates a Scheduled Task to retry again later, this allows it to survive a reboot. Once it has successfully run it should cleanup that task. I suspect that if you then run CCMSETUP again manually at some point, it starts as a whole new setup and "forgets" to cleanup that scheduled task
- Proposed as answer by Scott Williams - IP1 Monday, January 12, 2015 11:13 PM
- Marked as answer by DragonSpeed Tuesday, January 13, 2015 12:05 AM
Monday, January 12, 2015 11:13 PM