I’m setting up a test environment where I have two Windows 2008 server and one 2003 with SQL 2005. The 2003 server is the database for the BigFix installation will the BigFix server itself is installed on a Windows 2008 64 bit os. I tried installing BigFix a couple of times and failing because of rights issues on the database server. After making the domain admin group a part of all sql groups on the sql server I finally was able to install BigFix successfully. I’m not able to find any up to date documentation that describes the installation process with remote database server.
Also something that is strange is that the BES Diag reports that Windows 2008 is not supported and that TCP/IP is not enabled on the sql server.
The remote SQL server is completely independent of the BigFix install. Generally we let the install process use the SA account to log in and create the database etc. Once that is finished we use a DSN to connect to the database so that the login information isn’t stored in the registry. There used to be a set of tsql scripts that could be used by someone that had access to a specific database but not the sa account. I don’t know if that’s still the case.
The BES Diag tool just needs to be updated to report that Windows 2008 is supported. On the BES Server System Requirements page it specifically states Windows 2008 is supported and we just ignore the warning.
I tried this but BES uses the sa user name and password which is in clear text in the registry.
When Deleting the registry key Computers were able to register with the BES server but it was not moved to the database. This operation isn’t really straight forward and should be better.
I created the ODBC DSN connections but it didn’t seem as if the BES server and console used these connections.