Child and Not Licensable software reporting in the Workspace

NormKalish · ‎07-01-2025

How can I eliminate Child software from reporting in the Workspace. I don't want to create a Software model for Child software just to exempt it from the Workspace. example of child software reporting is .net Framework, .net Sdk and .netCore software all from Microsoft.

Vickie Cooper · ‎07-01-2025

I posted this solution a week ago in another post seems to be a common problem.

https://www.servicenow.com/community/sam-forum/child-asset-type-showing-up-as-non-compliant-in-workb...

This just happened to me and I input a ticket and it did fix my issue.

I went to the sam installation table and filtered on Unlicensed installs = True and then grouped the discovery models to see which ones I needed to revert the normalization for. This was the easier way for me.

ServiceNow ticket response:

Solution proposed is :

Upon checking further, usually when we run reconciliation we look for those product that have type licensable. For not licensable product type we do not create reconciliation result or product result/software model result.

The cause could be one of the following

1. The Products on license workbench are dependent on product results generated during the reconciliation. In some cases, even though the product is non-licensable somehow the product results generated. And this is the reason we see Reader in License workbench.
2. In some cases, the content must have updated from licensable to non-licensable. Due to this the software installs remains in older normalization where the product is licensable.
3. There might be some bad data import mechanisms that update this.

You can try :
Step#1 Revert the normalization for all the discovery models that are associated with these software installations. By doing below
Step #2 Then normalize it by clicking on Normalize UI Action as below

https://www.servicenow.com/docs/bundle/yokohama-it-asset-management/page/product/software-asset-mana...

I believe this issue can be related to the issue mentioned in the below kb article

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2020463

You can use the below script to fix the current set of problematic records:
// Clearing installation records' invalid norm_product & norm_publisher values
var installGr = new GlideRecord('cmdb_sam_sw_install');
installGr.addQuery('norm_product', 'norm_product_sys_id');
installGr.addQuery('norm_publisher', 'norm_publisher_sys_id');
installGr.addQuery('discovery_model.norm_type', '!=', 'licensable');
installGr.setValue('norm_product', '');
installGr.setValue('norm_publisher', '');
installGr.updateMultiple();

dylanhollor · ‎07-14-2025

We have been having the same issue and have escalated with ServiceNow to resolve as their one time solution didnt permanently fix the issue. There is a curated fix for this going to be implemented in the Zurich Release. See https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2020463