While attempting to install EPO 4.5 (server A) using SQL Authentication to a SQL 2005 SP3 server (server B - separate server from EPO 4.5 install server), I receive "The database user specified does not appear to have sufficient rights".
The provided SQL Authentication username has "DB Owner" rights to the SQL 2005 SP3 application on Server B, and I can log into SQL Manager using the provided account (via SQL Authentication) and create a database. The provided SQL Authentication username also uses a "simple" password. I can also see and select the SQL 2005 server from EPO 4.5 install "Database Server" drop down menu.
In addition, I'm also logged into the EPO 4.5 install server (server A) as "local admin", and can telnet to port 1433 on the SQL 2005 server (server B).
Not sure what else to do to to make SQL Authentication to work upon installing EPO 4.5......
Any advice would be greatly appreciated......
I spoke with some SQL Server 2005 DBAs. The resolution was to grant the SQL Authentication account the "sysadmin" role (and no other) on the SQL 2005 Server.
I then relaunched the EPO 4.5 install and the software created the EPO DB and tables on the SQL 2005 Server (Server B).
You were right about having the account with sysadmin privilege for installation of ePO 4.5. However, sysadmin affectively means the account has full privileges over your entire server.
So after installation is complete, you would revoke the sysadmin role and have the account database owner rights (dbo) on the ePO database (specifically the account would need db_datareader, db_datawriter and db_ddladmin roles at the minimum). Additionally, the database user should have db_datareader and db_datawriter on the tempdb database - as ePO uses temporary tables and views.
Hope that helps
Existing Knowledge Base article KB59903 SQL permissions required to install and use ePolicy Orchestrator 3.6.1, 4.0 and 4.5 is being updated to include this information.