Agent Client Collector file distribution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2024 05:07 AM
Hi, my use case is that I would like to have on each ACC agent a file, where will be stored information about to which company related ACC Agent belongs to.
I have noticed that on each agent, there is a "C:\ProgramData\ServiceNow\agent-client-collector\cache\config-files" dir, which is created together with ACC Agent installation.
What is the purpose of this folder?
My intent is that on MID server i will create a file and this file will be propagated to all connected ACC Agents.
In the same manner, as I attach file on MID server to path "...\agent\static\acc_plugin\all\all\all\all", which is propagated to the cache folder on ACC Agent, however this is done through ACC Policy and I don't want to do that in this way, as the company record will vary based on the company the agent belongs to and I will need f.e. 30 different ACC Policies as I have 30 companies.
If there will be a file containing that company, I will read it through read-file.rb script.
Any thought please?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2024 09:47 AM
Hi, you'll have better luck getting a response to your question by posting it in the ITOM forum. Although Agent Client Collector can update CI records, it is an ITOM solution and not part of the CMDB.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2024 07:37 AM
@Doci1: this feature is now documented here. The main feature is to pass config / metadata information to the agents when running a check definition, without having to embed them as parameters in the check definition itself. I believe this is the same config file that is retrieved by all the MIDs with ACC capability within that domain. You can create 30 distinct config files for each domain, assuming each of the 30 companies have their own one. From there, all the agents executing the check will download the same config file that is associated with their domain.