What attributes SCCM and JAMF feed into cmdb_sam_sw_install table for MS & Adobe for Laptop/Desktop

amit_kishore
Tera Contributor

2 hours ago

Hi All,

 

We have a client requirement where we need to carry out a migration from SAM Foundation to SAM Pro for both Laptop and Desktop environments, covering SaaS as well as on-premise deployments for Microsoft and Adobe publishers. As part of the current setup, SCCM and JAMF are being used to perform software discovery across the environment, and this data will be leveraged during the migration.
 
As we move forward with this transition, we want to ensure that the data being populated is complete and accurate so that we can achieve a reliable license position and enable effective software reclamation. In this context, we are particularly looking for guidance on the cmdb_sam_sw_install table.
 
Could someone please help clarify the complete set of attributes that need to be populated in the cmdb_sam_sw_install table? Additionally, it would be helpful to understand any best practices, mandatory fields, or common pitfalls to avoid so that the license reconciliation and reclamation rules function optimally post-migration.

 

Regards,

Amit K  

0 Helpfuls
  • 84 Views
2 REPLIES 2

Laveena-Agarwal
Mega Sage

56m ago

Hi @amit_kishore 

 

If you are using Service Graph Connector for JAMF , here are  the list of attributes and classes- https://www.servicenow.com/docs/r/washingtondc/servicenow-platform/service-graph-connectors/cmdb-jam...

0 Helpfuls

pr8172510
Tera Guru

15m ago

Hi @amit_kishore,


the following attributes are considered critical for successful Normalization, Reconciliation, Compliance, and Reclamation

Software Name / Display Name
Publisher
Version
Discovery Source
Installed On (CI)
Assigned User (if applicable)
Install Date
Last Used Date (if available)

 Important Fields

  • Software Name → Used for normalization.

  • Publisher → Required for software model matching.

  • Version → Required for license calculations.

  • Installed On (CI) → Required for device-based licensing.

  • Assigned User → Required for user-based licensing metrics.

  • Discovery Source → Helps manage multiple discovery tools (SCCM, JAMF, etc.).


Best Practices

  • Keep the Content Library up to date.

  • Validate normalization results before migration.

  • Ensure SCCM/JAMF installation records are linked to valid CIs.

  • Verify Microsoft and Adobe software models are correctly matched.

  • Run reconciliation and review unmatched installations before go-live.


Common Pitfalls

  • Missing Publisher or Version values.

  • Unnormalized software installations.

  • Orphaned installation records without a CI relationship.

  • Missing user-to-device mappings for user-based licensing.

  • Duplicate software installations from multiple discovery sources.

 

For SAM Pro, data quality is more important than populating every field. As long as the installation records contain enough information for:
Installation
↓
Normalization
↓
Software Model
↓
Reconciliation
↓
Compliance / Reclamation


the license position and reclamation processes will function correctly.

 

0 Helpfuls