Page tree
Skip to end of metadata
Go to start of metadata

Introduction

The following information is the general description of the health check and unhealthy agents in Configuration Management.
 
The purpose for the CapaInstaller Agent Health Check is to maintain a healthy and up to date agent on every computer/server.
 
The fundamental for the health check is a service named CapaInstaller Installation Service (ciinstsvc). The service is installed om every computer/server during agent deployment. The service initiates in a 4 hours interval the health check script named “CapaInstaller Health Check.vbs”. The script has the following functionality when invoked from the service.

  • Check Capanstaller Installation service (ciinstsvc)
  • Check .net runtime
  • Check the CapaInstaller Scripting component
  • Check that .cis extension has been registered to use the vbscript engine
  • Check CapaInstaller Agent service (cistub)
  • Update agent files
  • Update service files
    If a component check fails, the standard installation method is invoked and the component is repaired. If it’s impossible to repair the service a request is sent to the console and the client is added to the unhealthy agent view, which can be found under Views in Configuration Management. If the script named “CapaInstaller Health Check.vbs” is launched from the AD startup script the following checks are completed:
  • Check CapaInstaller Installation service (ciinstsvc)
  • Check .net runtime
  • Check the CapaInstaller Scripting component
  • Check that .cis extension has been registered to use the vbscript engine
  • Check CapaInstaller Agent service (cistub)
    To start the script from the AD start up script use the following: Cscript %ProgramFiles%\CapaInstaller\Agent\CapaInstaller Health Check.vbs
     
    Example: Cscript %ProgramFiles%\CapaInstaller\Agent\CapaInstaller Health Check.vbs \\ws32-srv2003\cmpProd