How are Software Discovery Models created?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2018 08:30 PM
Hi,
OOB Software Discovery Models gets created automatically based on the data being discovered and stored in Software Installations Table. But for us Software Discovery Models for some Product are not getting created even if the data is present in Software Installations table.
Is there an particular function or script accessible to us which needs to be debugged to fix this.
Kindly assist!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2018 08:33 PM
My recommendation is to create and submit a HI ticket.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-30-2018 07:44 AM
The following Business Rule on the Software Installation table creates a Discovery Model or links the newly inserted Software Installation record to an existing Discovery Model.
Create a Software Normalization
This is a Before business rule. The issue you describe could be caused if the Busines Rule completed but there was an error completing the insert of the Software Installation record.
As Mike suggested, a HI Incident may be useful in determining the root cause.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2018 08:28 PM
Thanks a lot Daniel and Mike.
Will contact the ServiceNow HI Team before making any changes to OOB Business Rule.
One other issue say when a Software is removed from a Physical Device, it's getting removed from SCCM as well, but the same is not getting deleted from Software Installations table which is causing a data count conflict for us.
Any inputs on this would be really helpful.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2021 11:51 AM
Hi,
Reference this community answer here.
New versions of SCCM 1906 and higher will most likely continue to have this issue, Triggers are getting deactivated by Microsoft for the two dedicated tables. I've dealt with this at clients in recent past as well. Have your SCCM team re-enable the triggers on the two tables below if they are disabled.
SCCM_Ext.Add_Remove_Programs_DATA_DD
SCCM_Ext.Add_Remove_Programs_64_DATA_DD)t