Welcome
Configuration Guide
Learn how to configure BigFix according to your needs.
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.
Managing cloud resources
The IT ecosystem in every organization keeps expanding to include a variety of endpoints such as servers, Mac and Linux desktops, and laptops. With the advent of cloud computing, more and more IT organizations consider shifting their entire on-premise infrastructure including data centers to the cloud, such as Amazon Web Services, Microsoft Azure, VMware, and Google Cloud Platform (GCP). Consequently, managing endpoints is becoming increasingly complex, which has necessitated endpoint management solutions to also support cross-hosting environments.
Managing cloud plugins
BigFix Platform includes a plugin for every cloud provider supported, namely Amazon Web Services (AWS), Microsoft Azure, VMware and Google Cloud Platform (GCP). Each of these cloud providers has its own uniqueness, capabilities, and ways to interface with an external program and they handle access to data and capabilities differently.
Verifying the cloud plugin installation
Once the deployment of a cloud plugin has completed, its first discovery attempt is expected to start immediately and the discovered resources should be displayed in the Computers view of the BigFix Console or in the Devices page of the BigFix WebUI within a few minutes.

BigFix Documentation Homepage
BigFix 11 Platform Documentation
Welcome to the BigFix Platform documentation, where you can find information about how to install, maintain, and use BigFix.
Detailed system requirements
The content of this page has moved to the HCL Support site. You will be redirected shortly. If the auto-redirect fails for some reason, use this link: https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0104120.
Platform guides in PDF format
Following is a list of links to the BigFix Platform user guides in PDF format:
Common Criteria Certification
BigFix 10.0.1.41 complies with the requirements of the standard ISO/IEC 15408 (Common Criteria) v. 3.1 for the assurance level: EAL2
Getting Started
Use this section to become familiar with BigFix infrastructure and key concepts necessary to understand how it works.
HTTPS across BigFix applications
This topic describes how the SSL/HTTPS communication works in BigFix applications and links the tasks on how to configure it.
Installation Guide
Learn the system requirements, licensing and installation instructions, and how to configure and maintain BigFix.
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 and BigFix Mobile.
- 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.
  - Managing cloud resources
    The IT ecosystem in every organization keeps expanding to include a variety of endpoints such as servers, Mac and Linux desktops, and laptops. With the advent of cloud computing, more and more IT organizations consider shifting their entire on-premise infrastructure including data centers to the cloud, such as Amazon Web Services, Microsoft Azure, VMware, and Google Cloud Platform (GCP). Consequently, managing endpoints is becoming increasingly complex, which has necessitated endpoint management solutions to also support cross-hosting environments.
    - Understanding cloud setup
      BigFix Console and WebUI provide operators with a single representation of a cloud resource, regardless of whether it is managed by the BigFix Agent, by the Platform/Config/c_pluginportal.html through the cloud plugins, or by both. This way, you as an operator can have complete visibility into and control over your cloud infrastructure.
    - Discovering cloud resources
      BigFix 11 provides the capability to discover resources that you own on any of the supported cloud providers.
    - Correlated devices
      BigFix 11 has the capability of correlating multiple representations of the same computer, allowing operators to manage them as a single entity (also referred to as correlated device throughout this documentation) as well as to operate on a specific representation as needed.
    - Introduction to Cloud Plugins
      Starting from Version 10, BigFix provides a set of Cloud Plugins that can be attached to a Plugin Portal, in order to manage the Cloud environments of Amazon Web Services, Microsoft Azure, Google Cloud Platform and VMware. Each plugin has a set of similar capabilities but each of them differs in the support of some features, due to the nature of the correspondent Cloud Provider.
    - Managing cloud plugins
      BigFix Platform includes a plugin for every cloud provider supported, namely Amazon Web Services (AWS), Microsoft Azure, VMware and Google Cloud Platform (GCP). Each of these cloud providers has its own uniqueness, capabilities, and ways to interface with an external program and they handle access to data and capabilities differently.
      - Planning the installation of cloud plugins
        Cloud plugins can be installed on computers running the Plugin Portal. Optionally, they may all be installed on the same Plugin Portal instance.
      - Installing cloud plugins
        Each cloud plugin has a specific installation task on BES Support, which becomes relevant on computers where the Platform/Config/c_pluginportal.html is installed.
      - Verifying the cloud plugin installation
        Once the deployment of a cloud plugin has completed, its first discovery attempt is expected to start immediately and the discovered resources should be displayed in the Computers view of the BigFix Console or in the Devices page of the BigFix WebUI within a few minutes.
      - Configuring cloud plugins
        Cloud plugins are installed with a base configuration that can be updated later on, primarily through the BigFix WebUI.
    - Cloud Plugins Inspectors
      Resources reported by the cloud plugins contain a lot of information related to the instances they represent. Such data is made available through numerous inspectors.
    - Cloud plugins Commands
    - Activating cloud analyses
      When a cloud plugin is installed, the following BES Support analyses must be activated to take advantage of the new cloud-related capabilities of BigFix.
    - Working with the cloud plugin dashboard
      The information displayed by the Cloud Plugin Dashboard.
    - BigFix Agent installation on cloud resources
      Starting from BigFix Version 10 Patch 2, you can install the BigFix Agent on the discovered cloud resources (AWS and Azure), using the cloud provider services through the corresponding BigFix cloud plugin.
    - Troubleshooting
      This section helps you troubleshoot some common issues or limitations.
- 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.
- 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.
- Migrating the BigFix Server from Windows to Red Hat 9 with SQL Server
  Starting from BigFix Version 11.0.1, you can migrate BigFix Platform from a Windows operating system to a Red Hat 9 operating system with Microsoft SQL Server 2022 Database, both using a local or a remote database.
- 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.
- Enabling Microsoft Control Flow Guard on BigFix Server
  Starting from BigFix version 11.0.3, the BigFix Server implements the Microsoft Control Flow Guard (CFG) security feature on Windows systems; the BigFix Server executables:
- 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.
Console Operator's Guide
Learn how to work with the BigFix Console.
Asset Discovery User's Guide
Learn how BigFix Asset Discovery works.
Web Reports Guide
Learn how the Web Reports feature extends the power of BigFix.
BigFix Explorer Guide
Learn how the BigFix Explorer feature extends the power of BigFix.
WebUI User's Guide
Read this guide for an introduction to the WebUI tools, concepts, and terminology.
WebUI Administration Guide
Read this guide for information about installing and administering the WebUI.
Glossary
This glossary provides terms and definitions for the Modern Client Management for BigFix software and products.

Verifying the cloud plugin installation

Once the deployment of a cloud plugin has completed, its first discovery attempt is expected to start immediately and the discovered resources should be displayed in the Computers view of the BigFix Console or in the Devices page of the BigFix WebUI within a few minutes.

Procedure

As a post-installation sanity check, you can verify the following:

The existence of the cloud plugin log file in the following default path:
- Windows: C:\Program Files (x86)\BigFix Enterprise\BES Plugin Portal\Plugins\Plugin_name\Logs\log.txt
- Linux: /var/opt/BESPluginPortal/Plugins/Plugin_name/Logs/log.txt

The content of the cloud plugin log file which for a functioning plugin just installed will be such as:

2020/03/31 19:33:48 - [info] <Plugin_name> 1.1.59 starts on <OS platform>
2020/03/31 19:33:48 - [info] Plugin Portal with API version 1
2020/03/31 19:33:55 - [info] Refresh all: Attempting discovery
2020/03/31 19:35:53 - [info] Refresh all: Discovery returned <number> unique devices

The running status of the BESPluginPortal process.
The content of the plugin portal log file, located in the following default path:
- Windows: C:\Program Files (x86)\BigFix Enterprise\BES Plugin Portal\BESPluginPortal.log
- Linux: /var/log/BESPluginPortal.log
After the latest plugin portal restart, the log file should contain a line such as:
```
Tue, 31 Mar 2020 19:33:49 +0200 - 1222616832 - Running plugin'<Plugin_name>'
```
Note: The presence of the following message in the plugin portal log file is expected as long as no discovered resources exist:
```
Tue, 31 Mar 2020 19:33:49 +0200 - 2383846272 - Error reading records from the database.
```

Results

In case of unexpected results, refer to the Troubleshooting section.