Home
Configuration Guide
Learn how to configure BigFix according to your needs.
Integrating with LDAP
You can add Lightweight Directory Access Protocol (LDAP) associations to BigFix.
Integrating with Active Directory
You can use Microsoft Active Directory (AD) to handle authentication on BigFix.
Integrating the Linux server with Active Directory
Configuring Kerberos authentication
To ensure a secure communication between Linux BigFix server and Active Directory, use the Kerberos protocol.
Modifying the local LDAP name
To modify the local LDAP name, perform the following steps:

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.
  - Integrating with a Generic LDAP
    Configure the integration with a Generic LDAP by adding an existing LDAP domain to the console as follows:
  - Integrating with Active Directory
    You can use Microsoft Active Directory (AD) to handle authentication on BigFix.
    - Integrating the Windows server with Active Directory
      To add an existing Active Directory to the console, follow these steps:
    - Integrating the Linux server with Active Directory
      - Configuring Kerberos authentication
        To ensure a secure communication between Linux BigFix server and Active Directory, use the Kerberos protocol.
        Preliminary Checks
        Before running the integration between the BigFix server running on a Red Hat Enterprise Linux 6 or Linux 7 system and the Active Directory server, ensure that:
        Installing the NSS and PAM libraries
        Ensure that the following NSS and PAM packages are installed:
        Configuring Authentication
        To configure the Kerberos protocol, the LDAP security and the authentication files for Active Directory integration, you can use one of the following methods:
        Modifying the local LDAP name
        To modify the local LDAP name, perform the following steps:
        Configuring the NSS and PAM libraries
        To use the LDAP database to authenticate users on a Linux system edit the /etc/nsswitch.conf and change passwd, shadow and group entries from the SSSD daemon (sss) to LDAP:
      - Integrating the server with Active Directory
  - Adding LDAP Operators
    You can create accounts for operators to access the console by using an existing Active Directory or LDAP account.
  - Associating an LDAP group
    You can associate LDAP users or groups, that have been defined in an existing Active Directory or LDAP directory, to console operators or roles.
- 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.
- 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.

Modifying the local LDAP name

To modify the local LDAP name, perform the following steps:

Make a backup copy of the LDAP configuration file as follows:
```
cp -p /etc/nslcd.conf /etc/nslcd.conf.bk
```
Modify the value of the base and uri settings in the /etc/nslcd.conf file as in the following example:
```
base dc=tem,dc=test,dc=com
uri ldap://winserver.tem.test.com
```
Restart the local LDAP name service daemon:
```
service nslcd restart
```
Ensure that the local LDAP name service daemon (nslcd) is set to start with the server:
```
 chkconfig nslcd on
```