- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
hi guys i am new in SAM do you know about reconciliation product list
I need to determine and configure the managed products targeted for reconciliation within SAM Pro to ensure accurate license compliance tracking.
Acceptance citeria: A list of products that will be evaluated under the reconciliation process in ServiceNow has been determined and configured
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Hi @adilalee200 ,
SAM Pro only evaluates products where the License Under Management flag is set to true on the Software Model (cmdb_software_product_model) record. Everything else is ignored by the reconciliation engine - no compliance position, no shortfall, no surplus. If a product isn't flagged, it effectively doesn't exist from a licensing perspective.
How to decide what goes on the list:
- Discovery coverage exists - Is there install data in cmdb_sam_sw_install? No installs = no reconciliation value.
- Entitlements are in place - Do records exist in alm_license ? Without this, you'll just generate an unresolved shortfall.
- Normalisation is confirmed - The product must be matched to a Publisher + Product + Version via the Content Library. Unmatched titles won't reconcile cleanly.
- Reconciliation model is assigned - Per Device, Per User, Per Core, Processor-based - this needs to be correct before the engine runs, not after.
For a deep-dive on how license type and metric interact with reconciliation calculations: SAM Pro: How license type and license metric affect Reconciliation
Prioritise by license risk: Microsoft, Oracle, IBM, Adobe, VMware typically come first. Anything under active audit or renewal pressure should be fast-tracked.
For understanding SAM system properties that control reconciliation behaviour Explained: SAM System Properties
Useful reference threads
- 🔗 How does Reconciliation work in SAM Pro?
- 🔗 Best Practice: Managing Licensed Software Models
- 🔗 Installs Requiring Action on the License Workbench
- 🔗 How to Troubleshoot Reconciliation Failures
- 🔗 SAM Pro Reconciliation Rules
If this helped - amazing, you're welcome, go click Helpful and Accept as Solution. If it didn't - well, at least you learned what not to do. Either way, we grow.
Cheers, Abby
ITAM Principal Solution Architect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Hello @adilalee200
Ithe Reconciliation Product List in ServiceNow SAM Pro is basically the list of software products that you decide to include in license reconciliation.
Not all discovered software is reconciled by default — only the products you enable.
To configure it:
Identify key software (e.g., Microsoft, Oracle, Adobe)
Go to Software Models
Enable reconciliation for those products
Ensure proper normalization/mapping
Once this is done, those products will be included in reconciliation and you can track their license compliance.
If this helps, please click on Helpful
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Hi @adilalee200 ,
SAM Pro only evaluates products where the License Under Management flag is set to true on the Software Model (cmdb_software_product_model) record. Everything else is ignored by the reconciliation engine - no compliance position, no shortfall, no surplus. If a product isn't flagged, it effectively doesn't exist from a licensing perspective.
How to decide what goes on the list:
- Discovery coverage exists - Is there install data in cmdb_sam_sw_install? No installs = no reconciliation value.
- Entitlements are in place - Do records exist in alm_license ? Without this, you'll just generate an unresolved shortfall.
- Normalisation is confirmed - The product must be matched to a Publisher + Product + Version via the Content Library. Unmatched titles won't reconcile cleanly.
- Reconciliation model is assigned - Per Device, Per User, Per Core, Processor-based - this needs to be correct before the engine runs, not after.
For a deep-dive on how license type and metric interact with reconciliation calculations: SAM Pro: How license type and license metric affect Reconciliation
Prioritise by license risk: Microsoft, Oracle, IBM, Adobe, VMware typically come first. Anything under active audit or renewal pressure should be fast-tracked.
For understanding SAM system properties that control reconciliation behaviour Explained: SAM System Properties
Useful reference threads
- 🔗 How does Reconciliation work in SAM Pro?
- 🔗 Best Practice: Managing Licensed Software Models
- 🔗 Installs Requiring Action on the License Workbench
- 🔗 How to Troubleshoot Reconciliation Failures
- 🔗 SAM Pro Reconciliation Rules
If this helped - amazing, you're welcome, go click Helpful and Accept as Solution. If it didn't - well, at least you learned what not to do. Either way, we grow.
Cheers, Abby
ITAM Principal Solution Architect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
