Agent Client Collector on Windows - Not discovering Software Installed

[Curtis Paul1]

Basic Discovery/ACC-V plugin's installed.

Agent Client Collector agent installed on Windows 11 machine.

Discovers everything but Software Installed.

"Enhanced Discovery" and "sam advanced metering" Check Definition are listed as checks for the Agent in question.

The sam advanced metering check has the following defined "endpoint_discovery.rb --compact --select=basic_inventory,installed_software,sam_advanced"

Should I be expecting the Agent to be bringing software records into the Software Installed related list on the Computer CI the agent is running on?

Or does this configuration need to be modified to make it populate the Software Installed related list on the Computer CI?

[Rahul Priyadars]

Do u have SAM Plugin Installed?

Refer this KB for More Troubleshooting..

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0966481

refer this Step

Regards

RP

[Curtis Paul1]

Ya, I did try adding ",installed_software" to the Enhanced Discovery check, and that broke it.  Step 2 is saying "update check-allow-list.json" file on the agent?  I didn't do that.  So does this mean I need to physically touch the file on the computer running the agent?  Or is there a way to force the update of that json file remotely on the agent computer with servicenow?

Are you saying the SAM Plugin is required to make this work or are you guessing it might be due to "sam advanced metering" being one of the Check Definitions involved?  The Asset Management plugin is installed.

[Curtis Paul1]

Regarding updating check-allow-list.json

https://docs.servicenow.com/bundle/rome-it-operations-management/page/product/agent-client-collector/task/acc-generate-allow-list.html

So how does the agent get the check allowed list in the first place?  Why would this need to be a manual update of the file?  Using "an automation tool"?  lol...

[Curtis Paul1 · Accepted solution]

I was looking at the CMDB data for the agent computer CI in question and it appears Software Installed eventually got populated.  So I suspect it was the "sam advanced metering" check that provided that data considering it had ,installed_software OOB.

So despite having the same Policy interval, they ended up executing at separate times.  Data collection for the two collections in question is 24 hours (86400 seconds).

The test in question was a newly installed Agent yesterday, so on the second check cycle both Enhanced Discovery and the SAM discovery occurred where as for whatever reason the first interval only executed/returned data for Enhanced Discovery.