Understanding the output of deploy and Run tasks
With Linux content, endpoint scans are performed using a series of Linux shell scripts, offering enhanced accessibility for Linux system administrators.
Unlike most BigFix content where Fixlets continuously evaluate conditions at each endpoint, Linux content utilizes a Deploy and Run task from the Security Checklist to initiate a scan on the endpoints. This scan can be executed on-demand whenever needed or scheduled as a recurring policy from the console.
The endpoint scan is carried out by various Linux shell scripts available within the Deploy and Run tasks. These scripts write the gathered information to an output file, which is then used by the corresponding Fixlet checks for evaluation. Once the results files are written to disk, the Fixlets read the output and display the results in the console.
/var/opt/BESClient/__BESData/__SCMData/
,
which contains several components as detailed below:
fileresults.db |
Created upon successful completion of the Deploy and Run tasks, storing the results of the entire filesystem scan. |
<HashValue>.out |
Stores the results of a particular Fixlet audit script. |
<HashValue>.out.err |
Contains error outputs from a specific Fixlet audit script. |
<HashValue>.out.metadata |
Stores metadata related to a specific Fixlet audit script. |
remediation.log |
Logs the actions executed by the script. |
remediation.log |
Contains error logs related to the action script. |
remediation.log.metadata |
Stores metadata related to the action script. |