BackupExec will set there database to hidden, and a login mode of 0 not 2. So this is why we dont see it.
I would highly recommend letting epo install its own instance of SQL, separate from Backupexec. Thus why our installer will create an instance named servername\EPOSERVER.
there are alot of other security benifits to using a seperate instance as well.
The only option would be to run the SQL Express installer beforehand and manually set up the instance. By default, the ePO installer will call the instance "EPOSERVER" but you can name it whatever you want. Then, once the new instance is installed, run the ePO installer again and choose to install the ePO Db to that newly created instance.
Sorry, that takes me back to my original question. I did do that and set up a new instance called epodb. Then I got the error.
When you get the "minimum requirements message" check the %temp%\McAfeeLogs\EPO450-Install-MSI.log for any additional messages.
Okay guys, my bad
I looked at the SQL configuration in the SQL Server Configuration Manager. The instance I had created called epodb had the TCP/IP Protocol set to disabled by default.
Not sure why?
In any case, I set it to enabled, restarted the mssql instance service and then re-ran the installed from scratch and its working.
Thanks for your help with this.