Exclude software asset on CI

[shwetakr]

Could you please explain how the "Exclude Software Asset on CI" functionality works in the backend? Specifically:

• How does ServiceNow process an excluded software asset internally?
• Does excluding a software asset impact Normalization, Software Discovery Models, or Software Models?
• Does this feature have any impact on the CMDB or Hardware Asset Management (HAM)?
• Are there any dependencies, limitations, or implications for other ServiceNow applications or modules when this feature is used?
• What are the recommended best practices and considerations before enabling this functionality?

[Maniteja_2003 · Accepted solution]

Hi @shwetakr 

I hope this answer helps you.

The Exclude Software Asset on CI functionality is used to exclude software installations associated with specific Configuration Items (CIs) from SAM license compliance calculations. It does not remove the software installation from the CMDB or prevent ServiceNow from discovering or normalizing the software.

The recommended ServiceNow approach is to create a True/False field on the CI table and configure that field in the system property com.snc.samp.exclude_device_flag. When the configured field is set to true on a CI, the software installations associated with that CI are excluded from SAM license compliance calculations.

A scheduled job called "SAM — Adjust Installs for excluded CIs" runs Weekly on Monday and excludes Software Installs from SAM (Software Asset Management) whenever the related CI is flagged with "Exclude from SAM" set to true.

1. If a Software Asset is excluded from SAM License Calculation, a scheduled job identifies the affected Software Installation records and:

• Sets the Active field to false.
• Clears the Primary Key value, which is a combination of Publisher, Product, Edition, and Version.
• Removes the reference to the Discovery Model.

2. For the Software Installation record, the Normalized values are also cleared, includes the normalized Publisher and Product. However, there is no impact on the Discovery Model or Software Model.

3. This feature does not impact the CMDB or Hardware Asset Management (HAM).

4. There are no direct dependencies on other ServiceNow applications or modules when using this feature.

5. This feature is recommended when the organization is not responsible for the software licenses consumed by software installed on those CIs. No additional considerations are required for implementation. Follow the ServiceNow-recommended steps to configure and enable this functionality.

Thanks,

Maniteja.

[shwetakr]

Thank you. this information helps!