Welcome
Installation Guide
Learn the system requirements, licensing and installation instructions, and how to configure and maintain BigFix.
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.
Reading and writing files in the specific encodings
BigFix agent uses UTF-8 as the internal representation of strings.
Background information
When files are written, by default, the BigFix agent assumes that the encoding is the local one.

BigFix Documentation Homepage
BigFix 10 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=KB0087327.
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.
- 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.
  - Masthead encoding parameters
    The masthead file has been modified to contain the following two new parameters:
  - Top-down data flow: from the BigFix server to the clients
    The encoding capability when sending data from the BigFix server to BigFix clients is the same as BigFix V9.2; UTF-8 support of the top-down data flow is not available in BigFix. The top-down data flow (such as actions, site subscriptions, computer groups, custom sites, and more) works only if you use non-ASCII data that belongs to the FXF encoding.
  - Bottom-up data flow: from BigFix clients to BigFix server
    BigFix Platform V10 uses UTF-8 as the standard encoding system to send reports from BigFix clients to BigFix server. The x-bes-report-charset parameter is set to utf-8 in the masthead and its value cannot be changed.
  - Unicode support requirements and limitations
    This is a list of BigFix Platform V10 requirements and limitations when using non-ASCII characters:
  - Reading and writing files in the specific encodings
    BigFix agent uses UTF-8 as the internal representation of strings.
    - Background information
      When files are written, by default, the BigFix agent assumes that the encoding is the local one.
    - Reading file inspectors
      You can use the inspector object encoding to specify an encoding to be used to read file in a relevance expression.
    - Writing file with the encode command
      You can use the Action Script command action uses file encoding to specify the encoding in which to write files when using the appendfile and createfile until commands.
    - Reading and writing files with encode
      Using the encode inspectors, you can also read from and write to files, having different encoding.
  - Managing actions on clients with different local encoding
    BigFix Platform introduces the possibility to specify the names of files and folders of UNIX clients in any encoding, even if it is different from the encoding used by 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.
- BigFix Administration Tool
  The BigFix Administration Tool, also called BESAdmin, is the tool we use to perform configuration changes and maintenance operations.
- 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
  The steps to upgrade the BigFix Platform.
- 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.
Configuration Guide
Learn how to configure BigFix according to your needs.
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.
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.

Background information

When files are written, by default, the BigFix agent assumes that the encoding is the local one.

On a client with local encoding different from UTF-8 (like Windows), text data is transcoded from UTF-8 to the local encoding. Using the encode inspector you can now specify what encoding must be used to read and write files.

When files are read, if the Byte Order Mark (BOM) is set, file encoding is determined based on the BOM. Otherwise, the content of file is assumed to be in the local encoding.

Note: Inspectors and the Action Script language no longer handle binary file contents, because file is transcoded to or from UTF-8.