We're having an issue with another IT Unit on our campus in which their "Common Base Agent" is not loaded.
This has not been a common issue among our IT unit, but our group is the product owner of IEM, so we are often enlisted to support these units with IEM issues.
We have narrowed down their issue as much as we possibly can at this point.
Their agents seem to work just fine when we test them, we've narrowed down that the issue is not the result of their image during deployment, they recently installed the agent via self-contained and we verified their agent is up to date.
They said they are having to run a command on almost all of their clients to get the CBA loaded, while this "technically" works, it is not a FIX. This is just a band-aid for a larger problem, and we are dedicated to help get this working for them.
According to the following article (How To: Fix the Common Base Agent Status Not Loaded Issue ), selecting "Use DNS" in "Agent Status Options" could be a fix if they cannot connect to the following url https://[client IP]:9595/, which they cannot.
However we are worried about what this might affect making this change. We know this will cause remote to connect via hostname rather than IP, correct?
Will we have to redeploy agents? What consequences could turning this on have?
Know that we not only support Centralized IT but several distributed IT groups across campus, so we are nervous about making a big change, when the consequences are not fully known.