Stop Client Push Installation In Configuration Manager

In this post we will see how to stop client push installation in Configuration Manager. We know that Configuration Manager client can be deployed in various ways. Client push is one of the most used installation methods because it requires very little work. All you need to do is to specify one or more client push installation accounts along with some client push installation settings.  Sometimes when you enable automatic site wide client push installation, you may begin to see that there is lot of network traffic (in large organizations), but how do you stop this now ?. Here is a post that explains you on how to do it.

Before we do that, let’s see a brief process on how is CCR generated.

1) When one of the discovery processes is running, a client configuration request (CCR record) will be generated for each object that does not have a client installed.

2) Using the client push account, the Client Configuration Manager (CCM) component will make a connection to the client and copy the two files ccmsetup.exe and mobileclient.tcf to Client>Admin$>CCMSetup.

3) Once the files are copied, the server will verify that the CCMsetup service is starting successfully on the client before it disconnects. The client installation will proceed on the client machine.

4) When ConfigMgr determines that the CCMSetup.exe service is started successfully and the agent is running, it adds the CCR file to the <ConfigMgrInstallPath>Inboxes> folder for verification. This file is deleted after a second verification.

When a client push installation is initiated Configuration Manager generates a CCR (Client Configuration Request file) for each client. To stop the client push you need to delete the files manually. As the files are processed they are moved between three different folders.

a) From the below screenshot we see that initially the files are created in the .inboxes> . The files are created here and are quickly processed and moved to next folder.

Stop Client Push Installation In Configuration Manager

b) Once the CCR is processed the record will be moved to .inboxes>>inproc.

Stop Client Push Installation In Configuration Manager

c) When ConfigMgr determines that the CCMSetup.exe service is started successfully and the agent is running, it adds the CCR file to the <ConfigMgrInstallPath>Inboxes> folder for verification.  In case the client computer is down or if there are some unknown reasons due to which client install fails, the record is seen in .inboxes>

Stop Client Push Installation In Configuration Manager



Prajwal Desai

Hi, I am Prajwal Desai. For last few years I have been working on multiple technologies such as SCCM / Configuration Manager, Intune, Azure, Security etc. I created this site so that I can share valuable information with everyone.
Photo of author

5 thoughts on “Stop Client Push Installation In Configuration Manager”

  1. i don’t know where to look but i am having issues where a device stopped in the windows upgrade process 71% in SCCM. is there a way to restart it?

  2. Hello,
    Thank you for this clarification of usage of the various folders. How does it take (on average) between the push and the deletion of the files on the folder? should theremaining files be deleted after a certain delay? how to make the relation between the ccr number and the machine name it is referring to as the content of the ccr is always empty?

  3. Hello Prajwal, i have initiated client push on test PC Windows 10. but as i see in ccm.log the ccmsetup service fails to start with error 1053. The exact message in log is “Unable to Start CCMexec service on workstation…” i have verified the service account is fine, sccm is copying the above 2 files to admin$ share, the ports in firewall looks good, the communication is fine between MP and PC. i tried to install manually the client but no luck. kindly can you suggest some workaround.

  4. Hi Prajwal by mistake i have initiated console client push on all system collection and now as the system is discovered automatically client agent is being installing and it is retrying every 60mins, so could you help me out how to overcome with this issue


Leave a Comment