Best Practice for Handling Large Volumes of "Match Not Found" Discovery Models

[PrajjvalSiG]

Hi Community,

We currently have 1,900+ discovery model records with a normalization status of "Match Not Found."

We submitted these to ServiceNow for review. While only very few were normalized, and rest returned as "Unverified" or "Incomplete."

What I'm struggling to understand is that for many of these records, we already have a valid Publisher, Product, and Version from discovery, and the software can also be verified through vendor websites.

• I am considering the mappings are not present with ServiceNow hence they couldn't Normalize them however why are such products not added to the content library for future normalization?
• What is the recommended SAM best practice for managing a large volume of Unnormalized discovered models that ServiceNow cannot verify or normalize?

Would appreciate hearing how others have addressed similar challenges.

Regards,
Prajjval Singh

[pr8172510]

Hi @PrajjvalSiG ,

Match Not Found does not necessarily mean that the discovered Publisher, Product, and Version are invalid.

Normalization compares the discovered values against the ServiceNow SAM Content Library and applies the available normalization rules.

• Check the normalization status and discovered values first. A discovery model can be manually normalized when its status is Partially Normalized, Publisher Normalized, or Match Not Found.
  
  
• Review the Content Service/normalization rules. ServiceNow uses Product/Package Map rules, Pattern Normalization, Enhanced Pattern Normalization, and Wide-net Normalization. Wide-net normalization can cover multiple similar discovery models, but only selected products are eligible for it.
  
  
• Don't manually normalize all 1,900+ records immediately. Prioritize models that are relevant to your SAM reconciliation and licensing position.
  
  
• Use Normalization Suggestions where available. Suggestions can provide predicted Publisher, Product, Version, Edition, Platform, and Language values that can be accepted or rejected.
  
  
• Continue receiving Content Service updates. The Content Service provides updates to normalization-related content, including discovery maps, normalization suggestions, product names, publishers, product classifications, and other content.
  
  
• For products that remain unnormalized, manual normalization is an available option when you have sufficient evidence to map the discovered software to the correct software product.

One important distinction is that being able to verify a product on the vendor's website does not by itself mean ServiceNow will have a corresponding normalization mapping. The normalization process depends on the available ServiceNow content/rules.

For 1,900+ records,  use Content Service updates + normalization suggestions + selective manual normalization, rather than trying to manually maintain every discovery model.

Also, before manually normalizing a large number of models, it is worth checking whether several records represent the same discovery pattern.

A pattern-based approach may be more maintainable than creating individual mappings for every variation.