Note: BigFix Consoles 8.2 and above no longer use ODBC to connect to the database (instead they connect to the server using HTTPS).
To make accessing a database easier, Windows uses a DSN to save authentication and setting information for a database connection. Doing so allows users to connect with a database once and save the information for future use. DSNs are stored locally on the computer used to reach the database. Each DSN is identified by a name, like "bes_bfenterprise".
The ODBC is a standardized interface to the database developed by the SQL Access group. DSNs are stored setting for using an ODBC. BigFix may use several DSNs to connect to the same database. The reason for this is each DSN has different settings and each one may be used to connect to the database in different ways. For example, the primary distinction between the "bes_bfenterprise" and "bes_EnterpriseServer" DSNs is that "bes_bfenterprise" connects to the BigFix database using Windows NT authentication and "bes_EnterpriseServer" connects using SQL authentication.
You can view your DSNs by running Control Panel > Administrative Tools > Data Sources (ODBC), which will launch the ODBC Data Source Administrator tool. The first tab, "User DSN", specifies DSNs that are available only to the currently logged in user. Most of the BigFix DSNs will be found and created in the "System DSN" which contain DSNs that are available to anyone using the machine and by the System account of the machine itself. Only a user with Administrative privileges can make changes in the "System DSN" tab. If you create a new DSN here it will use "SQL Server" as a Driver.
For 64-bit Windows systems, use the 32-bit version of the ODBC tool to configure teh System DSNs:
The follow portion details the components of an DSN that are used by BigFix and how BigFix uses those components. If you add a new "System DSN" or configure an existing one, the following fields will need to be configured for use with BigFix in the Microsoft SQL Native Client DSN Configuration:
The name of the DSN is used to identify stored DSNs. BigFix looks for DSNs with certain names like "enterprise_setup" and "bes_bfenterprise". Certain BigFix components will expect a DSN with a certain name to exist and will automatically attempt to use those DSNs to connect to the database. Please read the reference guide below for more specific details. The "bes_" prefix is special. The BigFix Console and BigFix Admin Tool will allow to use any DSN with the "bes_" prefix on it. It will display these DSNs without the prefix when launched.
This field specifies the database the DSN will go to. This field needs to be the machine running BigFix's database. In BigFix 4.1, the default value of this field will be the BigFix Server machine. If you are setting up a remote database you will need to change this field to point to the database machine for all DSNs that are created automatically by BigFix installers. Any upgrades will reset the DSNs to point to the BigFix Server. Therefore, you will need to reset these DSNs after any upgrades to the BigFix Consoles and BigFix Server.
There are two options for this field, Windows NT or SQL authentication. The Windows NT authentication method will automatically use your Windows Login and Password as the Login ID and Password to the database. The SQL authentication method will require a Login ID and Password be supplied manually every time a connection to the database is made. You can set up the BigFix components to use either of these two authentication methods. We recommend you choose one approach and try to maintain use of that scheme for configuring DSNs. The exception is the "bes_EnterpriseServer" DSN which should always use SQL authentication.
The default database is the database instance that this DSN will attempt to use. This field will be set to be one of the two BigFix database instances which are named "bfenterprise" and "BESReporting" by default. If the DSN is going to be used for Web Reports it will likey default to the "BESReporting" database instance. Otherwise the DSN should use "bfenterprise" by default. The default database specifies which database instance your DSN will use. Your authentication information will be used to access this database instance as well. There are two levels of permissions on SQL Server, the first is to access the database itself and the second to access database instances.
Note: Notice that the field used to specify a Login ID and Password on the second screen of the DSN Configuration setup is not listed above. You will NOT need to check the box to "Connect to SQL Server to obtain default settings for the additional configuration options." and provide an ID and password. The only use of checking this box would be in testing the connection on the final screen where the Login and Password provided will be used by the "Test Data Source..." option. The Login ID and Password you provide will not be stored with this DSN! It is used to obtain default settings and test the DSN but after configuration of the DSN is complete the information is discarded. If you set the DSN to use SQL authentication, provide a Login ID and Password and then successfully "test" the DSN, then you have verified that the Login ID and Password can be used to connect to the database but you will have to provide the same credentials every time the SQL authenticated DSN attempts to connect to the database.
|BigFix Component||DSNs Used||Authentication Methods|
|BigFix Server Installation||enterprise_setup||NT|
|BigFix Server||bes_bfenterprise||NT or SQL|
|BigFix Console||any DSN beginning with "bes_"||NT or SQL|
|BigFix Administration Tool||any DSN beginning with "bes_"||BigFix 4.1: NT (SQL not fully supported). BigFix 5.0+: NT or SQL.|
(Note:the LocalBESReporting DSN contains configuration and login data, not data shown in Web Reports reports. In Web Reports on the "Database Settings" page when adding a new database or configuring a remote database, use the "bes_bfenterprise" DSN.)
|BigFix 4.1: NT. BigFix 5.0+: NT or SQL.|