Home
Configuration Guide
Learn how to configure BigFix according to your needs.
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.
Archive Manager
Archive Manager is a component of the BigFix Client that can collect files periodically or on command. It passes the resultant compressed tar-ball to the Upload Manager on the BigFix Client.
Archive Manager Server Index File Format
When the BigFix Server receives files from the Archive Manager, it creates a server index containing metadata about all files present on the Server.

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 or Microsoft Entra ID
  You can add Identity Providers associations to BigFix.
- Enabling SAML V2.0 authentication for identity provider operators
  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, BigFixVersion 11 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 Modern Client Management.
- Extending BigFix management capabilities
  BigFix 11 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.
  - Archive manager settings
    A typical archive is a collection of logs and configuration files that are compiled regularly and posted to the server. There are many settings available to help you customize your logging needs.
  - Creating a Custom Action
    You can create custom actions that can post attributes about the BigFix client to an archive file.
  - Archive Manager
    Archive Manager is a component of the BigFix Client that can collect files periodically or on command. It passes the resultant compressed tar-ball to the Upload Manager on the BigFix Client.
    - Archive Manager internal variables
      These are the internal variables of the Archive Manager component.
    - Archive Manager Index File Format
      During the building of the archive, the Archive Manager creates an index containing metadata about the archive.
    - Archive Manager Server Index File Format
      When the BigFix Server receives files from the Archive Manager, it creates a server index containing metadata about all files present on the Server.
  - Upload Manager
    The Upload Manager coordinates the sending of files in chunks to the Post File program. You can throttle the upload dataflow to conserve bandwidth. The file system uses 64-bits, sufficient for file sizes of up to 2⁶⁴ – 1 bytes in length.
  - PostFile
    The PostFile program receives the chunks of files posted by the Upload Manager and appends them to its own copy of the file. The Upload Manager specifies the range of bytes being posted and the sha1 of the file, which is used as the filename. For details about the configuration settings related to this component, see Post File in Platform/Config/c_config_stngs_overview.html#c_overview.
  - Resource Examples
    Some concrete examples.
- 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
  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
  Starting from Version 11, BigFix provides the capability to configure several security options.
- 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.

Archive Manager Server Index File Format

When the BigFix Server receives files from the Archive Manager, it creates a server index containing metadata about all files present on the Server.

The server index file is created when you have enabled one or more settings named _BESClient_ArchiveManager_KeepFileSet-<tag> on the BigFix client.

This is a sample index from an archive with a single file:

MIME-Version: 1.0 
Content-Type: multipart/x-directory2; boundary="===" 
Unique-ID: 1077307147 
Archive-Size: 105 
SendAll: 0 
Date: Wed, 17 Mar 2004 02:23:01 +0000 
FileSet-(LOG): c:\temp\log\newfile.log
KeepFileSet-(LOG): 1

--=== 
URL: file:///c:/temp/log/newfile.log
UTF8URL: file:///c:/temp/log/newfile.log
NAME: (LOG)newfile.log 
UTF8NAME: %28LOG%29newfile.log
SIZE: 105 
TYPE: FILE 
HASH: 3a2952e0db8b1e31683f801c6384943aae7fb273 
MODIFIED: Sun, 14 Mar 2004 18:32:58 +0000 

--===--