Home
Managing the infrastructure
After you complete the initial configuration of BigFix Inventory, learn how to manage components of its infrastructure: VM managers, server, database, and data sources.
Managing VM managers
VM managers are pieces of software that create, manage, and monitor virtual machines. You configure connections to VM managers so that BigFix Inventory can gather data that is required to calculate utilization of license metrics in virtual environments.
Maintenance tasks
You can perform additional maintenance and troubleshooting tasks on VM Manager Tool. These tasks are not limited to a specific approach to VM management, but can be applied to any instance of VM Manager Tool.
Log files
You can gather the log files to determine the problems that are related to the VM Manager tool. You can also change the log settings.

Managing the infrastructure
After you complete the initial configuration of BigFix Inventory, learn how to manage components of its infrastructure: VM managers, server, database, and data sources.
- Computer statuses
  Computer statuses provide information about the condition of the computers that are monitored by BigFix Inventory. To properly discover the installed software and measure its license metric utilization, ensure that computers in your environment work correctly.
- Managing VM managers
  VM managers are pieces of software that create, manage, and monitor virtual machines. You configure connections to VM managers so that BigFix Inventory can gather data that is required to calculate utilization of license metrics in virtual environments.
  - Default PVU counting on x86 processors
    To properly calculate PVU subcapacity, BigFix Inventory requires information about the number of processor cores that are available to virtual machines and on the physical computers that host these machines. If the information is not available, license metric utilization cannot be properly calculated and reported results might be over-counted for x86 processors.
  - Supported virtualization types
    BigFix Inventory requires that connections to VM managers are defined for the following virtualization types: Kernel-based Virtual Machine, Microsoft Hyper-V, VMware vSphere, and Xen.
  - Flow of capacity data from VM managers
    To understand how capacity data is gathered in virtual environments, see what data flows between virtual machines, VM Manager tool, and the BigFix Inventory server, and how frequently it is transferred.
  - Basic VM management (central)
    Use basic VM management if the BigFix server can connect to VM managers in your infrastructure. It is the default method of configuring connections to VM managers through the BigFix Inventory user interface.
  - Advanced VM management (distributed)
    Use advanced VM management if the BigFix server cannot connect to some of the VM managers because they are in separated networks. This approach requires that you install an additional VM Manager Tool, and configure VM managers through the command line.
  - 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.
  - Maintenance tasks
    You can perform additional maintenance and troubleshooting tasks on VM Manager Tool. These tasks are not limited to a specific approach to VM management, but can be applied to any instance of VM Manager Tool.
    - VM Manager tool installation requirements
      The computer on which you install the VM Manager tool must meet all software and hardware requirements.
    - Log files
      You can gather the log files to determine the problems that are related to the VM Manager tool. You can also change the log settings.
    - Changing the upload schedule
      Capacity data collected by VM Manager Tool is uploaded to the BigFix server every 12 hours. You can change this schedule by removing the default schedule and creating a new one.
    - Forcing the upload of collected data
      You can force the collected data to be immediately uploaded to the BigFix server. The data is uploaded once and no schedule is set.
    - Checking the VM Manager tool version
      Activate the VM Manager Information analysis to retrieve data about the installed version of VM Manager tool. You can use the analysis to quickly confirm the successful installation of the tool.
    - Updating VM Manager Tool
      You can update VM Manager Tool to the newest version.
    - Uninstalling VM Manager tool
      Follow the procedure to uninstall the VM Manager tool from the endpoints and to delete all the related settings and folders. Uninstallation of the VM Manager tool is also required if you want to reinstall the tool.
    - Backing up and restoring the VM Manager tool
      To avoid losing configuration of VM manager connections due to corruption of VM Manager tool files, back up the /LMT/VMMAN/config/ and /LMT/VMMAN/keydb/ directories. If the VM Manager tool files are corrupted, reinstall the VM Manager tool and restore the two directories from the backup location.
  - Best practices for configuring VM managers
    Apply the best practices when configuring VM managers to ensure that your infrastructure works efficiently.
- Administering the server
  Perform administering tasks on your server to configure advanced settings, or restart its services.
- Administering the database
  Perform administering tasks on your database to keep it in good condition, protect your data, or configure additional settings.
- Removing inactive computers
  When you decommission a computer in your infrastructure, it continues to report to BigFix Inventory. The data is still collected from this computer, and displayed on the metric reports. To ensure that all infrastructure changes are reflected in BigFix Inventory, you should remove each decommissioned computer from BigFix. If you cannot remove this computer from BigFix for a valid reason, you can use an alternative solution, and decommission the computer in BigFix Inventory.
- Managing data sources
  Computers in an organization can be divided into organizational units, and can be monitored by multiple BigFix infrastructures. Each infrastructure is referred to as a data source. Data from multiple data sources can be imported to one instance of BigFix Inventory.

Log files

You can gather the log files to determine the problems that are related to the VM Manager tool. You can also change the log settings.

VM Manager tool log files are stored at:

Trace log files: BES Client\LMT\VMMAN\logs
Installation log files: BES Client\LMT\VMMAN\logs\install

You can also gather the complete set of logs by running the -retrievedebugdata command in VM Manager tool.

Log settings

You can change the log settings by editing the following files:

log4j.properties for application update 10.0.2 and lower
log4j2.xml for application update 10.0.3 and higher

The following parameters are the most useful:

For versions below 10.0.3

log4j.appender.mylogger.maxFileSize specifies the maximum size of a log file

Default value = 1000 KB

log4j.appender.mylogger.MaxBackupIndex specifies the maximum number of log files

Default value = 10

log4j.rootLogger specifies the logging level

Default value = INFO. You can change it to DEBUG to enable debug logging.

For versions 10.0.3 and 10.0.4

SizeBasedTriggeringPolicy specifies the maximum size of a log file

Default value = 1 MB

DefaultRolloverStrategy specifies the maximum number of log files

Default value = 10

Root level specifies the logging level

Default value = INFO. You can change it to DEBUG to enable debug logging.

For versions 10.0.5 and higher

SizeBasedTriggeringPolicy specifies the maximum size of a log file

Default value = 1 MB

DefaultRolloverStrategy specifies the maximum number of log files

Default value = 2 (number of files for the main trace.log and for every hypervisor log)

Root level specifies the logging level

Default value = INFO. You can change it to DEBUG to enable debug logging.