To The Lab: ServiceNow Agent Client Collector for Visibility

[@ashupakasma]

Great understanding on ACC, thanks for showing all details using lab. Prost! Danke..

[@122004nilanjan]

Do you have any vidoes for installation of ACC in the linux Machine with RHEL 9 version.. ?

[@pavanakodila7834]

How to run a powershell script from check definition to pull the machine data in service now?

[@howardelton6273]

This is a really interesting candidate to replace the SCCM integration. Since we have ITOM visibility and will be retiring SCCM from our environment in the near future, we have been looking for agent based alternatives. This seems like a good fit. However Agentless Discovery and the SCCM integrations work with both PROD and DEV instances of ServiceNow. From what you have shown, it seems that ACC clinet would only be able to point to one MID server (e.g. PROD) so testing changes in DEV will prove more complicated. Have I understood this correctly?

[@einarpartners7707]

Hi, thanks for your great questions. Yes, you are 100% spot on! The ACC can be configured with a list of multiple MID Servers, however this is only for fail-over purposes. Meaning, if the first MID Server on the list fails to connect, then the ACC will try the next one on the list. You can find all these details in the acc.yml.example file that is provided with every ACC installation.

[@philippetherond8355]

@@einarpartners7707 I suppose it may be possible to install more than one ACC on the same client machine?