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.
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.
Step 5: Collecting hardware information and capacity data
The hardware information and capacity data concern information about your processors, and the processor capacity that is assigned to each computer. You can review the information on the Hardware Inventory report. The hardware and capacity data is essential to calculate processor-based metrics, for example PVU.
Client Installation on Oracle Solaris
To ensure that the capacity data is properly collected from computers that are running on the Oracle Solaris virtualization, install the BigFix client on all required operating systems, zones and domains. Then, set up capacity scans on each endpoint.

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.
    - Distribution of scans for improved performance
      Performance of importing data from the BigFix server to BigFix Inventory depends on the number of scan files, usage analyses, and package analyses that are processed during a single import. By properly scheduling scans and distributing them over the computers in your infrastructure, you can reduce the length of the data import.
    - Step 1: Activating the analyses
      An analysis is a collection of property expressions that is used to view and summarize properties of computers in your infrastructure. Some of the analyses are required to discover installed software and must be activated all the time. Other analyses are used only in specific scenarios or for troubleshooting purposes and can be activated according to your needs.
    - Step 2: Installing the scanner
      The scanner collects hardware information as well as information about files and packages that exist on the computers in your infrastructure. Install the scanner on every computer on which you want to detect software. If you enabled the default scan configuration, the scanner is installed automatically and this configuration is not required.
    - Step 3: Initiating software scans
      During the software scans, the scanner collects information about files with particular extensions, package data, and software identification tags to evaluate whether particular software is installed on the computers in your infrastructure. It also gathers information about the running processes to measure software usage. By default, software scans are scheduled to run regularly but you can specify the exact days and times of the scans, or modify their start and end dates.
    - Step 4: Uploading software scan results
      When the software scan finishes, its results must be uploaded from the computers in your infrastructure to the BigFix server. To ensure that software inventory data is up-to-date, software scans and uploads of their results should run on a similar schedule.
    - Step 5: Collecting hardware information and capacity data
      The hardware information and capacity data concern information about your processors, and the processor capacity that is assigned to each computer. You can review the information on the Hardware Inventory report. The hardware and capacity data is essential to calculate processor-based metrics, for example PVU.
      - Initiating the capacity scan on all computers
        The capacity scan is the essential part of collecting capacity data and should run on all computers, including Oracle Logical Domains. The scan runs every 30 minutes, and collects data about the physical processor, system type (physical or virtual), guest operating system, and logical partitions.
      - Client Installation on Oracle Solaris
        To ensure that the capacity data is properly collected from computers that are running on the Oracle Solaris virtualization, install the BigFix client on all required operating systems, zones and domains. Then, set up capacity scans on each endpoint.
      - Adding VM managers for VMware, Hyper-V, KVM with RHEV-M, and XenServer
        After you configure the capacity scan, BigFix Inventory can evaluate capacity of virtual machines in your environment. However, to accurately calculate subcapacity consumption, it also needs data about physical hosts on which these VMs are running. The data can be collected only from VM managers. To ensure that the data is available to BigFix Inventory, configure connections to VM managers in your infrastructure.
      - Collecting capacity data from virtualization hosts for Xen and KVM
        For Citrix, Xen and KVM, connection to the VM manager does not have to be defined in BigFix Inventory to collect capacity data. The data can be collected directly from virtualization hosts by using the Run Capacity Scan on Virtualization Hosts task.
      - Identifying computers on public clouds
        Available from 9.2.1. For all computers that run on public clouds, you must additionally identify them as such. This is required to apply the correct PVU rates, which might differ between the public clouds. It is enough to run a Fixlet against these computers and specify the type of the public cloud.
  - 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 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 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.
- Performing optional configuration
  You can perform optional configuration tasks to further customize the application.
- Classifying the BigFix client used by multiple BigFix products
  BigFix client is a component that is common for all products from the BigFix family. If you have a number of BigFix products installed, the client must be classified as used by these products. Because the client is usually installed on all computers in the enterprise, its manual classification can be time-consuming. To reduce the amount of time and resources that are needed to perform this task, you can generate license tags. The tags mark the client as used by the BigFix products that are installed in your infrastructure. The information is later on reflected in BigFix Inventory without the need of manual classification.

Client Installation on Oracle Solaris

To ensure that the capacity data is properly collected from computers that are running on the Oracle Solaris virtualization, install the BigFix client on all required operating systems, zones and domains. Then, set up capacity scans on each endpoint.

Install the BigFix client in the following order:

Global zone in the Control Domain (if it exists)
Global zones
Local zones and Kernel zones

You might change the order and install the BigFix client on the computers in the local zone first. As a result, these computers have the No Host Scan Data status until you install the BigFix client on the computers in the global zone.

Examples

The following examples of possible installation scenarios describe in what order you might install the BigFix client on computers in the global and local zones.


Scenario		Applicable for
Scenario		Solaris x86	SPARC
To discover an application that is installed on operating system 2 (local zone), install the client in the following order: Operating system 1 (global zone) Operating system 2 (local zone)		Yes	Yes
To discover an application that is installed on operating system 3 (local zone), install the client in the following order: Operating system 1 (global zone) Operating system 2 (global zone in the Kernel Zone) Operating system 3 (local zone in the Kernel Zone)		Yes	Yes
To discover an application that is installed on operating system 4 (local zone on a Logical Domain that is not the Control Domain), install the client in the following order: Operating system 1 (global zone in the Control Domain) Operating system 3 (global zone of operating system 4 in the Logical Domain) Operating system 4			Yes
To discover an application that is installed on operating system 2, install the client in the following order: Operating system 1 (global zone in the Control Domain) Operating system 2			Yes
To discover an application that is installed on operating system 5 (local zone in the Kernel Zone), install the client in the following order: Operating system 1 (global zone in the Control Domain) Operating system 3 (global zone of operating system 4 in the Logical Domain) Operating system 4 (global zone of operating system 5 in the Kernel Zone) Operating system 5			Yes