cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
rbl
Level 9
Report Inappropriate Content
Message 1 of 12

Migrate epo 5.9.1 to 5.10 on a new server

Jump to solution

Hello,
I would like to replace my ePo 5.9.1 server, which is running on a Windows Server 2012R2 with epo 5.10, which will run on a Windows Server 2019.
What is the best way to proceed here?
Can I simply transfer the configuration from 5.9.1 to 5.10?
Do the client agents automatically notice the change?
What else needs to be considered during such a move?
Questions about questions...

2 Solutions

Accepted Solutions
cdinet
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 11 of 12

Re: Migrate epo 5.9.1 to 5.10 on a new server

Jump to solution

Ok, then follow the kb to see what is happening with communication.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

View solution in original post

rbl
Level 9
Report Inappropriate Content
Message 12 of 12

Re: Migrate epo 5.9.1 to 5.10 on a new server

Jump to solution

The agent logs showed "request failed with curl error <7>" among other things, but I could not fix the errors with the suggested solutions.I will now re-roll out the agents from the new ePO server.
Thanks a lot for the help.

View solution in original post

11 Replies
cdinet
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 12

Re: Migrate epo 5.9.1 to 5.10 on a new server

Jump to solution

There are a couple of ways you can go about this.

1.  Upgrade your existing server to 5.10, then back everything up and restore it to the 2019 server keeping either servername or IP the same as old server.  That should keep everything as it is.

2.  Build new server, then transfer config, policies and tasks first (export/import) so that everything is the same, then transfer the systems.

https://kc.mcafee.com/corporate/index?page=content&id=KB79283

Keep in mind that 5.10 has different tls requirements than 5.9.x and update 11 even has tighter requirements, as old tls versions and ciphers were removed.  Please refer to https://kc.mcafee.com/corporate/index?page=content&id=KB91519 for tls requirements for epo and sql on 5.10.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

rbl
Level 9
Report Inappropriate Content
Message 3 of 12

Re: Migrate epo 5.9.1 to 5.10 on a new server

Jump to solution

Thank you for the tips.
I still have one question.
How can I tell the agents on the Windows clients that a different/new ePo server is now responsible for them?

cdinet
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 4 of 12

Re: Migrate epo 5.9.1 to 5.10 on a new server

Jump to solution

The transfer systems option gives them the keys and sitelist of the new server for them to connect to.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

rbl
Level 9
Report Inappropriate Content
Message 5 of 12

Re: Migrate epo 5.9.1 to 5.10 on a new server

Jump to solution
cdinet
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 6 of 12

Re: Migrate epo 5.9.1 to 5.10 on a new server

Jump to solution

Yes, that is the KB I gave you in the beginning.  Let us know if you run into any problems.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

rbl
Level 9
Report Inappropriate Content
Message 7 of 12

Re: Migrate epo 5.9.1 to 5.10 on a new server

Jump to solution

So, the new ePO server is up and running.
I have now registered the new ePo server on the old server (How to transfer computers from one ePolicy Orchestrator server to another) and want to transfer a test client to the new ePo server.
Unfortunately the client does not appear on the new ePo server 😞
What could be the reason for this? Which logs do I have to look at to find the error?

 

rbl
Level 9
Report Inappropriate Content
Message 8 of 12

Re: Migrate epo 5.9.1 to 5.10 on a new server

Jump to solution

Maybe the problem is with the secure agent port .
The old server communicated with the agents via port 443 , the new server must use port 444 for communication.

cdinet
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 9 of 12

Re: Migrate epo 5.9.1 to 5.10 on a new server

Jump to solution

That should not matter as the transfer systems would give the agent the new sitelist with new port.  Did you also import the agent communication keys from old server into the new server?  Otherwise you need to look at the agent logs for communication problems.  See KB90603

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

rbl
Level 9
Report Inappropriate Content
Message 10 of 12

Re: Migrate epo 5.9.1 to 5.10 on a new server

Jump to solution

Yes, I have imported the keys as described in the KB article. (Don't be surprised, is a German system ;-))McAfeeKeys.png

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

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