Home
Installation Guide
Learn the system requirements, licensing and installation instructions, and how to configure and maintain BigFix.
Installing the clients
Install the BigFix client on every computer in your network that you want to administer, including the computer that is running the console.
Installing the Client on Linux
The BigFix client can always be installed by manually running the client installer on each computer.
Oracle Linux Installation Instructions
How to install the client on Oracle Linux.

Installation Guide
Learn the system requirements, licensing and installation instructions, and how to configure and maintain BigFix.
- Introduction
  BigFix aims to solve the increasingly complex problem of keeping your critical systems updated, compatible, and free of security issues. It uses patented Fixlet technology to identify vulnerable computers in your enterprise. With just a few mouse-clicks you can remediate them across your entire network from a central console.
- BigFix Platform Unicode Support Overview
  BigFix Platform V10 gathers data from BigFix clients deployed with different code pages and languages, encode the data into UTF-8 format, and report it back to the BigFix server.
- Sample deployment scenarios
  The following deployment scenarios illustrate some basic configurations taken from actual case studies.
- Requirements and assumptions
  BigFix runs efficiently using minimal server, network, and client resources.
- Types of installation
  Before you install the product, decide if you want to do an evaluation or production installation.
- Managing licenses
  You must obtain a license key before you can install and use BigFix.
- Before installing
  Before running the installation make sure that you read the following topics and run the requested activities if needed.
- Installing on Windows systems
  Now that you understand the terms and the administrative roles, you are ready to get authorized and install the programs.
- Installing on Linux systems
  After understanding the terms and the administrative roles, you are ready to actually get authorized and install the programs.
- Installing the clients
  Install the BigFix client on every computer in your network that you want to administer, including the computer that is running the console.
  - Using the Client Deploy Tool
    You can use the Client Deploy Tool (CDT) to install Windows, UNIX and Mac target computers.
  - Installing the Client on AIX
    How to install the client on AIX.
  - Installing the Client on Linux
    The BigFix client can always be installed by manually running the client installer on each computer.
    - Amazon Linux 2 Installation Instructions
      How to install the client on Amazon Linux 2.
    - CentOS Installation Instructions
      How to install the client on CentOS.
    - Oracle Linux Installation Instructions
      How to install the client on Oracle Linux.
    - Raspbian Installation Instructions
      How to install the client on Raspbian.
    - Red Hat Installation Instructions
      How to install the client on Red Hat.
    - Rocky Linux Installation Instructions
      How to install the client on Rocky Linux.
    - SUSE Linux Enterprise (64-bit) Installation Instructions
      How to install the client on SUSE Linux Enterprise (64-bit).
    - Ubuntu/Debian (64-bit) Installation Instructions
      How to install the client on Ubuntu/Debian (64-bit).
  - Installing the Client on Mac
    How to install the Mac client.
  - Installing the Client on Solaris 11
    As a prerequisite, all Solaris agents must have the SUNWlibC package installed.
  - Installing the Client on Windows
    You can install the BigFix client manually by running the Client installer on each computer.
  - Embedding in a Common Build
    If your organization employs a specific build image or common operating environment (COE) on a CD or image that is used to prepare new computers, you can include the Client in this build.
  - Avoiding duplicates when a Client is restored
    When the BigFix client is rolled back or restored from a snapshot, the next time it registers itself with the BigFix server, it receives a new Computer ID. The BigFix client with the old Computer ID becomes inactive because it does not report with the same Computer ID. As a result, the BigFix console shows duplicated entries for the same computer. Additionally, the affected computer loses all information: action history, discovery, and so on.
  - Enabling encryption on Clients
    When installed, you can set up your Clients to encrypt all outgoing reports to protect data such as credit card numbers, passwords, and other sensitive information.
- Post-installation configuration steps
  After having run the installation, make sure that you read the following topics and run the requested activities if needed.
- Managing relays
  Relays can significantly improve the performance of your installation.
- Introduction to Tiny Core Linux - BigFix Virtual Relay
  Follow the step-by-step sequence of operations needed to build the virtual machine, from the downloading of the ISO image to the complete setup and configuration of the BigFix Virtual Relay.
- Setting up a proxy connection
  If your enterprise uses a proxy to access the Internet, your BigFix environment can use that communication path to gather content from sites.
- Running backup and restore
  You can schedule periodic backups (typically nightly) of the BigFix server and database files, to reduce the risk of losing productivity or data when a problem occurs by restoring the latest backup.
- Upgrading on Windows systems
  Before you begin
- Upgrading on Linux systems
  Before you begin
- SQL Server parallelism optimization
  The performance of an SQL Server database instance can often be improved by small tweaks. Performance might also be hindered by simple oversights. In fact, some SQL Server parallelism settings have suboptimal default values. Moreover, they have to be re-tuned after an hardware upgrade. Other issues might arise from inadvertent hardware configurations, especially when SQL Server is hosted on a virtual machine (VM).
- Known limitations and workarounds
  This section describes the known limitations and possible workarounds.
- Logging
  This section describes the log files associated with the BigFix components.
- Uninstalling the BigFix client
  To uninstall the BigFix client installed on the various operating systems, see the following sections.

Oracle Linux Installation Instructions

How to install the client on Oracle Linux.

Before installing the client on Oracle Enterprise Linux 9, ensure that you have installed the initscripts package.

To install the client perform the following steps:

Download the corresponding BigFix client RPM file to the Oracle Linux computer.
Install the RPM by running the command
```
rpm -ivh client_RPM_path 
```
Copy your actionsite masthead to the client computer (the masthead contains configuration, license, and security information). The action site masthead (actionsite.afxm) can be found in your BES Installation folders (by default they are placed under C:\Program Files (x86)\BigFix Enterprise\BES Installers\Client on Windows and /var/opt/BESInstallers/Client/ on Linux). If the masthead is not named actionsite.afxm, rename it to actionsite.afxm and place it on the computer at the following location: /etc/opt/BESClient/actionsite.afxm.
Note: The directory /etc/opt/BESClient/ is not automatically created by the installer. If it does not exist, create it manually.
The masthead file for each BigFix server is downloadable at http://servername:port/masthead/masthead.afxm (example: http://bes.BigFix.com:52311/masthead/masthead.afxm).
Start the BigFix client by running the command:
```
/etc/init.d/besclient start
```

Note:

The BigFix client installation on Oracle Linux operating system can be performed also on computers having SELinux enabled. With SELinux enabled, the following SELinux settings are supported:

selinux = enforcing, policy = targeted.

Note: On Oracle Enterprise Linux 9, the user interface component of the client is displayed only if you log in choosing GNOME on Xorg.

Signed RPM packages

The RPM packages are signed with a PGP key. For more details, see Red Hat Installation Instructions.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.