Skip to content
Documentation

Unhealthy Agents

The Unhealthy agents view under Views in Configuration Management lists the computers whose CapaInstaller Agent the health check couldn’t repair.

How the health check works

Section titled “How the health check works”

The purpose of the CapaInstaller Agent health check is to keep a healthy and up-to-date agent on every computer and server. The health check is the script CapaInstaller Health Check.vbs in the agent folder, and it runs automatically:

  • At the start of an agent run. The CapaInstaller Agent service (cistub) runs the health check once per session before a scheduled run, a network-connected run, or a remote run.
  • At least once a day. The CapaInstaller Service Health Service (ciinstsvc), which is installed on every computer during agent deployment, runs the health check if it hasn’t run within the last 24 hours.

When the health check is started by one of the services, it does the following:

  • Checks the CapaInstaller Service Health Service (ciinstsvc)
  • Checks the .NET runtime
  • Checks the CapaInstaller Scripting component
  • Checks that the .cis extension is registered to use the VBScript engine
  • Checks the CapaInstaller Agent service (cistub)
  • Updates the agent files
  • Updates the service files

If a component check fails, the standard installation method is used to repair the component. If the same error is found again on the next health check, or if the error can’t be repaired (for example, if the .NET Framework is missing), the computer is reported as unhealthy and appears in the Unhealthy agents view.

Run the health check from an AD startup script

Section titled “Run the health check from an AD startup script”

You can also start the health check from an Active Directory startup script. When the script is started this way, it doesn’t download files. It only runs these checks:

  • Checks the CapaInstaller Service Health Service (ciinstsvc)
  • Checks the .NET runtime
  • Checks the CapaInstaller Scripting component
  • Checks that the .cis extension is registered to use the VBScript engine
  • Checks the CapaInstaller Agent service (cistub)

To start the script from the AD startup script, use the following command:

cscript "%ProgramFiles%\CapaInstaller\Agent\CapaInstaller Health Check.vbs"