List of fixlets and tasks
The list and description of fixlets and tasks available in the BigFix console on the BigFix Inventory v10 site.
Required configuration fixlets and tasks
There are four basic fixlets and tasks that are required to configure BigFix Inventory to collect all necessary data from the computers in your environment.
Name | Category | Description |
---|---|---|
Get Oracle Database Auditing Data | Scanner | Use this task to collect information about database editions and features for auditing Oracle software installed on your infrastructure. The task executes Oracle usage reporting script and uploads results to BigFix server. The fixlet also contains a link to download the script for manual execution without the fixlet. For more information, refer to Scheduling Oracle Auditing scans. |
Configure Collection of Oracle Auditing Data in VM Manager Tool | VM Managers | Use this task to enable or disable collection of Oracle auditing data in VM Manager tools. To review the current setting, check the results of Oracle Auditing Data Collection Settings analysis. For more information, refer to Configuring VM Managers. |
Get Oracle Hardware Auditing Data | Scanner | Use this task to collect hardware information for auditing Oracle software installed on your infrastructure. The task executes Oracle reporting script and uploads results to BigFix server. For more information, refer to Schedule Oracle Data collection scans. |
Upgrade to the interim version 10.0.x of BigFix Inventory | Deployment | Use this fixlet to upgrade BigFix Inventory through the required
interim versions (10.0.2, 10.0.10) and then to be able to upgrade to
the latest version. This is applicable depending on the current
BigFix Inventory version. For more information, refer to Upgrading to BigFix Inventory v10. The fixlet description includes links that allow you to manually download BigFix Inventory. |
Upgrade to the latest version of BigFix Inventory | Deployment | Use this fixlet to directly upgrade BigFix Inventory
to the latest version. For more information, refer to Upgrading to BigFix Inventory v10.
The fixlet description includes links that allow you to manually
download BigFix Inventory. Note: For
BigFix Inventory to be compliant with IBM Subcapacity,
you must upgrade the
server. |
Download PVU table | Deployment | This task provides a link to the latest PVU table. Download the file and then manually upload it to the BigFix Inventory server. For more information, refer to download instructions. |
Install or Upgrade Scanner | Scanner |
BigFix Inventory requires a dedicated scanner to be installed on each endpoint. This task installs the scanner or upgrades it to the latest version on the specified endpoints. For more information, see: Installing the scanner. Analysis: Scanner Information |
Run Capacity Scan and Upload Results | Scanner | After you install the scanner, you need to schedule capacity scans on all endpoints to ensure that the data in BigFix Inventory is complete. By default, the capacity scan is set to run every 30 minutes and usually takes a few seconds. The frequency is required by the IBM pricing for subcapacity reporting. This task runs the capacity scan to retrieve data from the specified endpoints. If the action is completed, the results were gathered and uploaded. For more information, see: Initiating the capacity scan on all computers. |
Initiate Software Scan | Scanner | Use this fixlet to configure software scan that analyzes the file
system and registry, and discovers the installed software. The scan
can take from few minutes to few hours depending on the number of
files in your file system. You can specify the exact date and time
of the scan, not to affect other business applications running on
the system. Additionally, you can set a CPU threshold for the scan
to minimize its impact, however, that will make the scan last
longer. Select all the listed scan types. If the task is not relevant for some endpoints, log in to the BigFix Inventory and run the initial import to ensure that the catalog is propagated to all endpoints. This task is not relevant on endpoints where the scanner is not installed. For more information, see: Initiating software scans. Analysis: Software Scan Status |
Upload Software Scan Results | Scanner | This task uploads inventory data that is collected by the software scans from the specified endpoints to the BigFix server. Each endpoint should be targeted only once. For more information, see: Uploading software scan results. |
Troubleshooting fixlets
There are several fixlets and tasks that can help you troubleshoot the most common issues and questions related to the application.
Name | Category | Description |
---|---|---|
Analyze the Relevance of a Fixlet or Task | Troubleshooting | This task creates an analysis that checks which relevance conditions of a particular fixlet or task are not met. Check the results of the analysis to learn why a fixlet or task is not relevant on a particular endpoint. The analysis is created in the Master Action site. For more information, see: Checking why a fixlet or task is not relevant. |
Force Reupload of Software Scan Results | Troubleshooting | This task forces reupload of inventory data that was gathered by the software inventory and the file system scans. The data is reuploaded to BigFix once and no schedule is set. The data is then transferred to BigFix Inventory during the import. The import includes results of the full file system scan, not the delta scan. It might affect the length of the import. |
Gather Environment Information | Troubleshooting | This task retrieves information about BigFix Inventory and BigFix environment for troubleshooting purposes. The task is relevant only for the Linux operating system. |
Other fixlets
The remaining fixlets and task can help you manage, configure, troubleshoot, deploy and migrate the product and its components, and manage VM Managers.
Name | Category | Description |
---|---|---|
Install or Upgrade Scanner in private mode on windows | Scanner | BigFix Inventory requires a dedicated scanner to be installed on each endpoint. This task installs the scanner or upgrades it to the latest version on the specified endpoints in a private mode. It installs CIT binaries in <BES Client>\LMT\CIT\scanner directory, but without registering the instance in CIT global files (no cit.ini or other global CIT configuration files).In case when there is a global CIT with SUA exploiter already installed, the SUA exploiter will be uninstalled from the global CIT and upgraded to the private version. |
Add Excluded Directories | Scan Management | This task is used to add entries to the list of directories that are excluded from scanning. After you specify the directories, run the task against the chosen endpoints. The directories are then sent to the scanner that omits them during the software scan. For more information, see: Excluding additional directories. |
Add Targeting Exception to Temporarily Disable Scans | Configuration | This task prevents software and capacity scans that are scheduled on the endpoint from running without the need of modifying the entire scan schedule. You can use it to temporarily disable scans on a computer that undergoes maintenance, patching, or some other resource-consuming action that could be disturbed by the software or capacity scan. |
Change Scanner Cache Folder | Scanner | This task allows you to select a new cache folder to store the scanned cache data. The task cannot be performed when a scan is in progress. If the task is relevant, the scanner is installed in all applicable endpoints. The task is not applicable to endpoints which have HCL scanner installed in private mode. For more information, see: Optimizing scanner cache configuration. |
Collect Detailed Hardware Information | Scanner |
This task runs a detailed hardware scan on the specified endpoints. It collects 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 and AIX. The task can be run also on other operating systems but the returned results might not be accurate. For more information, see: Detailed hardware scan. Analysis: Detailed Hardware Information |
Collect Logs from Endpoints | Troubleshooting | The task collects BigFix client logs, scanner logs, scan configuration logs, VM manager configuration files, and files generated during scans. Run this task when you are requested by BigFix Support to collect log files for troubleshooting purposes. |
Configure Collection of Additional Properties of Windows Executables | Scan Management | This task allows you to enable the collection of additional properties of Windows executables by running a fixlet that changes the configuration of the software scan for BigFix Inventory. For more information, see: Enabling collection of additional properties of Windows executables. |
Configure File Checksums Collection (MD5/SHA-256) | Scan Management | This task enables the collection of file checksums and is intended for advanced security scenarios only. The MD5 and SHA-256 checksums are calculated during the file system scan, and are created for each file that is discovered by the software scan. For more information and requirements, see: Collecting file checksums. |
Configure Scan Cache | Scanner | This task allows for configuring the file system scan cache. By default, the cache is enabled and is cleared after every scan. The cache is shared by different scan types. Disabling the cache will significantly impact scan performance, and it is not recommended, unless absolutely necessary. The task is relevant only on computers where the scanner is installed. For more information, see: Optimizing scanner cache configuration. |
Configure Scanner Query Timeout | Scanner | This task allows you to set the maximum time in which the software scan process should finish. As the software scan involves scanning as well as additional evaluation, the overall software scan time might exceed the value provided. |
Create Capacity Configuration for Linux on z Systems | Configuration | This task creates a file that contains the manually-entered capacity values. If this task is relevant, it means that no capacity configuration exists on this endpoint yet and the manual configuration is required. If this fixlet is not relevant on a computer, you do not have to perform any manual actions to calculate the capacity values. For more information, see: Creating capacity configuration for Linux on z Systems. |
Delete Capacity Configuration for Linux on z Systems | Configuration | This task deletes the file that contains the manually-entered capacity values. |
Disable Application Usage Statistics | Configuration | This task disables the collection of application usage statistics on endpoints. For more information, see: Disabling the collection of software usage. |
Disable Collecting Executable Files Based on Application Usage | Configuration | Collecting executable files based on application usage is automatically enabled when you have the BigFix client and server in version 9.5.5 or higher, use Linux or Solaris system, and have the Application Usage Statistics analysis activated. This task disables collection of executable files that are based on the list of processes on endpoints. If you run this task, the files associated with these processes are not displayed on the Scanned File Data report. |
Discover Remote Shared Disks | Scan Management |
This task identifies shared disks that exist in your environment. For more information, see: Discovering software on shared disks and Limiting scope of automated scan. Analysis: Shared Disk Information |
Download BigFix Inventory | Deployment | This task downloads the newest BigFix Inventory server installer to the specified
endpoint. The fixlet description include links that allow you to manually download BigFix Inventory. |
Download the Disconnected Scanner Package (version) | Deployment | This task provides a link to the latest disconnected scanner package. The package contains installation and configuration files, and the scripts that are required for software and capacity discovery on Windows and Linux computers. This solution can only be used if the BigFix client cannot be installed due to legal, business, or technical reasons. For more information, see: Discovering software and hardware with disconnected scanner on Windows and UNIX. |
Download the Disconnected Scanner Package for IBM i (version) | Deployment | This task provides a link to the latest disconnected scanner package for IBM i. The package contains installation and configuration files, and the scripts that are required for software and capacity discovery on IBM i systems. For more information, see: Discovering software and hardware on IBM i. |
Edit Capacity Configuration for Linux on z Systems | Configuration | This task edits the file that contains the manually-entered capacity values. If this task is relevant, it means that the capacity configuration already exists on this endpoint. |
Edit Scanner Trace Settings | Troubleshooting | This task allows you to set debug traces for the scanner. If this task is relevant, it means that the scanner is installed on an endpoint. For more information, see: Changing scanner trace settings. |
Enable Collecting Executable Files Based on Application Usage | Configuring | This task enables collection of executable files that are based on the list of processes on endpoints. If you run this task, the files associated with these processes will be displayed on the Scanned File Data report. Use this task if you previously disabled the feature using the Disable Collecting Executable Files Based on Application Usage fixlet. |
Force VM Manager Tool Scan Results Upload | Troubleshooting | This task forces the upload of capacity data collected by VM Manager Tool or by the Run Capacity Scan on Virtualization Hosts task. The data is uploaded to BigFix and can be transferred to BigFix Inventory by running a data import. The data is uploaded only once and no schedule is set. For more information, see: Forcing the upload of collected data. |
Get Microsoft Exchange Edition | Scanner | This task allows you to retrieve information about the editions of Microsoft Exchange servers that are installed on the computers in your infrastructure. For more information, see: Discovering Microsoft Exchange edition. |
Get Oracle Concurrent Sessions Number | Scanner | This task allows you to retrieve information about the high water mark value of concurrent sessions for Oracle Databases that are installed on the computers in your infrastructure. For more information, see: Metering the number of Oracle Database concurrent sessions. |
Get Oracle Features | Scanner | This task allows you to retrieve information about the editions and features of Oracle Databases that are installed on the computers in your infrastructure. For more information, see: Extended discovery of Oracle Database. |
Get SAP Components | SAP Systems | This task allows you to retrieve information about the SAP components that are installed on the computers in your infrastructure. For more information, see: Discovering SAP components. |
Identify Computers on Public Clouds | Configuration | This task marks targeted endpoints as computers that are running on a public cloud. It allows the specific license model for the PVU count without hypervisor access. For more information and a list of supported public clouds, see: Identifying computers on public clouds. |
Initiate Collection of SAP Metric Data | SAP Systems | This task runs the SAP Metric Data Collector. The tool collects license metric utilization data from a single SAP landscape. For more information, see: Collecting utilization of SAP license metrics. |
Initiate Software Scan on Shared Disks | Scanner |
This task runs the catalog-based scan, file system scan, and software identification tags scan to discover software that is installed on shared disks. Scan results are used to create software templates that represent the discovered software. The templates are later on shared between all computers on which the disks are mounted to ensure that the software is reported on these computers. For more information, see: Discovering software on shared disks and Limiting scope of automated scan. Analysis: Status of Shared Disks Software Scan |
Install Additional VM Manager Tool version number (OPTIONAL) | VM Managers | This task installs an additional VM Manager Tool in the specified version on any computer. The tool should only be used to manage VM managers that are in separated networks and cannot be reached by the BigFix server. For more information, see: Managing VM managers. |
Install SAP Metric Data Collector | SAP Systems | This task installs the SAP Metric Data Collector in the specified version on a selected computer. The tool collects license metric utilization data from a single SAP landscape. For more information, see: Collecting utilization of SAP license metrics. |
Install VM Manager Tool version number | VM Managers | This task installs VM Manager Tool in the specified version on the BigFix server. Use this task if automatic installation failed. For more information, see: (Optional) Installing VM Manager Tool. |
Refresh Re-Subscribed Endpoints | Scanner | This fixlet detects endpoints that were re-subscribed from a different fixlet site and is used for the coexistence of License Metric Tool and BigFix Inventory. For such endpoints, it forces the upload of capacity data, and refreshes properties to ensure that they are related to the relevant fixlet site. An endpoint is refreshed after each re-subscription. The initial subscription is set after running the software scan. |
Remove Capacity Scan Data from Virtualization Hosts | VM Managers | This task applies to the KVM and Xen hosts only. It removes the data that was generated on virtualization hosts during the capacity scan. For more information, see: Collecting capacity data from virtualization hosts for Xen and KVM. |
Remove Excluded Directories | Scan Management | This task is used to remove entries from the list of directories that are excluded from scanning. After you specify the directories, run the task against the chosen endpoints. The directories are then sent to the scanner that includes them back in the software scan. For more information, see: Including the excluded directories back in scans. |
Remove Targeting Exception to Resume Scans | Configuration | This task resumes software and capacity scans that were temporarily disabled by using the Add Targeting Exception to Temporarily Stop Scans task. |
Run Capacity Scan on Virtualization Hosts | VM Managers | This task applies to the KVM and Xen hosts only. It runs a capacity scan on virtualization hosts to retrieve capacity data from all virtual machines that are managed by the specified host. Schedule the scan on every host that manages virtual machines which have the BigFix client installed. For more information, see: Collecting capacity data from virtualization hosts for Xen and KVM. |
Schedule VM Manager Tool Scan Results Upload | VM Managers | This task schedules regular uploads of capacity data collected by VM Manager Tool or by the Run Capacity Scan on Virtualization Hosts task. The data is uploaded to BigFix and can be transferred to BigFix Inventory by running a data import. For more information, see: Changing the upload schedule. |
Set DSD Mode | Configuration | This task sets the DSD mode on Solaris endpoints. If the Solaris system is in the DSD domain, set this mode so that the PVU data is correctly calculated. For more information, see: Setting the DSD mode on Solaris. |
Software Catalog Update (version) | Deployment |
Starting from application update 9.2.11, the catalog update process is automatized. This task automatically downloads the software catalog, and uploads it to the BigFix Inventory server during the next import of data. No further action is required. For versions before 9.2.11, this task downloads the latest
software catalog to the computer where the BigFix Inventory server is installed. After the file is
downloaded, you must upload it to the BigFix Inventory server. For more information, see: Updating server software catalog.
Warning: Since catalog version 10.0.2,
Software Catalog Update fixlet updates only non-IBM part of
the catalog. The same applies to the manual catalog upload.
To get the latest supported IBM catalog part you must
upgrade BigFix Inventory. It is
in line with IBM ILMT 9.2.20, https://www.ibm.com/support/pages/node/6223460. However, the definition of the software catalog does not change for other vendors, and the manual updates continue to be supported. |
Uninstall SAP Metric Data Collector | SAP Systems | This task uninstalls the SAP Metric Data Collector from the selected computer. It also removes folders that the tool uses as well as deletes settings of the BigFix client specific to the tool. |
Uninstall Scanner | Scanner | This task uninstalls the scanner and the corresponding
configuration files from the specified endpoints. Uninstall Scanner fixlet removes all CIT exploiters |
Uninstall VM Manager Tool | VM Managers | This task uninstalls the VM Manager Tool from the specified endpoints. It also deletes the client settings and folders used by the VM Manager Tool. For more information, see: Uninstalling VM Manager tool. |
Unset DSD Mode | Configuration | This task unsets the DSD mode on Solaris endpoints. For more information,see: Setting the DSD mode on Solaris. |
Update SAP Metric Data Collector | SAP Systems | This task updates the SAP Metric Data Collector to the latest version. |
Update VM Manager Tool to version version number | VM Managers | This task updates VM Manager Tool to the specified version. For more information, see: Updating VM Manager Tool. |
Upgrade to the latest version of BigFix Inventory10 | Deployment | This fixlet upgrades BigFix Inventory to the latest version. It also uploads the latest software catalog and PVU table to the BigFix Inventory server. For more information, see: Upgrading to BigFix Inventory v10. |
WARNING: Endpoints Subscribed to Multiple Sites | Troubleshooting | Some of your endpoints are subscribed to both the IBM License Reporting (ILMT) v9 and the BigFix Inventory v10 fixlet site, which will lead to issues with software discovery that are not supported. An endpoint can report to only one application at a given moment. Remove the endpoints from one of the sites. |
Clear cache to force rescan Docker containers during next Software Scan | Deployment |
Use this fixlet to force rescanning of docker containers during the next Initiate Software Scan. You need to clear cache of already scanned images. This task refers to the ISO tagged software scan on Docker containers. This fixlet is related to Discovery of software in Docker containers. |