cancel
Showing results for 
Search instead for 
Did you mean: 

All McAfee agent 4.8 failed to communicate with ePO server 5.3

Jump to solution

We recently migrated from ePO 4.6.8 to ePO 5.3 using upgrade compatibility tools following steps documented in KB82808

1. Old ePO server (4.6.8)

  • Server Hostname: epo001
  • ip address: 10.10.10.32
  • Win2k3, 32-bit

2. New ePO server (5.3)

  • Hostname: epo002
  • ip address: 10.10.10.37
  • Win2012, 64-bit

3. Database in other server running in SQL server 2014

The migration has been done, and I can access ePO 5.3 console on the new ePO server.

However, all the existing agent on all systems are failing to communicate with ePO server. I noticed all the agents are still using the epo001 and IP as the handler, but tried updating the DNS pointing to epo002 ip address is not solving the issue either.

I also tried to install new agent (5.0.4) that is generated directly from the new ePO server, the handler has been pointed to epo002 by default and say no failure in communication to ePO server but they got no policies, and the client hostname is not added to the system tree as well.

I have a very limited knowledge to ePO and I've tried to find some useful logs to troubleshoot this agent-server communication issue but so far I can't find any. Please kindly advise

1 Solution

Accepted Solutions

Re: All McAfee agent 4.8 failed to communicate with ePO server 5.3

Jump to solution

Hi everyone,

I am sorry for the late followup. After a few days of troubleshooting and lots of googling I found this thread .. the root cause was server migrated under different hostname, so it is mandatory to re-generate the SSL certificate used by agent handler for agent-server communication. As suggested, I followed KB66616 from step 8 onwards, and I can confirm that the problem is solved!

Thanks for your time!

4 Replies

Re: All McAfee agent 4.8 failed to communicate with ePO server 5.3

Jump to solution

Hello

did you select force install over existing versions when you deployed the new agent from the new epo ?agent.jpg

did you run the standlaone package with the command line switch forceinstall

framepkge /install=aegnt /forceinstall

Re: All McAfee agent 4.8 failed to communicate with ePO server 5.3

Jump to solution

framepkg.exe /install=agent /forceinstall

apologies finger trouble

Reliable Contributor tao
Reliable Contributor
Report Inappropriate Content
Message 4 of 5

Re: All McAfee agent 4.8 failed to communicate with ePO server 5.3

Jump to solution

You may have already done this or confirmed this - is the agent (5.0.4) extension checked in?

If this information was helpful or has answered your question, please select Accept as Solution. This will assist other memebers

Re: All McAfee agent 4.8 failed to communicate with ePO server 5.3

Jump to solution

Hi everyone,

I am sorry for the late followup. After a few days of troubleshooting and lots of googling I found this thread .. the root cause was server migrated under different hostname, so it is mandatory to re-generate the SSL certificate used by agent handler for agent-server communication. As suggested, I followed KB66616 from step 8 onwards, and I can confirm that the problem is solved!

Thanks for your time!

More McAfee Tools to Help You

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community