- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-13-2015 06:28 PM
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.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-17-2015 07:21 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-08-2015 06:54 AM
I can tell that RPM or DPKG intalled software is making it into the cmdb_sam_sw_install table, and since what I really care about are things we don't use RPM/DPKG to install, I plan to move the above code into a Script Include and then call it from the necessary Process Classifiers and Sensors.
I still consider Discovery to be a fine Asset Mgmt tool. We already spent the time to tell Discovery what all these Running Processes are, it's not a big deal to now tell Discovery to record them as Software Installations.