Agent problems

The Health Check dashboard, and Computer Health information on the Computers report provide the status of computers that do not meet one or more of the deployment or scan health conditions. To resolve health issues, perform the steps relevant for your particular problem. The BigFix console provides fixlets that can be run to resolve some deployment health issues. Issues that cannot be resolved by using fixlets must be resolved manually.

Low disk space: The drive on which the agent is installed has less than 100 MB of free disk space
Computers with low disk space have less than 100 MB of free space available. To identify the affected computers:
  1. Log in to the BigFix console.
  2. Click Sites > External sites > BES Support > Fixlets and Tasks.
  3. In the upper right pane, click BES Client Computer is Low on Free Disk Space. The list of computers is displayed.
  4. Free up disk space on each affected computer.
Out of sync: The time that is set on the computer differs by at least an hour from the time that is set on the server
Out of sync computers have incorrect system clock times. To update the clocks on affected computers:
  1. Log in to the BigFix console.
  2. Click Sites > External sites > BES Support > Fixlets and Tasks.
  3. In the upper right pane, select BES Clients Have Incorrect Clock Time and click Take Action.
  4. In the lower right pane of the window that opens, select the computers whose clocks you want to synchronize and click OK.
Missing prerequisites: Scanner prerequisites are not installed on the computer
Linux™ computers with missing prerequisites do not have the correct C++ runtime library versions installed.
  1. Log in to the BigFix console.
  2. Click Sites > External sites > BigFix Scanner > Analyses.
  3. In the upper right pane, select the Scanner Information analysis and then click Results to see which computers are missing the correct C++ runtime library.
  4. Install the C++ runtime libraries manually on each computer that is returned by this analysis. The required version of the /usr/lib/libstdc++.* or /usr/lib64/libstdc++.* library is 6.
If the scanner is still experiencing problems, ensure the endpoints have the correct version of the bzip2 archiver installed.
  1. Log in to the BigFix console.
  2. Click Sites > External sites > BigFix Scanner > Analyses.
  3. In the upper right pane, select the Software Scan Status analysis and then click Results to see which computers return the Invalid archived status.
  4. Copy the correct version of the bzip2 archive manually to each computer that is returned by this analysis, to the /LMT/CIT/custom folder. Name the file:
    • UNIX bzip2
    • Windows bzip2.exe
    The correct version of the bzip2 archive for your operating system can be obtained from your operating system vendor. It can also be compiled on the endpoint with resources from bzip.