CapaInstaller agent health check
Introduction
Section titled “Introduction”The purpose for the CapaInstaller Agent Health Check is to maintain a healthy and up to date agent on every computer/server. In the following section an in depth technical description can be found. A technical description of the service can be viewed in the below.
| Element | Description |
| Ciinstsvc | 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 |
| Component check fail | 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 system group named “Unhealthy Agents”. |
| CapaInstaller Health Check.vbs | If the script named “CapaInstaller Health Check.vbs” is launched from the AD startup script the following check 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 \ServerName\ShareName\Resources\Agent\CapaInstaller Health Check.vbs Example: Cscript \ws32-srv2003\cmpProd\resources\Agent\CapaInstaller Health Check.vbs \ws32-srv2003\cmpProd |
The purpose for the CapaInstaller Agent Health Check is to maintain a healthy and up to date agent on every computer/server. In the following section an in dept technical description can be found.
Technical overview
Section titled “Technical overview”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 system group named “Unhealthy Agents”.
If the script named “CapaInstaller Health Check.vbs” is launched from the AD startup script the following check 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 \ServerName\ShareName\Resources\Agent\CapaInstaller Health Check.vbs . E.g.
Cscript \ws32-srv2003\cmpProd\resources\Agent\CapaInstaller Health Check.vbs \ws32-srv2003\cmpProd
Beawre that the unit will be moved to the point that the server belongs to.
The following command line arguments are available (Service Update 1 - 2011):
Section titled “The following command line arguments are available (Service Update 1 - 2011):”/Force -> The core agent health check will only be executed if it hasn’t been executed for 30 minutes. If the argument /Force is specified the core check will be executed.
/Debug -> Run in debug mode.
/Dontmove -> If the specified management server is different from the current management server the agent will be moved to the new server. However if the argument /Dontmove is specified the agent will not be moved
Example:
Section titled “Example:”cscript “\DC1-SKANDERBORG\Produktion\Resources\Agent\CapaInstaller Health Check.vbs” \DC1-SKANDERBORG\Produktion /debug
cscript “\DC1-SKANDERBORG\Produktion\Resources\Agent\CapaInstaller Health Check.vbs” \DC1-SKANDERBORG\Produktion /debug /Force