SCCM Probe vs Client Agent

  • 8 November 2021
  • 2 replies

Userlevel 1
Badge +2

Hi everone

Can someone explain me the difference between the crawling of SCCM data and if I install a agent on a client?

Thank you.

2 replies

Userlevel 4
Badge +5

Hi @alephtaph 

When using the discovery probe to sync information from SCCM, the probe would need to be installed in your domain and then the integration has to be setup. Post this, you can configure a schedule within your probe which would import data from SCCM on the mentioned intervals. Whereas with the discovery agent you would need to deploy the agent to all the machines using GPO or other deployment tools and the data would be directly pushed from those specific machines to your inventory when connected to the internet.

With the probe, the data gets scanned based on the schedule that you configure, whereas with the discovery agent the agent checks for any updates on the machine and pushes the data automatically to your inventory.

You can read more about Discovery probe and SCCM integration in the solution article here.

Do let us know if you need any more information on this.


We have been using the discovery agent and a probe for active directory sync. What do we need to be aware of if we wanted to change to using the sccm probe? Does the discovery agent need removed from all machines first and the AD probe sync turned off?