Agents being registered with IP or FQDN seemingly randomly

[TristanMcHardie]

When new Agents are registered for Windows machines, their address field is seemingly randomly given either the machine's FQDN or IP. Machines that are virtually identical are registering with a mix of both IP or FQDN. My agents list looks a bit chaotic because of this. I can manually rename the IP addressed agents to make them identifiable, but the address field is not editable.

While its mostly a cosmetic issue, it's a bit annoying when the IP address is used instead of a human-readable name, and the address field propagates to other parts of AGM, e.g. Discovered Components will display "ArcGIS Server @ x.x.x.x".

I suspect this might be an issue with how Windows is reporting the machines' addresses. If so, I might be able to fix it on each machine.

What method does ArcGIS Monitor Agent use to acquire an address on Windows?

[GarrettMcBride]

I had a simliar issues but it wasn't using the IP it was using the external web adaptor on some machines and then the internal web adaptor machine name on others.  All configured the same way and was driving me crazy.  We did a few different things but ultimately for my situation unistalling and reinstalling the web adaptors fixed our issue.  Unregister server with monitor, stopped agent on AGS machines, reinstall web adaptor, reregister with Monitor.  We also deleted the bindings on the IIS box (internal and external ports for 443).  I don't think that influenced anything but was changing too many things at once while troubleshooting.  

[TylerTheobald]

I'm going through the same behavior in our environment when adding agents.  I believe, at least for us, it is partly due to reverse DNS not being consistently done when new servers were built. 

[TristanMcHardie]

Pleased I'm not the only one. Do you think it's Windows (self-reporting) or your DNS itself that's inconsistent?