Learn what's new in BigFix Scanner.

The list and description of fixlets and tasks available in the BigFix console on the BigFix Scanner site.

BigFix Scanner Service—Preview Feature

Scanner Information and Scanner Trace Settings analysis have been updated with additional information.

The topic lists the naming conventions followed in BigFix Scanner.

The tables in this section provide detailed information about the system requirements for BigFix Scanner.

The scanner collects hardware information as well as information about files, ISO Tags and other on the computers in your infrastructure.

You can upgrade BigFix Scanner on an operating system that is supported. BigFix Scanner version 11.0.38.1 includes security fixes, issues addressed, and new features.

Creating Scanner Wrapper for Scanner.

This section describes the methods to whitelist scanner services in File Access Policy Daemon.

This task allows for configuring the File System Scan Cache. The task is relevant only on computers where the scanner is installed.

The scanner cache folder is used to store information about scanned files and directories in your file system. The scanner locates the cache folder using the file hierarchy which results in quick scans. The amount of disk space that is needed for the cache depends on the number of files that are being scanned. If the current cache folder does not have sufficient disk space, you can change the location of the cache folder or optimize the cache.

The File System Monitoring Cache (FSMon) is a mechanism designed to optimize the performance of file system monitoring operations. It acts as an intermediary storage layer that temporarily holds metadata and state information about the monitored file system. This reduces the need for frequent direct access to the file system, thereby improving efficiency and reducing system overhead.

Excluding some directories from scanning is useful if the directories are large and contain no information that is important to the software inventory. By excluding them, you can speed up the scanning process. Some directories are excluded from software scans by default. They must remain excluded to ensure accuracy of data. You can add or remove other directories from the list by using tasks in the BigFix console. You can also manually add them to the scanner files on particular endpoints.

This task allows you to set the BigFix Scanner Wscan CPU Threshold. With this setting, you can limit the CPU utilization of the Wscan.

A dedicated mechanism to prevent exhausting whole disk space.

If requested by HCL® support to limit the amount of traces generated by the scanner tool, you can change the scanner trace settings.

If you are asked by BigFix Support to provide data for troubleshooting problems with computers in your infrastructure, go to the details of the computer. Open the Computer Support Data panel, download the log package, and provide it to BigFix Support. The package contains log files that are needed for troubleshooting purposes such as BigFix client logs.

Checks the relevance expressions of a particular Fixlet or task on endpoints.

BigFix Scanner Service gathers detailed System Information from endpoints.

BigFix Scanner Service gathers detailed Application Data from endpoints.

BigFix Scanner Service gathers File System Information from endpoints.

CPU Throttling in BigFix Scanner Service is managed through the CPUHandler component.

This topic provides information on the different modes of configuration available in BigFix Scanner Service.

The topic provides information on settings that control the behavior of the BigFix Scanner Service, including scan frequency, data collection, resource usage, and reporting. These options allow customization to align with system performance and compliance requirements.

The information collected by BigFix Scanner Service is available through the SQLite database and can be accessed using the sqlite database inspector.

This topic lists the APIs available in BigFix Scanner Service. It is recommended to use the documented view to access the API data.

By default, the BigFix Scanner Service gathers the log at <BESClient dir>\tools\scanner\logs\ under the bf-scanner.log file.