SAM Pro License Renewal Lifecycle End to End
The lifecycle has five distinct phases in ServiceNow SAM Pro. Here's how they connect:
Phase-by-Phase Breakdown
Phase 1 - Discovery & Inventory
This is the foundation. SAM Pro pulls software install data into cmdb_sam_sw_install via Discovery (MID Server + probes), SCCM/Intec connectors, or agent-based collection. Without clean, normalized installs, everything downstream breaks.
The normalization engine maps raw install strings (e.g. "Microsoft Office 365 ProPlus 2019 en-US x64") to a canonical publisher → product → edition → version hierarchy using the Soft Library (MSRP). If normalization fails, the install won't reconcile. Unnormalized installs are one of the most common root causes of inaccurate compliance positions.
Key tables: cmdb_sam_sw_install, cmdb_software_product_model, cmdb_software_instance
Phase 2 - Entitlement Setup
This is where you tell SAM Pro what you own. Entitlements live on the alm_license table and are linked to contracts (ast_contract). Each entitlement has:
- Metric type — Per device, per user, per processor, concurrent, etc.
- Effective/expiry dates — Critical for renewal tracking
- Quantity — Purchased seats or rights
- Rights type — Standard, downgrade, upgrade, cross-edition
Common mistake here: importing entitlements with wrong metric types, or leaving renewal dates blank. Blank expiry dates mean SAM Pro will never flag the entitlement for renewal.
Phase 3 - Reconciliation
The reconciliation engine matches installs (what's deployed) against entitlements (what you own) and calculates your compliance position. Let me show you how the reconciliation logic flows internally:
The three outputs (compliant, over-licensed, under-licensed) drive completely different next steps, which is why many people conflate reclamation and remediation when they're actually solving opposite problems.
Phase 4a — Reclamation (Over-licensed / Unused software)
Reclamation is for software you have too much of — either over-purchased entitlements or installs sitting unused. SAM Pro has a built-in reclamation workflow:
Key reclamation config points in SAM Pro:
The reclamation workflow is triggered from the SAM Workspace. You configure: the inactivity threshold (e.g. software not used in 90 days), the response window (how many days the user has to justify), and whether the uninstall task auto-creates or requires approval.
Phase 4b — Remediation (Under-licensed)
Remediation is the opposite — you've deployed more than you own. SAM Pro generates remediation tasks to bring you back into compliance:
Phase 5 — Contract / License Renewal
This is where the lifecycle feeds back to the beginning. SAM Pro drives renewal through three mechanisms:
1. Renewal notifications - configured on the contract record (ast_contract). Set a threshold (e.g. 90 days before expiry) and SAM Pro fires a notification to the contract owner. Common issue: notification not firing because the End date field is blank or the notification's condition isn't matching the right contract type.
2. Renewal decision workflow - when approaching renewal, your reconciliation position directly informs the renewal quantity. If you're carrying 200 unused seats (over-licensed), you reduce at renewal. If you're under-licensed by 50, you add at renewal. This is the data loop that makes SAM Pro genuinely useful for procurement negotiations.
3. Contract update - once the renewal is agreed, you update the ast_contract record with new start/end dates, revised quantities, and updated cost. The linked alm_license entitlement records are updated accordingly. The next reconciliation run immediately reflects the new position.
Common Practitioner Gotchas
A few things that bite almost every implementation:
1: Reconciliation doesn't run unless normalization is clean. Unnormalized installs simply don't get picked up. Always check the normalization coverage % before your first reconciliation run and set a KPI (typically targeting >85%).
2: Metric type mismatches kill compliance accuracy. If your entitlement says "per device" but the publisher actually charges "per user," your position will be meaningless. This is especially painful for Microsoft 365 and Adobe CC. Validate metric types during entitlement import.
3: Reclamation notifications silently fail when the "Last used date" field isn't being populated by your discovery source. If SCCM isn't passing metering data, SAM Pro has no basis for inactivity detection. Confirm the metering data flow before enabling reclamation.
4: Renewal date alerts require the contract to have an end date. Sounds obvious, but imported contracts often have blank end dates especially when migrated from spreadsheets. Build a data quality check into your contract import process.
5: The 3 R's must run in sequence. Reconciliation first → identifies the position → then reclamation (over-licensed) and remediation (under-licensed) run in parallel → then renewal uses the cleaned position as the negotiation baseline.
If this helped sort things out, please mark it as Helpful and Accept it as the Solution much appreciated.
Regards,
Abby
SAM Pro License Renewal Lifecycle End to End
The lifecycle has five distinct phases in ServiceNow SAM Pro. Here's how they connect:
Phase-by-Phase Breakdown
Phase 1 - Discovery & Inventory
This is the foundation. SAM Pro pulls software install data into cmdb_sam_sw_install via Discovery (MID Server + probes), SCCM/Intec connectors, or agent-based collection. Without clean, normalized installs, everything downstream breaks.
The normalization engine maps raw install strings (e.g. "Microsoft Office 365 ProPlus 2019 en-US x64") to a canonical publisher → product → edition → version hierarchy using the Soft Library (MSRP). If normalization fails, the install won't reconcile. Unnormalized installs are one of the most common root causes of inaccurate compliance positions.
Key tables: cmdb_sam_sw_install, cmdb_software_product_model, cmdb_software_instance
Phase 2 - Entitlement Setup
This is where you tell SAM Pro what you own. Entitlements live on the alm_license table and are linked to contracts (ast_contract). Each entitlement has:
- Metric type — Per device, per user, per processor, concurrent, etc.
- Effective/expiry dates — Critical for renewal tracking
- Quantity — Purchased seats or rights
- Rights type — Standard, downgrade, upgrade, cross-edition
Common mistake here: importing entitlements with wrong metric types, or leaving renewal dates blank. Blank expiry dates mean SAM Pro will never flag the entitlement for renewal.
Phase 3 - Reconciliation
The reconciliation engine matches installs (what's deployed) against entitlements (what you own) and calculates your compliance position. Let me show you how the reconciliation logic flows internally:
The three outputs (compliant, over-licensed, under-licensed) drive completely different next steps, which is why many people conflate reclamation and remediation when they're actually solving opposite problems.
Phase 4a — Reclamation (Over-licensed / Unused software)
Reclamation is for software you have too much of — either over-purchased entitlements or installs sitting unused. SAM Pro has a built-in reclamation workflow:
Key reclamation config points in SAM Pro:
The reclamation workflow is triggered from the SAM Workspace. You configure: the inactivity threshold (e.g. software not used in 90 days), the response window (how many days the user has to justify), and whether the uninstall task auto-creates or requires approval.
Phase 4b — Remediation (Under-licensed)
Remediation is the opposite — you've deployed more than you own. SAM Pro generates remediation tasks to bring you back into compliance:
Phase 5 — Contract / License Renewal
This is where the lifecycle feeds back to the beginning. SAM Pro drives renewal through three mechanisms:
1. Renewal notifications - configured on the contract record (ast_contract). Set a threshold (e.g. 90 days before expiry) and SAM Pro fires a notification to the contract owner. Common issue: notification not firing because the End date field is blank or the notification's condition isn't matching the right contract type.
2. Renewal decision workflow - when approaching renewal, your reconciliation position directly informs the renewal quantity. If you're carrying 200 unused seats (over-licensed), you reduce at renewal. If you're under-licensed by 50, you add at renewal. This is the data loop that makes SAM Pro genuinely useful for procurement negotiations.
3. Contract update - once the renewal is agreed, you update the ast_contract record with new start/end dates, revised quantities, and updated cost. The linked alm_license entitlement records are updated accordingly. The next reconciliation run immediately reflects the new position.
Common Practitioner Gotchas
A few things that bite almost every implementation:
1: Reconciliation doesn't run unless normalization is clean. Unnormalized installs simply don't get picked up. Always check the normalization coverage % before your first reconciliation run and set a KPI (typically targeting >85%).
2: Metric type mismatches kill compliance accuracy. If your entitlement says "per device" but the publisher actually charges "per user," your position will be meaningless. This is especially painful for Microsoft 365 and Adobe CC. Validate metric types during entitlement import.
3: Reclamation notifications silently fail when the "Last used date" field isn't being populated by your discovery source. If SCCM isn't passing metering data, SAM Pro has no basis for inactivity detection. Confirm the metering data flow before enabling reclamation.
4: Renewal date alerts require the contract to have an end date. Sounds obvious, but imported contracts often have blank end dates especially when migrated from spreadsheets. Build a data quality check into your contract import process.
5: The 3 R's must run in sequence. Reconciliation first → identifies the position → then reclamation (over-licensed) and remediation (under-licensed) run in parallel → then renewal uses the cleaned position as the negotiation baseline.
If this helped sort things out, please mark it as Helpful and Accept it as the Solution much appreciated.
Regards,
Abby
