McAfee ePolicy Orchestrator - Fails to Install

Hi,

 I've just purchased McAfee Complete Data protection for a care company who use remote laptops during the weekend for On call managers. Due to the nature of the staff i really brought it for the encryption, but i figured installing the ePolicy Orchestrator might be worth it.


I've installed a new instance of SQL Server 2008 R2 Express SP1 but every time i try and connect to it (even after restarting the server) it says that the database is not the required version. Does it not install on SQL server Express? As the installation guide implies it will install. What things could i check? The server is SBS 2011.

If i excecute 'select @@version' it does say SQL Server 2008 R2 SP1'.
 

And really, is EPO required or should i just install the encryption on the laptops.

 

Thanks,

 

Josh
LVL 1
joshhoughAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
btanConnect With a Mentor Exec ConsultantCommented:
the minimal spec should be below

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

Microsoft Windows 2008 Server (64-bit) - Service Pack 2 or higher
Microsoft Windows 2008 Server Release 2 (64-bit)
Microsoft Windows 2012 Server

ePO only supports processors that use x86 or x64 compatible architecture. Itanium processors use the IA64 architecture and are not supported.  

Windows SBS 2011 is a suite that contains Windows Server 2008 R2 Standard, Exchange, SQL, and so on. Because ePO supports the Windows 2008 R2 operating system, ePO 4.6 (and later) is supported on platforms running Windows SBS 2011.

ePO 5.0 requires Service Pack 1 (or later) for SQL 2008 and Expresss

i was also looking through this mcafee forum and the last reply may helps, I did not deep dive in to the doc though but I do suggest raise support case as this will not be trivial and to ensure all are well covered ...

https://community.mcafee.com/thread/59666
0
 
btanExec ConsultantCommented:
you may want to catch this [1]. ideally centralised mgmt by EPO make senses but if the remote users are of small pool may not be worthwhile, but the central back of recovery key [2] (except for user local key not centrally generated) is critical and can be exported.

[1]SQL permissions required to install and use ePO
https://kc.mcafee.com/corporate/index?page=content&id=KB75766

[2]Encryption key types in Endpoint Encryption for Files and Folders 4.x
https://kc.mcafee.com/corporate/index?page=content&id=KB72668
http://kc.mcafee.com/resources/sites/MCAFEE/content/live/PRODUCT_DOCUMENTATION/24000/PD24207/en_US/ee_700_scripting_guide_en-us.pdf?searchid=1382853672740
0
 
joshhoughAuthor Commented:
Hi,

Thanks for your help. I've tried the above after you gave the link and it hasn't resolved the issue. To be sure i have even created a second user with the above permissions and it hasn't resolved it.

I've attached a screenshot to show the error i get with the configuration i have. Even using the SQL 'sa' account (which i can login to the SQL Management console with) doesn't work.

Starting to get a bit frustrated with it now :(

Cheers!
epo.png
0
All Courses

From novice to tech pro — start learning today.