ePO 5.10 disaster recovery failed on new server

[ssedhai]

@cdinet 

I am using the certificate signed by McAfee or ePO itself and I changed that after first failure. Thank you for your help till this time and I am going to open a ticket with the McAfee support. 

[ssedhai · Accepted solution]

@cdinet @YashT 

I am able to resolve the problem now and I have successfully installed the ePO on new Windows Server 2019 using DR method and also installed Agent Handler on DMZ as well. 

The problem while installing ePO was I was using the SQL account with sysadmin role which I replaced with "SA" account and just by doing this there was no error and the installtion is successful. I later change the "SA" account with another account after installation. But, I am still thinking here how the other account with sysadmin role didn't work but the "SA" account work later? Is it compolsory to have "SA" account while installing ePO using DR method? 

Also, in DMZ I encountered problem and it was like "no connection to the SQL server" which I resolved by editing the host file. Thanks for your help and suggestion guys and thanks to McAfee Support as well. 

[cdinet]

Glad it is resolved!  If the first account you used was a Windows account instead of sql authentication, that might explain the failure if that account is not also a local admin with log on locally rights to the epo server. As for adding host entry in dmz, that is a normal requirement for a system in dmz where there is no dns resolution.  Good job!

[Former Member]

---

@MyFedLoan wrote:

If that still fails and you can't find reason, you can open a ticket with McAfee so we can analyze logs and go through the install with you.  Otherwise you can also try the manual restore method of kb66616.  If you go that route, you need to install to the same directory and drive path that current install is on.  If you don't want to do that, you can follow kb71078.

---

The error ini file is the main error that caused the failure.  For services not starting, a live orion log is best to look at for that.  The snapshot may not have been a current or complete one, or any other reason.  Once you upgrade the OS, be sure to run IISCrypto on the server (as well as sql server if you haven't already), choose best practices, then reboot.  That will ensure correct ciphers and tls protocols are enabled.