- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-20-2025 07:01 AM
We ran reconciliation for Red Hat and are receiving non-compliance for some Red Hat child products on the workbench. When we open the Software Model a message pops up indicating that the model will not be used for licensing. So now we are not sure why it is showing up on the license workbench. The child product is not currently related to a parent and we wonder if that could be causing the issue.
I included some screens shots attached for reference.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2025 07:33 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-23-2025 06:56 AM
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 :
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2020463
|
Do to the software install table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2025 12:54 AM
We had the same issue and what you can also do is convert the license type of the Discovery Models to Child or Not Licensable (keep the same here as in the Software Product) by creating a Product Exception Rule. After updating the rule, the license type will be correct and the products will disappear from the Workspace.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2025 07:33 AM
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