Unknown discovery source: Ci's are creating in personal computer class instead of SCCM

[jayanthiare]

Unknown discovery source: Ci's are creating in personal computer class instead of SCCM and there is no most recent discovery too. Does anyone have idea why those are creating in unknow source. how should those need to make to come from SCCM. Do i need to change the IRE rule, please find the attached images.

[fknell]

Hi @jayanthiare,

To better assist you, we need more information. Are you referring to asset or CI creation, in which case the reconciliation rules are irrelevant. What do you mean by the CIs are created as personal computer rather than SCCM? 

Do you have the payload available that should or will be processed? You could simulate the IRE processing of your records and identify the identification rule, that is triggered. I wrote an article about that topic:  Identification Simulation: Testing IRE Rules and Creating Mock Data 

Hope this helps!

[jayanthiare]

Thanks for your reply, what i mean is that computer devices which are supposed to build from SCCM discovery source are creating but alot of devices are getting from unknown discovery source. so my question is why they are creating in unknown discovery source. Due to this the ci's in computer class doesn't have any most recent discovery.

[fknell]

Do you load / update the computer devices from SCCM via import set or the Service Graph Connector?

In case you load via RTE and IRE, have you mapped the fields accordingly? This is not done by default, you have to add the mapping for discovery_source manually.

To verify if the source is set, open the SCCM Computer Identity mapping step in the setup of the SCCM graph connector. Check if you find a mapping for the discovery source. If it’s missing, add it and set it to the fixed value 'SG-SCCM'.