Missing Installed Software : Discovery

[jeremyeperdue]

Last month we were able to pull in the installed software on a machine via discovery.

Found that when we run discovery now, it is not populating this data.

At the beginning of this project, we applied a business rule to prevent duplicate CI names and it had a similar affect on Network Adapters and Disks. We found this BR to be the issue and removed it and this is no longer an issue. So I am somewhat familiar with the process, but not familiar enough. How can I further troubleshoot this issue?

I have:

checked all Business Rules created on or around the time it stopped working.

Confirmed the payload is being returned:   WMI: Installed Software (nodes: 2)

Check log files and no errors are being returned.

[jeremyeperdue · Accepted solution]

We found the Software Asset Management plugin was enabled around the time this started. Once enabled, it changes the table where installed software is populated by discovery from 'Software' cmdb_ci_spkg to 'Software Installation' cmdb_sam_sw_install.

By adding the related list pointing back to the sw_install table, it resolved this issue.

[johnnyjava]

How does the SAM plugin change the target?

My Installed Software Sensors both have hard coded entries:

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

[jeremyeperdue]

Good question Johnny. To be honest, I never looked into it. Once we found that was the issue, we change the related lists to reflect the table being populated and never looked back. If you look into it anymore, posting what you find here may help someone in the future.

Thank you for the extra input.

Jeremy

[johnnyjava]

I have added the following code to our IBM WebSphere Process Classifier:

handleWithSAM(g_sensor.deviceGR.sys_id, 'IBM WebSphere Application Server V' +current.version);

function handleWithSAM(installed_on, display_name) {

  var sgr = new GlideRecord("cmdb_sam_sw_install");

  sgr.addQuery("installed_on", installed_on);

  sgr.addQuery("display_name", display_name);

  sgr.query();

  if (!sgr.next()) {

  sgr.initialize();

  sgr.installed_on = installed_on;

  sgr.display_name = display_name;

  sgr.publisher = "IBM";

  sgr.insert();

  }

}

Which works. I couldn't locate any code that wrote to the cmdb_sam_sw_install table other than a Transform Map for SCCM integration that our previous implementation partner wrote. This would explain why the only data I have in cmdb_sam_sw_install is related to machines in the SCCM database.