How does the ACC agent match to a host?

[Morgan2]

Hey guys,

My team is trying to PoC the Agent Client Collector, and have run into a bit of a problem. We have the proper modules installed, everything setup and the agent installed on 3 Windows laptops. 2 laptops are full remote, and 1 is mostly in office. For the in office laptop, the host is always correct. For the 2 remote laptops, the host starts out correct, but somehow updates to an incorrect host over the course of a day or so. If we click the "Collect host data" button, they will correct themselves, but only until whatever is running once again runs. My question is, what magic is happening that could cause the system to get confused? The hosts that are being incorrectly associated don't have the agent installed. Appreciate any insight the community might have. Thanks!!

[vNick]

Hey Chuck - yes, it's a bit confusing and I, unfortunately, can't speak to why the inconsistency between discovery data and ACC-V data (I'm not on the product side).

I've advised my customers to create reconciliation rules on the hardware (or at least computer or server) classes to have ACC-V be a lower priority source for the identification fields, so that if they're already populated, ACC-V cannot overwrite them... only if they're empty or it's a new CI can ACC-V populate data on those attributes.

[chuckn]

Awesome. We'll give that a go. Thank you so much!!