1 of 1 people found this helpful
The connection attempts (to new ePO server) would be logged locally on each agent's logs. (\users\All Users\McAfee\Common Framework\DB\Agent_hostname.log)
Look for lines like this: Connecting to site: EPO_SERVER_IP_ADDRESS
You'll probably see errors connecting to the old server, then the agents will have tried connecting using the DNS name and NETBIOS name.
You would also see the agents communicating with the NEW ePO server in the NEW ePO server's logs: \Program Files (x86)\McAfee\ePolicy Orchestrator\DB\Logs\Server.log
Look for lines that look like this: "Received [PropsVersion] from HOSTNAME"
As far as pointing all your agents to the new ePO server (with new name and IP), the easiest was is to create a CNAME entry for the OLD server pointing to the NEW ePO server's DNS name and to make sure the IP of the old server does not respond on the network anymore.
Agents try to connect to the ePO server using the last known IP, then DNS name or NETBIOS name. If the old IP does not respond, they will do a DNS query for the ePO server name. By having a CNAME with the OLD server name, pointing to the NEW ePO server name, they will find their way to the new sevrer and establish a connection (assuming the ePO keys are the same, which they should if you used an imaging software).
Hope this helps.
Awesome idea on the dns entry... Thanks !!! We are doing that and a restart of the frame service might make it go!