The ODBC wizard doesn’t save any credentials - the username/password you enter there for “SQL Authentication” are only used to test the ODBC connection and then are discarded.
There are registry values that BigFix uses to store the database username and password, usually configured during setup…BESAdmin Tool can set the password, but you may need to update the registry to include a SQL username manually.
I should be able to post a bit more detail shortly.
Configure the username as ‘sa’ by creating a REG_SZ value…
Key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BigFix\Enterprise Server\Database
Value Name: User
Type: REG_SZ
value: sa
If you’re also running Web Reports on the machine, there’s a second place to set the database username:
Key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BigFix\Enterprise Server\FillAggregateDB
Value Name: username
Type: REG_SZ
value: sa
Value Name: password
Type: REG_SZ
value: clear-text password for ‘sa’ account - will be encrypted when Web Reports starts up
All the parameters are optional except /updatepassword /type=server_db, you’ll be prompted for the PVK path, PVK password, and new Database password.
When done, run BESAdmin without any options to verify it connects to the database, and then restart the BigFix Server services (BESRootServer, FillDB, and GatherDB)
Restart the Web Reports service and verify the ‘password’ value under FillAggregateDB gets encrypted.
Hope this helps, let us know if you have any trouble with it.