When a client push installation is initiated Config Mgr. generates a CCR – Client Configuration Request file – for each client. To stop the process those files must be manually deleted. As the files are processed they are moved between three different folders.
- Initially the files are created in the .\inboxes\CCR.box
- When the CCR is prossed the record will be moved to .\inboxes\CCR.box\inproc
- Finally all installation request that failed (for some reason) will be stored as the computername in .\inboxes\ccrretry.box
Dear kent
I already remove all recoard on .inboxesCCR.box and .inboxesCCR.boxinproc
and restart server , after server back I still see client on branch site go to primary site to download file ( I used prtg to monitor traffic. it have many traffic out of server ) how to can stop client go to download installation file on primary server
[…] Full Post – http://blog.coretech.dk/kea/how-to-stop-a-client-push-installation-in-configuration-manager/ […]
Saved my bacon! Inadvertenly chose to install the client to the all systems collection!
Thanks!
@Miguel :
It happens more than you could imagine. One time I sent Office 2013 to All Systems collection and maxed out every single MPLS in the company for an hour. Nevertheless, this method also saved my bacon.
Thank you Kent Agerlund!
Is that sufficient for SCCM 2012 SP1 CU1?
Isn’t there an additional working list elsewhere now before they go to .inboxesCCR.box?
Hi by mistake i have initiated console client push on all system collection,once the system is discovered agent is installing on all discovered machine and it is retrying ever hour, So could you help me out
Hello,
Excellent information…
As the issue is when the ccrretry is filling up how do you get alerted for this? Any view? Monitor?
Thanks,
Dom