Home
Configuring
After you install BigFix Inventory, configure the application. Create accounts for the users who need access to the application and set up scans to collect software and hardware inventory data from your environment.
Setting up scans to discover software and hardware inventory
The scanner is an independent, well-defined component that is used by BigFix Inventory. It is installed and managed through the BigFix client, and it enables the software and capacity scans. Software and capacity scans collect data that is later on displayed on the BigFix Inventory reports. For environments with up to a few thousand computers, you can enable the default scan configuration. In this case, the analyses are activated and software and capacity scans as well as uploads of their results are scheduled automatically on the computers that are subscribed to the BigFix Inventory site. For larger environments, it is advisable to divide the computers into groups and manually configure a separate scan schedule for each group to avoid performance issues.
Advanced scan configuration
After you successfully schedule software and capacity scans and the scan data is displayed on the BigFix Inventory reports, you can further customize the scans. For example, you can exclude directories from software scans or scan remote shared file systems.
Discovering software and hardware with disconnected scanner on Windows and UNIX
Available from 9.2.7. You can discover software and hardware inventory by using disconnected scans that do not require direct connection between the scanned computers and the BigFix server. Scripts that are provided in the disconnected scanner package initiate software and capacity scans, and prepare scan results that you later on upload to BigFix Inventory.
Disconnected scanner maintenance and troubleshooting
Available from 9.2.7. You can use the maintenance and troubleshooting tasks to monitor the scan progress, optimize the processor usage during the scan, understand and fix the most common issues, or learn more about the log files.
Understanding the Deployment Health and Software Scan Health
Available from 9.2.7. Deployment Health and Software Scan Health contain information about your clients and the scans that were initiated. You can view this information on the Deployment Health, and Software Scan Health widgets on the dashboard, or on the Computers report. Deployment Health excludes all the disconnected datasource endpoints. To properly understand values that are displayed for systems scanned with disconnected scans, see the explanation of particular columns on the Computers report.

Configuring
After you install BigFix Inventory, configure the application. Create accounts for the users who need access to the application and set up scans to collect software and hardware inventory data from your environment.
- Creating users and groups
  Each user who has access to BigFix Inventory must be assigned a role and a computer group. The role defines which reports and panels the user can view. The computer group narrows down the scope of these reports and panels to computers that meet certain criteria.
- Setting up scans to discover software and hardware inventory
  The scanner is an independent, well-defined component that is used by BigFix Inventory. It is installed and managed through the BigFix client, and it enables the software and capacity scans. Software and capacity scans collect data that is later on displayed on the BigFix Inventory reports. For environments with up to a few thousand computers, you can enable the default scan configuration. In this case, the analyses are activated and software and capacity scans as well as uploads of their results are scheduled automatically on the computers that are subscribed to the BigFix Inventory site. For larger environments, it is advisable to divide the computers into groups and manually configure a separate scan schedule for each group to avoid performance issues.
  - Frequency of scans and uploads of data
    By default, software and capacity scans are scheduled with a frequency that meets auditing requirements. If you want to change the default frequency, ensure that the new setup fulfills the minimal requirements and all considerations.
  - Default scan configuration
    Default scan configuration is advised for environments with up to a few thousand computers. It ensures that the required analyses are activated and software and capacity scans as well as uploads of their results are scheduled automatically. These actions are necessary to collect data from the computers in your infrastructure and to display it on the BigFix Inventory reports. You can enable the default scan configuration during the configuration of BigFix Inventory connections to the databases or when adding another data source.
  - Manual scan configuration
    Manual scan configuration is advised for environments with more than a few thousand computers. It requires that analyses are activated and software and capacity scans as well as uploads of their results are scheduled manually after the installation. These actions are necessary to collect data from the computers in your infrastructure and display in on the BigFix Inventory reports. Flexibility of the manual scan configuration allows for avoiding performance issues that might occur when you scan too many computers at the same time.
  - Advanced scan configuration
    After you successfully schedule software and capacity scans and the scan data is displayed on the BigFix Inventory reports, you can further customize the scans. For example, you can exclude directories from software scans or scan remote shared file systems.
    - Detailed hardware scan
      Available from 9.2.12. Detailed hardware scan collects hardware information related to memory, operating systems, storage, processors, partitions, network adapters, SMBIOS data, IP addresses and logical partition capacity data. The solution is supported on Windows, Linux x86-64 and x86-32, and AIX. It can be run also on other operating systems but the results might not be accurate.
    - Discovering software on shared disks
      BigFix Inventory allows you to scan the shared disk on designed endpoint and use the information across all of endpoints. The solution is fully-automated.
    - Discovering software in Docker containers
      Available from 9.2.5. Docker and Podman are platforms that allow automating the deployment of applications inside software containers. BigFix Inventory BigFix Inventory discovers software that is installed inside Docker containers. It also measures license metric utilization of the discovered BigFix products.
    - Excluding directories from being scanned
      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.
    - Discovering software and hardware with disconnected scanner on Windows and UNIX
      Available from 9.2.7. You can discover software and hardware inventory by using disconnected scans that do not require direct connection between the scanned computers and the BigFix server. Scripts that are provided in the disconnected scanner package initiate software and capacity scans, and prepare scan results that you later on upload to BigFix Inventory.
      - Disconnected scanner requirements
        Available from 9.2.7. The list of disk space requirements, and the supported operating systems compatible with the disconnected scanner.
      - Adding a new data source for disconnected scans
        Available from 9.2.7. All scan results are imported to BigFix Inventory from a directory dedicated to disconnected scans. Add this directory as a data source to allow BigFix Inventory to check its content and import all packages that are stored within. The packages are imported during each data import.
      - Preparing installation files for disconnected scans
        Available from 9.2.7. After you add the disconnected data source, prepare the installation package and distribute it to the disconnected systems. The package should contain the scanner, software catalog and the configuration files that are used to initiate scans. You can download the catalog from the BigFix Inventory server.
      - Installing the scanner and gathering initial data
        Available from 9.2.7. After you copied the installation files and the software catalog to the endpoints, start the installation and the initial scans.
      - Running software scans and gathering scan results
        Available from 9.2.7. The script that is responsible for the software scan collects the results of the catalog-based, package data, and ISO tags scan, as well as retrieves results of the capacity scan and the computer.yml file. All these results are combined and compressed into a common .zip or tag.gz package that can be imported to BigFix Inventory.
      - Importing scan results to BigFix Inventory
        Available from 9.2.7. To import new scan results to BigFix Inventory, copy the package to the disconnected scans directory that you added as a data source.
      - Disconnected scanner maintenance and troubleshooting
        Available from 9.2.7. You can use the maintenance and troubleshooting tasks to monitor the scan progress, optimize the processor usage during the scan, understand and fix the most common issues, or learn more about the log files.
        Updating the scanner and the scripts
        Available from 9.2.7. Both the scanner and the scripts are updated on a regular basis to introduce improvements and new functions. To update the scanner, once again download all the required files, and copy them into the directory where the previous version is already located.
        Decommissioning computers with disconnected scanners
        Available from 9.2.7. When you decommission a computer that is no longer in use, you can mark it as decommissioned on the Computers report, so that it is not displayed in BigFix Inventory.
        Uninstalling the disconnected scanner
        Available from 9.2.7. If you no longer need the disconnected scanner to scan the computer, you can uninstall it from any endpoint.
        Understanding the Deployment Health and Software Scan Health
        Available from 9.2.7. Deployment Health and Software Scan Health contain information about your clients and the scans that were initiated. You can view this information on the Deployment Health, and Software Scan Health widgets on the dashboard, or on the Computers report. Deployment Health excludes all the disconnected datasource endpoints. To properly understand values that are displayed for systems scanned with disconnected scans, see the explanation of particular columns on the Computers report.
        Troubleshooting the discovery by disconnected scanner
        Available from 9.2.7. The troubleshooting section lists the most common issues you might encounter while discovering software and hardware inventory with the disconnected scanner. The main objective of troubleshooting is to determine why something does not work as expected and explain how to resolve the problem.
    - Scheduling imports of data
      BigFix clients report data to the BigFix server that stores the data in its file system or database. BigFix Inventory server connects to the BigFix server and its database, downloads the stored data, and processes it. This process is called an import or Extract, Transform, Load (ETL). By default, the import runs once a day at midnight. You can schedule it for a period that is most suitable for your environment considering its size and specification.
    - Creating capacity configuration for Linux on z Systems
      To properly calculate subcapacity values for products that are installed on Linux on z Systems, create capacity configuration for such computers. First, run a fixlet that creates a file with manually entered capacity values and places it on the target computer. Then, run regular software and capacity scans to discover the installed software and calculate its license metric utilization.
    - Setting the DSD mode on Solaris
      If a computer runs the Solaris operating system and is in the DSD domain, set the DSD mode to ensure that metric utilization is correctly calculated for software that is installed on this computer. If you do not set the DSD mode, Solaris machines in DSD might not be properly identified and metric utilization might be underestimated.
    - Advanced Scanner Configuration Option
    - Optimizing scanner cache configuration
      The scanner cache folder is used to store information about scanned files and directories in your file system. By knowing the hierarchy of files, the scanner can locate them quicker, which results in shorter 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 location of the cache folder cannot ensure sufficient disk space, you can change the location of the cache folder or optimize the cache.
    - Deprecated: Setting up additional analysis properties
      Analysis properties are used to recognize software and gather information about its usage. Analysis properties are set by default in BigFix Inventory. You can also set up your own properties that you want to use to gather information from the endpoints.
    - Disabling the collection of software usage
      Information about software usage is collected if you enabled the default scan configuration or manually activated the Application Usage Statistics analysis and ran the relevant scan. If you are in the initial deployment phase, or if you do not need information about software usage, you can disable the collection of this information to improve BigFix Inventory performance and shorten the import time.
  - Discovering software and hardware on IBM i
    Available from 9.2.5. You can discover software and hardware inventory on IBM i systems by using disconnected scans that do not require direct connection between the scanned computers and BigFix server. Scripts that are provided in the disconnected scanner package initiate software and capacity scans, and prepare scan results that you later on upload to BigFix Inventory.
- Performing optional configuration
  You can perform optional configuration tasks to further customize the application.
- Classifying the BigFix client used by multiple BigFix products

Understanding the Deployment Health and Software Scan Health

Available from 9.2.7. Deployment Health and Software Scan Health contain information about your clients and the scans that were initiated. You can view this information on the Deployment Health, and Software Scan Health widgets on the dashboard, or on the Computers report. Deployment Health excludes all the disconnected datasource endpoints. To properly understand values that are displayed for systems scanned with disconnected scans, see the explanation of particular columns on the Computers report.

Table 1. Explanation of Deployment Health and Software Scan Health information for systems with disconnected scans
Column Name	Description
Has Outdated Version	Always shows `No`.
Has Low Disk Space	Always shows `No`.
Is Out of Sync	Always shows `No`.
Has Missing Prerequisites	Always shows `No`.
Agent Version	Taken from the Agent Version property in the computer.yml file.
Catalog Scan Successful	Shows `Yes` if the imported package contains the catalog_scan.xml file.
Software Tags Scan Successful	Shows `Yes` if the imported package contains the isotag_scan package.
File System Scan Successful	Shows `Yes` if the imported package contains the file_scan.xml file.
Package Scan Successful	Shows `Yes` if the imported package contains the package_scan.xml file.
Catalog Version	Taken from the Catalog Version property in the computer.yml file.
Endpoint Scanner Catalog Version	Taken from the Catalog Version property in the computer.yml file. It displays only the second part of the whole catalog version, for example 1250110.1.
Last Scan Attempt	Taken from the timestamp used in the final package name.
Scanning Shared Disks	Always shows `No`.
Mounted Shared Disks	Always shows `''`.