How SCCM 2012 R2 Client Communication Process Works

How SCCM 2012 R2 Client Communication Process Works

Once the agent is available on the network and the client is installed, the client goes through the following actions as part of the reporting process:

1. Client location services identify the site code and the MP it is supposed to connect to.
2. The client connects to the Management Point and downloads the policies.
3. Once the policies are downloaded it sends the heartbeat record to the server.
4.  Once the server receives this heartbeat record these are converted in to DDR and processed.  This will set the client flag to 1 which will make the client status display as Active in the console.
5.  On a regular basis the agent will send the heartbeat and if no heart beat or inventory shows up for a length of time then the client flag will be marked as 0 by the client flag maintenance task, setting the client status to Inactive.
6.  So only if this process is completed and it continues to happen will the client remain reporting to the server.