Agent Client Collector Discovery and JEA

[NicoleHollihan]

Hi everyone,

We’ve recently installed Agent Client Collector (ACC) on a couple of test Windows servers and configured a test MID Server specifically for ACC. These Windows servers were previously being discovered using JEA with ServiceNow Discovery, and that’s still the case even after ACC installation.

Here’s what we’re seeing:

• ACC is installed and running on the test servers.
• The MID Server is configured for ACC and appears healthy.
• When I manually change the Discovery Source on the CI to "ACC-Visibility" and run discovery, it reverts back to "ServiceNow" after the scan completes.
• It seems like ACC is not taking over the discovery process as expected.

Question:
What am I missing in the configuration or setup that would allow ACC to take over discovery and properly set the Discovery Source to "ACC-Visibility"?
Are there additional steps needed to prioritize ACC ? I have also set Reconciliation rules to use ACC as priority 1 in the data manager. 

Any insights or guidance would be greatly appreciated!

Thanks in advance!

[NicoleHollihan]

Hi Pratiksha,

We would like to continue to use JEA, however,  have set a reconciliation rule for ACC to be priority 1 but Servicenow still runs. Not sure what I am missing. Linux seems to work fine but the Windows servers keep reverting back to Servicenow discovery.