- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Was looking for some info and couldn't find a crystal clear answer on it. We are using the free base SAM plugin package and we're using ACC as our main endpoint discovery right now. We are populating software installations on our Linux and Windows servers, but not on our endpoint machines.
Is SAM Pro required to populate this? I see that the software does populate when I run a test check using the agent on windows endpoints, but the scan never populates the data into cmdb_sw_install.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @mattwatts8451 ,
If your goal is only to capture and view raw discovered software data, you technically don’t need SAM Pro Discovery, ACC, or SCCM can populate this data (cmdb_software_instance).
However, in most environments, the Software Installation [cmdb_sam_sw_install] table which holds all discovered software installations is maintained and updated through background jobs and logic provided by SAM Pro.
Here’s how it works in practice:
-
ACC / Discovery collects the raw software inventory.
-
SAM Pro’s data model and scripts process and write that data into cmdb_sam_sw_install.
-
SAM Pro then enables normalization, license metrics, reconciliation, and compliance activities.
So while the scan itself doesn’t depend on SAM Pro, the automated population and management of installation data typically do.
Regards,
Abhishek
Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @mattwatts8451 ,
If your goal is only to capture and view raw discovered software data, you technically don’t need SAM Pro Discovery, ACC, or SCCM can populate this data (cmdb_software_instance).
However, in most environments, the Software Installation [cmdb_sam_sw_install] table which holds all discovered software installations is maintained and updated through background jobs and logic provided by SAM Pro.
Here’s how it works in practice:
-
ACC / Discovery collects the raw software inventory.
-
SAM Pro’s data model and scripts process and write that data into cmdb_sam_sw_install.
-
SAM Pro then enables normalization, license metrics, reconciliation, and compliance activities.
So while the scan itself doesn’t depend on SAM Pro, the automated population and management of installation data typically do.
Regards,
Abhishek
Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.
