I think I figured out what my problem is. At one point in the process, the agent is trying to connect to my server by a shortened name instead of the full name, i.e. advmepo instead of advmepo.(domainname).usu.edu
I have no idea where to go to change that so it will connect properly.
With epo 3.6.1 you could add a line in the server.ini with the ip of the server, something similar to serveripaddress=10.10.10.10, to force the agents to use this ip. The problem is that the agents must contact one time to apply this config
It should tell is the local server name, as well as the fully qualified name and the IP address. It should try all these before it fails, you will be able to see this in the Agent_<computer name>.log file that is located in the DB folder
Well, it has the server listed in there correctly, the IP in there correctly, and everything, but it still fails when it connects. It says 'Bad IP address data in the registry' and 'Agent communication failed, result=-2147467259'
I am getting very frustrated with ePO 4.5 here. I may have to go back to an older version and see if that fixes it. It isn't that hard with the server being a virtual server, rather than physical hardware.
The "bad ip address" message is referring to the registry on the client machine... is there a valid IP address in the HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\ePolicy Orchestrator\Agent\IPAddress reg value?
In that case something is either preventing the agent from picking up the IP address from the machine, or from writing it to the registry. Restart the framework service on an affected machine and after two or three minutes check the agent_<MachineName> log. Are there any relevant messages?