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.
Managing Downloads
BigFix uses several methods to ensure that downloads are efficient and make the best use of available bandwidth.
Dynamic download White-lists
Dynamic downloading extends the flexibility of action scripts, adding the ability to use relevance clauses to specify URLs.

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.
- Using multiple servers (DSA)
  Here are some of the 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
  You can gather license updates and external sites by using the HTTP or HTTPS protocol on a BigFix server or in an airgapped environment.
- Configuring secure communication
- Real Time AV Exclusions
  BigFix Console, Server and Relay components of the architecture perform high volume file operations.
- 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.
- Persistent connections
  Starting from Patch 11, the capability to establish persistent connections was added to the product.
- Relays in DMZ
  Starting from Patch 13, 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 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.
  - 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.
  - 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.
  - 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.
  - Managing Downloads
    BigFix uses several methods to ensure that downloads are efficient and make the best use of available bandwidth.
    - Enabling data pre-cache
      You can specify for each Client if the data to download to run an action must be pre-cached on the Client or not and how.
    - Dynamic download White-lists
      Dynamic downloading extends the flexibility of action scripts, adding the ability to use relevance clauses to specify URLs.
  - Creating custom client dashboards
    You can create custom Client Dashboards, similar to those in the console.
  - 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. You can create a location property in BigFix using the Location Property Wizard.
  - Locking clients
    You can change the locked status of any BigFix client in the network.
  - Editing the Masthead on Windows systems
    You can change the 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.
  - 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
  - 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
  Starting with BigFix version 9.5.11, the server audit logs include the following items:
- List of advanced options
  The following lists show the advanced options that you can specify in the Advanced Options tab of the BigFix Administrative tool on Windows systems, or in the BESAdmin.sh command on Linux systems using the following syntax:
- Security Configuration Scenarios
  BigFix provides the capability to follow the NIST security standards by configuring an enhanced security option.
- Client Authentication
  Client Authentication 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.

Dynamic download White-lists

Dynamic downloading extends the flexibility of action scripts, adding the ability to use relevance clauses to specify URLs.

As with static downloads, dynamic downloads must specify files with the confirmation of a size or sha1. However, the URL, size, and sha1 are allowed to come from a source outside of the action script. This outside source might be a manifest containing a changing list of new downloads. This technique makes it easy to access files that change quickly or on a schedule, such as antivirus or security monitors.

This flexibility entails extra scrutiny. Because any client can use dynamic downloading to request a file, it creates an opportunity for people to use your server to host files indiscriminately. To prevent this, dynamic downloading uses a white-list. Any request to download from a URL (that is not explicitly authorized by use of a literal URL in the action script) must meet one of the criteria specified in a white-list of URLs that is contained in the following file:

On Windows systems:: <Server Install Path>\Mirror Server\Config\DownloadWhitelist.txt
On Linux systems:: <Server Install Path>/Mirror Server/config/DownloadWhitelist.txt

This file contains a newline-separated list of regular expressions using a Perl regex format, such as the following:

http://.*\.site-a\.com/.*
http://software\.site-b\.com/.*
http://download\.site-c\.com/patches/JustThisOneFile\.qfx

The first line is the least restrictive, allowing any file at the entire site-a domain to be downloaded. The second line requires a specific domain host and the third is the most restrictive, limiting the URL to a single file named "JustThisOneFile.qfx". If a requested URL fails to match an entry in the white-list, the download immediately fails with status NotAvailable. A note is made in the relay log containing the URL that failed to pass. An empty or non-existent white-list causes all dynamic downloads to fail. A white-list entry of ".*" (dot star) allows any URL to be downloaded.