Discovery models with the status of Match not Found

JhansiLaksN
Mega Contributor

Wednesday

Hi Team,

 

There are 1432 discovery models with the status "Match not Found"

I raised these records to ServiceNow content team. But unfortunately, they were able to normalize only-151, Partially normalized-15, discovery models with Unverifiable/ Incomplete/ Invalid Data: 1,266.

 

Still there are 1266 records left. Could you please advise how to proceed with these records. In my opinion manual normalization these many records is not ideal at the same time not possible as well. Please advise on this. I have gone through the article they mentioned in the comment, but really not understanding completely. 

Below mentioned is the exact comment by ServiceNow team for your reference.

 

JhansiLaksN_0-1781690752312.png

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2673405

 

Thanks and Regards,

Jhansi Nagini

0 Helpfuls
  • 148 Views
1 REPLY 1

pr8172510
Tera Guru

Wednesday

Hi @JhansiLaksN,

Based on the ServiceNow Content Team response and KB2673405, the remaining 1,266 Discovery Models could not be normalized because the discovery data was classified as Unverifiable, Incomplete, or Invalid.

  • Content Service can only normalize software when sufficient and verifiable publisher, product, and version information is available.
  • These records will not be normalized automatically unless the source discovery data improves.

 
Action:

  • Review the unmatched records and identify common data quality issues.
  • Improve discovery source data (Discovery, SCCM, Intune, JAMF, etc.).
  • Create Manual Normalization Rules only for high-volume or business-critical software.
  • Do not attempt to manually normalize all 1,266 records.

 normalization success is dependent on the quality and completeness of the discovered software data. If the source data cannot be verified, the Content Service team cannot create a normalization match.

0 Helpfuls