Steps to make the product complaint.

Go to solution
akguj
Tera Contributor

3 weeks ago

I W1.png

 

I would like to understand the steps required to make a Windows product compliant from a Microsoft publisher perspective. Could you please guide me on the process involved?

Additionally, it would be helpful if you could specify the relevant tables or areas that need to be reviewed to ensure compliance.

I would appreciate a detailed explanation of the steps and best practices to follow.

0 Helpfuls
  • 987 Views
1 ACCEPTED SOLUTION

Go to solution
pr8172510
Tera Guru

3 weeks ago

Hi @akguj,

 Microsoft/Windows products become compliant only after proper normalization, entitlement mapping, and reconciliation are completed.

  1. Verify Software Discovery Model
    Table:
cmdb_sam_sw_discovery_model

Ensure:

  • Publisher = Microsoft
  • Product normalized correctly
    2.Verify Software Model
    Table:
cmdb_software_product_model

Check:

  • Publisher populated
  • Discovery model mapped
  • Product normalized

    3.Verify Software Entitlement / License
    Table:
alm_license

Ensure:

  • Correct software rights exist
  • License metric configured
  • Entitlement linked to product

    4.Verify Installations
    Table:
cmdb_sam_sw_install

Make sure installations are discovered properly.

            5.Run Reconciliation

             Navigate:

Software Asset → Reconciliation → Run Reconciliation

Select:

Microsoft Publisher

6.Review Compliance Result

Check:

  • Product Compliance
  • License Position
  • Over/Under Licensed status

 Tables

Purpose Table
Discovery Modelscmdb_sam_sw_discovery_model
Software Modelscmdb_software_product_model
Installationscmdb_sam_sw_install
Entitlementsalm_license
Compliance Resultssamp_compliance_result

Common Reasons Compliance Fails

  • Publisher missing
  • Product not normalized
  • No entitlement/license rights
  • Discovery model not mapped
  • Reconciliation not run

compliance is calculated through:

 
Normalized Installations
        +
Software Entitlements
        +
Reconciliation
        =
Compliance Position
 
  • Use Content Library updates
  • Normalize software first
  • Run reconciliation regularly
  • Maintain proper publisher/product mappings
 
 

View solution in original post

0 Helpfuls
6 REPLIES 6

Go to solution
pr8172510
Tera Guru
In response to akguj

2 weeks ago

Hi @akguj,

 compliance is calculated using entitlements (license rights) versus consumption.

If the Windows product has no entitlement records, then it cannot be made compliant simply by running reconciliation.

To make it compliant:

  • Create or import the appropriate Microsoft Windows Software Entitlements.

  • Link the entitlement to the correct Software Model.

  • Verify installations are discovered correctly.

  • Run SAM Reconciliation.

Without entitlement rights, ServiceNow has no licenses to compare against consumption, so a compliant position cannot be achieved.

Entitlements (License Rights)
            +
Installations/Consumption
            =
Compliance Position


No entitlements = No license rights available for compliance calculation.

 

0 Helpfuls

Go to solution
Tanushree Maiti
Tera Patron

3 weeks ago

Hi @akguj 

 

Product : Windows server

Windows server license compliance

 

Product: O365

Microsoft 365 or O365 License Compliance and Optimization on ServiceNow SAM

 

 

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
0 Helpfuls