Epolicy 5.3.3 requirements

[ghtr]

Hello,

Can somebody please provide the requiments (server/sql) for epolicy 5.3.3, or provide a link to this infomation.

I need to understand if 5.3.3 can be installed on server 2016 and cant find any documentation for 5.3.3 on the McAfee site.

many thanks

[cdinet · Accepted solution]

Yes, support for Windows 2016 and sql 2016 were introduced with 5.3.3.

[jmcg]

For my personal curiosity, why do you want to install 5.3.3 instead of 5.9 or 5.10 ?

[ghtr]

We currently have 5.3.3 installed on server 2008 r2

The plan was to upgrade this to 5.10, then migrate to a new 2016 server using the snapshot recovery feature. However, the upgrade to 5.10 is failing.

I am now instead, migrating straight to 5.3.3 on the 2016 server using the snapshot recovery feature. I will then attempt an upgrade to 5.10 on the new 2016 server.

thanks

[cdinet]

Be sure to run iiscrypto on the new epo server and sql, choose best practices and reboot to ensure the tls protocols and ciphers are enabled for what epo needs.  Be sure also that your version of sql supports tls 1.2, as many versions need a hotfix to be able to support that.

[jmcg]

If you are going to a new server, just install a fresh ePO 5.10 on the new server and then, migrate every settings from ePO 5.3 to 5.10

After, you will just need to add ePO 5.10 in the 5.3 so you can transfer all your agent to the new server.

This HMO, is the best practise to upgrade it.

[ghtr]

Do you mean migrate with the snapshot recovery feature or create a new instance of 5.10 (with a new database)? If you mean to use the snapshot recovery feature, I was under the impression you could only perform a restore to the same EPO server version. 5.3.3 to 5.3.3 for example.

I also assumed the snapshot recovery feature transfers the agents for you?

Is there a mcafee article explaining your suggested method?

[cdinet]

Snapshot recovery is only for same version to same version.  Your easiest option, especially if your servername and IP are changing is to follow these steps.

1.  Restore your 5.3.3 server to the 2016 server with snapshot recovery and go ahead and upgrade it.

2.  With your old server still running, after the new server is set up, go to menu, agent handlers and edit the epo server to add published dns and IP for the new server to point your clients to it.

3.  You also might want to set up a dns alias to point to the new IP.  

This ensures all your same policies, etc are still in place just like the old server and easiest to redirect your clients to the new server without having to reinstall agents.

[ghtr]

Thanks cdinet

This is my intended method

[jmcg]

@ghtr

Well forget about "snapshot recovery feature" for any update, you do not need that.
Here the TODO list.

- Keep your 5.3 where is it.
- Create a new server (Windows 2016) and update it with Microsoft Update.
- Install ePO 5.10 on this new server
- Export every settings from 5.3.3 and also the communication key for the McAfee Agent
- Import every settings inside the ePO 5.10
- Add the ePO 5.10 server inside registered server in 5.3.3
- You are now ready to migrate any agent to the new ePO server using the "transfer function"

I'm not sure if there is a KB for this method.

PS: be sure to check every port for communication, you may need to add some rules in FW.

Also, this a 1 to 2 days work to do.

And also also, this method keep your old infra until you migrate, so you can go back easily if there is a issue