Q1: Is MS Server 2012 R2 supported?
A1: I installed EPO 5.1.1. It's working.
Check Ref.No. 939815
Q3:Is MS SQL 2012 Express supported?
A3: From Installation Guide:
McAfee ePO supports any edition of these Microsoft SQL Servers.
• Microsoft SQL Server 2008, with Service Pack 1 or later
• Microsoft SQL Server 2008 R2
• Microsoft SQL Server 2012
VMware ESXi 5.5 supported is supported by McAfee EPO 5.1
Virtual Infrastructure software versions
Virtual software ePO 4.6 ePO 5.0 ePO 5.1 VMware ESX/ESXi 5.x (and later) Yes* Yes Yes VMware ESX/ESXi 4.x Yes No No VMware ESX Server 3.5 Yes No No VMware Workstation 5.0 No No No Microsoft Virtual Server 2005 R2 with SP1No No No Windows Server 2012 R2 Hyper-V
Yes Windows Server 2012 Hyper-V No Yes Yes Windows Server 2008 R2 Hyper-V Yes Yes Yes Windows Server 2008 Hyper-VNo Yes No Citrix XenServer 6.0 No Yes Yes Citrix XenServer 5.5 Yes No No
*ESX 5.x is supported with ePO 4.6.6 and later, which is available on the McAfee downloads site.
Please follows this link McAfee KnowledgeBase - Supported Platforms, Environments, and Operating Systems for ePolicy Orchestrator for more details.
Thank you guys for the fast answers.
It looks like i could need some help with the installer connecting to the database.
Can you help me out what i should enter in the red marked fields with the information given (marked orange)?
Thx in advance
The SQL 2012 Express is installed on the same server like i'm trying to install the epo server.
For database server you will enter the name of your server (dns name): ie myserver
For database name you will type in: epo
The udp port 1434 it says not accessible, due to host name given in the database server.
Change to IP address instead of hostname and proceed further to over come this error and proceed further.
If you have more queries, please check another community link, which resolved the similar issue...
Thx for your answer rgc, but this didn't work for me....
Are you using windows authentication for the DB connection or SQL? Try setting up an account for either and just testing for the heck of it.
Try with SQL authentication and the steps follow as per the document as attached.