This content has been marked as final. Show 5 replies
You mean you get another (duplicate) entry for the 3.7 solaris agent appearing aswell as the one that it was orginally using in the directory?
Does the server have dual nics running different IPs?
No, the existing agents get replaced. For example
In the ePO there is server1-agent, server2-agent.
After install a new agent at another server, in the ePO it becomes
The server2-agent is gone. If do a agent wake up call, server3-agent will get replaced-become server2-agent again.
I have the same problem right now.
I have around 20 new servers ("clean" installed, not cloned) that I have installed the ePolicy-agent to. The agents turn up on the ePo 3.6.1 console, but - for example - when server 10 has turned up it is getting overwritten by the next one, server 11. Server 10 is nowhere to be found anymore.
If re-adding server 10 manually to the console, or re-installing the agent on the server it will turn up on the console, but it will overwrite some other agent in turn...
Very strange! Any help is much appreciated!
I know you say they are not cloned but still check the agent guid key on the servers for duplicates:
HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\ePolicy Orchestrator\Agent\agentguid
Are the 20 servers behind an ISA server perhaps where the IP of the ISA server is being taken to be the IP of the individual servers?
What does the epoapsrv.log file say about these agents?
in 3.6.1 it would be in the folder:
Program Files\Network Associates\ePO\3.6.1\DB\Logs
(you havnt given any version info on epo or CMA versions)
Sorry about that. ePolicy 188.8.131.52. CMA 184.108.40.2064.