'Discovery source' field is empty for cmdb_ci_spkg CI after Discovery is complete

[P-Rudenko-SN]

Dear Community,

as I haven't found the clear answer to the question, decided to raise it again here. After I complete the WMI Discovery for Windows Servers, I've got server CIs created together with multiple related CIs. All the CIs are populated with 'Discovery Source' = 'ServiceNow', but Software (cmdb_ci_spkg) remains empty.

Did anyone change the default sensors and can advise what exactly must be adjusted in order to set  'Discovery Source' = 'ServiceNow' for Software CIs (cmdb_ci_spkg)? I know there is a sensor called 'Windows - Installed Software', that does 

this.addToRelatedList('cmdb_ci_spkg', filteredPackages, '', '');

 but after checking 'filteredPackages' variable and called 'InstallSoftwareFilter' script include, I still couldn't identify the line to set the discovery source field.

Appreciated for the help.

[Vaughn1]

Hi,

I'm currently having the same issue in my reporting for servers without software installations - 

I've been working with my CMDB team to run discovery on CIs that have a discovery source of SCCM and ServiceNow, and the counts have been reducing and pulling software

but I still have a considerably high amount of servers that have a discovery source of either Empty or Importset - will the scripts above help remediate this issue as well, if not how would I go about remediating these discovery sources?

[Venky VA]

Hi Vaughn,

check any of following articles might help.

• https://hi.service-now.com/kb_view.do?sysparm_article=KB0779445

• https://docs.servicenow.com/bundle/paris-it-operations-management/page/product/discovery/task/t_ChangeTheDiscoverySourceName.html

[Ashutosh Munot1]

HI,

As far as i know we do not populate this field via discovery. 

https://docs.servicenow.com/bundle/paris-it-operations-management/page/product/discovery/reference/r_DataCollDiscoGenSWPkg.html

I am not using this anymore because we have SAMpro but will check on this in detail.

Thanks,
Ashutosh