Managing Windows ODBC with BigFix

Technote (FAQ)


How to add a new "System DSN" or configure an existing one


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. TEM looks for DSNs with certain names like "enterprise_setup" and "bes_bfenterprise". Certain TEM 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 however. The TEM Console and TEM 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 TEM's database. In TEM 4.1, the default value of this field will be the TEM 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 TEM installers. Any upgrades will reset the DSNs to point to the TEM Server. Therefore, you will need to reset these DSNs after any upgrades to the TEM Consoles and TEM Server.

Authentication Method

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 by supplied manually every time a connection to the database is made. You can set up the TEM components to use either of these two authentication methods. It is recommended 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.

Default Database

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 TEM database instances which are named "bfenterprise" and "BESReporting" by default. If the DSN is going to be used for Web Reports it will likely 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 Native Client" 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.

Reference of TEM Components and DSNs

TEM 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_" NT or SQL.
Web Reports LocalBESReportingServer NT or SQL.

Historical Number


Document information

More support for:

Tivoli Endpoint Manager

Software version:

All Versions

Operating system(s):

Platform Independent

Reference #:


Modified date:


Translate my page

Content navigation