Home
Configuration Guide
Learn how to configure BigFix according to your needs.
Additional configuration steps
These topics explain additional configuration steps that you can run in your environment.
Configuring FillDB
The FillDB process runs on the BigFix Server system and is responsible for storing the information returned from the BigFix Agents into the BigFix database.
Enabling FillDB parallel processing
On the BigFix Server, the FillDB process is responsible to run in a single thread the following activities.

Configuration Guide
Learn how to configure BigFix according to your needs.
- Introduction
  This guide explains additional configuration steps that you can run in your environment after installation.
- BigFix Site Administrator and Console Operators
  In BigFix there are two basic classes of users.
- Integrating with LDAP
  You can add Lightweight Directory Access Protocol (LDAP) associations to BigFix.
- Enabling SAML V2.0 authentication for LDAP operators
  Starting from Version 9.5.5, BigFix supports SAML V2.0 authentication via LDAP-backed SAML identity providers.
- Disabling local operators
  Starting from BigFix Version 10.0.8, this feature provides a mechanism where the creation and use of any local operator is prohibited in favor of LDAP-based operators.
- Using multiple servers (DSA)
  Some important elements of multiple server installations.
- Server object IDs
  The BigFix server generates unique ids for the objects that it creates: Fixlets, tasks, baselines, properties, analysis, actions, roles, custom sites, computer groups, management rights, subscriptions.
- Customizing HTTPS for Gathering
- Using the DHE/ECDHE key exchange method
  By default, BigFix 10.0 Patch 1 components use the DHE/ECDHE key exchange method if the version of the BigFix component on the other side of the SSL communication allows it.
- Configuring secure communication
- Real Time AV Exclusions
  BigFix Console, Server and Relay components of the architecture perform high volume file operations. This activity is a substantial part of the functionality that these BigFix architecture components provide.
- Downloading files in air-gapped environments
  In air-gapped environments, to download and transfer files to the main BigFix server, use the Airgap utility and the BES Download Cacher utility.
- Getting client information by using BigFix Query
  The BigFix Query feature allows you to retrieve information and run relevance queries on client workstations from the WebUI BigFix Query Application or by using REST APIs.
- The Plugin Portal
  The Plugin Portal is a new component introduced in BigFix 10 to help manage cloud devices as well as modern devices such as Windows 10 and MacOS endpoints enrolled to BigFix. For details on modern client management, see the Modern Client Management documentation.
- Extending BigFix management capabilities
  BigFix 10 delivers a few significant new functions for enhancing the visibility and management of devices on your network regardless of whether the devices are physical or virtual.
- Persistent connections
  The capability to establish persistent connections was added to the product.
- Relays in DMZ
  The capability to establish a persistent TCP connection between the parent relay in the more secure zone and its child relay inside the DMZ network was added to the product. This allows you to manage systems in a demilitarized zone (DMZ network).
- Working with PeerNest
  The BigFix Client includes a new feature named PeerNest, that allows to share binary files among Clients located in the same subnet. The feature is available starting from BigFix Version 9.5 Patch 11.
- Archiving Client files on the BigFix Server
  You can collect multiple files from BigFix clients into an archive and move them through the relay system to the server.
- BigFix Configuration Settings
  A number of advanced BigFix configuration settings are available that can give you substantial control over the behavior of the BigFix suite. These options allow you to customize the behavior of the BigFix server, relays, and clients in your network.
- Additional configuration steps
  These topics explain additional configuration steps that you can run in your environment.
  - Installing and configuring the email notification service
    You can use the email notification service to send automatic email notifications to notify you about the completion status of Baselines that you run. To use this notification feature, you must first install the notification service by running a Task. After you have installed the service, you must configure it by running another Task.
  - Configuring FillDB
    The FillDB process runs on the BigFix Server system and is responsible for storing the information returned from the BigFix Agents into the BigFix database.
    - Configuring the FillDB database performance
    - Increasing the size of the FillDB buffer directory
      The FillDB buffer directory temporarily stores reports from the clients before they are stored into the database.
    - Enabling FillDB parallel processing
      On the BigFix Server, the FillDB process is responsible to run in a single thread the following activities.
      - Configuring parallel FillDB
  - Configuring ODBC data sources
    How to use Open DataBase Connectivity (ODBC) to set up and configure ODBC Data Sources with BigFix.
  - Configuring the number of Web Reports results
    To avoid excessive use of memory when displaying Web Reports results on Explore Computers reports, you can configure the MaxReportResults keyword. This keyword sets the maximum number of rows that can be displayed in a web report. Its default value is 1000000.
  - Managing Daylight Saving Time (DST) for Web Reports
    By default, Web Reports track scheduled activity next attempt times using UTC rather than the local time zone.
  - FIPS 140-2 cryptography overview
    BigFix uses the BigFix Cryptographic Module to perform cryptographic functions throughout its environment.
  - Managing Client Encryption
    Server and relay-bound communications from clients can be encrypted to prevent unauthorized access to sensitive information. To enable it, you must generate a key and provide a value on clients for the setting named _BESClient_Report_Encryption.
  - Message Level Encryption (MLE) Overview
    Message Level Encryption (MLE) allows your Clients to encrypt upstream data using a combination of an RSA public/private key-pair and an AES session key.
  - Changing the Client Icon
    By default, the icon in the upper left corner of the client UI is the BigFix logo.
  - Client UI main actions
    The BigFix Client UI is used to display message boxes to the end users logged on to the client computer (including pre-action messages, action running messages, and restart/shutdown messages).
  - Optimizing the servers
    BigFix operates efficiently, with minimal impact on network resources. However, there might be installations that stretch the recommended configurations, where there are too many clients for the allotted server power.
  - Optimizing the consoles
    To be responsive, the console requires reasonable CPU power, memory, and cache space.
  - Managing Bandwidth
    File downloads consume the bulk of the bandwidth in a typical installation. You can control the bandwidth by throttling, which limits the number of bytes per second.
  - Managing Downloads
    BigFix uses several methods to ensure that downloads are efficient and make the best use of available bandwidth. Among other techniques, caching is used extensively by all the BigFix elements, including servers, relays, and clients.
  - Customizing HTTPS for downloads
    This page describes the usage of CA bundles in HTTPS downloads and how to customize them.
  - Creating custom client dashboards
    You can create custom Client Dashboards, similar to those in the console. Dashboards are HTML files with embedded Relevance clauses that can analyze the local computer and print out the current results.
  - Geographically locating clients
    Because clients are often deployed in remote offices, it is useful to create a property that lets the clients report their own location.
  - Locking clients
    You can change the locked status of any BigFix client in the network. This lets you exclude specific computers or groups of computers from the effects of Fixlet actions.
  - Editing the Masthead on Windows systems
    You can change default parameters stored in the masthead by using the BigFix Administration Tool.
  - Editing the Masthead on Linux systems
    To modify the masthead, run the following command as super user.
  - Obfuscating server passwords
    You can replace the passwords on the server with obfuscated passwords, by indicating the type of password that you want to replace and the new password.
  - Modifying Global System Options
    To modify a few basic system defaults, such as the minimum refresh time and the Fixlet visibility, perform the following steps.
  - Extending the BigFix License
    When you first request your action site license, you are issued a license for a specific period of time. Before your license expires, BigFix warns you, giving you sufficient time to renew your license.
  - Re-creating Site Credentials
    Private and public key encryption creates a chain of signing authority from the BigFix root down through the Site Administrator and including each console operator.
  - Creating special custom sites whose name begins with FileOnlyCustomSite
    You might delete special custom sites whose name begins with FileOnlyCustomSite that are generated to propagate files to agents accidentally or purposely, for example, when performing a gather reset. You can recreate them by using the PropagateFiles.exe tool.
  - Configuring Client CPU Utilization
    How to configure the amount of CPU the BigFix client uses on an endpoint machine.
  - Customizing Client UI message strings
    You can customize the Client UI message strings. It is possible to alter the English text output and also to change any of the localizable string translations by using the XLAT files for the Client UI. The Client UI XLAT files default location for a 64-bit machine is C:\Program Files (x86)\BigFix Enterprise\BES Client\BESLib\Reference.
- Migrating the BigFix Server (Windows/MS-SQL)
  This section details the steps and operational procedures necessary for migrating the BigFix Server from existing hardware onto new computer systems.
- Migrating the BigFix Server (Linux)
  This section provides basic information on migrating your BigFix Server from existing Linux hardware onto new systems.
- Server audit logs
  The BigFix Server generates a server audit log file which contains the access information (login/logout) and information about the actions performed through the Console or the WebUI by the different users.
- List of advanced options
  The following lists show the advanced options.
- Security Configuration Scenarios
  BigFix provides the capability to follow the NIST security standards by configuring an enhanced security option.
- Client certificate
  To comply with the modern industry standards, starting from product version 10.0.7, the client certificate of the BigFix Agent will have a validity period of 13 months.
- Client Authentication
  Client Authentication (introduced in version 9) extends the security model used by BigFix to encompass trusted client reports and private messages.
- Maintenance and Troubleshooting
  If you are subscribed to the Patches for Windows site, you can ensure that you have the latest upgrades and patches to your SQL server database servers.

Enabling FillDB parallel processing

On the BigFix Server, the FillDB process is responsible to run in a single thread the following activities.

Read the buffer directory content.
Parse the report, which includes:
- Decrypting the encrypted reports.
- Decompressing the compressed reports.
Store the report data in the database.
Replicate content from other DSA servers (optional).

An additional thread is responsible for performing the same type of processing for the reports returned by the BigFix Query processing.

Starting from V9.5 Patch 5, the parallel processing is enabled by default during a fresh installation and upgrade according to the following rules:

If the machine has 6 to 9 cores, the parallelism is enabled for normal reports by configuring 3 parsing threads and 3 database update threads.
If the machine has at least 10 cores, the parallelism is enabled both for normal and for query reports by configuring for each of them 3 parsing threads and 3 database update threads for a total of 12 threads.

You can manually enable or disable the FillDB parallel processing by configuring the following settings on the BigFix Server:

ParallelismEnabled
ParallelismEnabledForQuery

Once you enabled the FillDB parallel processing, you can configure its behavior by specifying the following settings on the BigFix Server:

NumberOfParsingThreads
NumberOfDBUpdatingThreads
MaxNumberOfReportsReadyForDB
MinNumberOfReportsReadyForDB
MaxNumberOfReportsInParsingQueue
NumberOfParsingThreadsForQuery
NumberOfDBUpdatingThreadsForQuery
MaxNumberOfQueryReportsReadyForDB
MinNumberOfQueryReportsReadyForDB
MaxNumberOfQueryReportsInParsingQueue

For more information about these settings, see Configuring parallel FillDB.

Run the following steps to activate changes on one or more of the settings specified above:

If the BigFix Server is installed on a Windows system:

Stop the BES FillDB service.
Update the values of the settings as appropriate in the Windows registry.
Start the BES FillDB service

If the BigFix Server is installed on a Linux system:

Stop besfilldb, for example /etc/init.d/besfilldb stop
Stop besserver, for example /etc/init.d/besserver stop
Update the values of the settings as appropriate in the besserver.config file.
Start besserver, for example /etc/init.d/besserver start
Start besfilldb, for example /etc/init.d/besfilldb start