Baseline inventory is only available for Windows computers.
The baseline inventory process uses and creates several baseline files. A baseline configuration file contains options for running the scans. For example, you configure the files or registry keys to be included or excluded, the directories to scan, and so on. You can use the default configuration file, edit it, or create one or more custom configuration files. Configuration files for registry baselines are in INI format. The default registry baseline configuration file is AexRegScan.ini. Configuration files for file baselines are in INI format but have the .bls extension. The default file baseline configuration file is local_master.bls.
The local baseline tasks use the default configuration files.
A baseline snapshot (BLS) file maintains a record of the files or registry settings on a computer at a given time. This data is gathered during a baseline scan that is based on the options in a baseline configuration file. Registry baseline snapshots are saved to a new file on the scanned computer in .RBL format.
File baseline snapshots are appended to the baseline configuration file. The location of the default baseline snapshot files is as follows:
The file compliance scan and the registry compliance scan create output in XML format. This output is stored in Notification Server Events (NSEs) and reported to the Configuration Management Database (CMDB).
The default locations of the file baseline tasks and the registry baseline tasks, respectively, are as follows:
You need to make sure that you copy or keep the baseline configurations and baseline snapshots that you want to use for compiling a custom baseline or comparing with a custom baseline when running these tasks. Otherwise, the task fails.