Are you following these steps?
1 Open the folder where you extracted the contents of the ePolicy Orchestrator installation
2 Copy the AgentHandler folder to the intended Agent Handler server system.
3 Double-click and run Setup.exe. Installation activities take place in the background. When
they are completed, the InstallShield Wizard for McAfee Agent Handler opens. Click Next.
4 Accept the default destination or click Browse to change the destination, then click Next.
The Server Information page opens.
5 Type the machine name of the ePO Server with which the Agent Handler is to communicate.
6 Type the port to be used for server-handler communication. Port 8433 is the default. McAfee
recommends that you change the port designation. See the discussion of Ports in the Server
and Agent Handler requirements section.
7 Type the ePO Admin User name and password of a user with global administrator
privileges. If these credentials are to be used for the database as well, click Next to start
NOTE: These credentials must be identical with those used during installation of ePolicy
8 If you want to use different database credentials than those mentioned in step 7, follow
these additional steps:
a Deselect Use ePO Server's database credentials, then click Next.
b Type the name of the SQL database server.
c Select Windows Authentication or SQL Authentication, then type the credentials.
NOTE: These credentials must be identical with those of a previously defined SQL Server
9 Click Next. The installation process begins.
Yes done all that Alex.... Thanks...
I found out what the issue was, the agent handler needed to be on the same domain as my epo cluster and SQL Server... On any other domain or standalone and I could not connect in to the database... Strange as I didn't read anything about that in the documentation..
All sorted now, hope this helps others...
Is ePO configured to use Windows authentication to access SQL? If so then this could happen if there is no trust relationship. A workaround would be to configure an SQL account and specify it when installing the AH - that would let the AH machine stay out of the domain and still be able to access SQL.
1.if SQL configured with window authentication, AH machine should also be part of the same domain to access SQL DB.
and any account with SQL authentication will allow AH to connect to DB irrespective of domain membership.
Well you are right Bruce,Many other will find helpful hints from this discussion.
Strangely enough, not 1 SQL account seems to have the rights to allow this access to the DB. As soon as the proposed AH server is domain joined the process flies straight through... You don't have to even login to the domain for it to work either. Simply use a local account on the domain joined server and all you need is the EPO global administrator account and its fine... I have used the SA account and created a new account and given that all the privileges to the SQL DB. Still not working
The only thing I haven't done is changed the owner of the DB .. I don't want to break what is clearly working perfectly fine for everything else.. I'm not the most experienced with SQL 2008r2...
Can't find a single log either in SQL, SQL 2K8 server or the EPO Servers that can prove its being blocked..
I have also searched the EPO Logs in the program install DB directory.. Nowt!!
Confused.com is not the word!