Windows Services – Custom Test

Like the Windows Services test, the Windows Services – Custom test too reports whether/not specified services are available on the Windows host. Here again, the intent is to alert administrators when services associated with critical Windows applications inadvertently stop. The difference between these two tests however, lies in how these services are to be configured for monitoring. While the Windows Services test needs to be configured with the Display name of the services, the Windows Services – Custom test needs to be configured with the actual Service names.

For instance, if the RDP service on a Windows host is to be monitored for availability, use Figure 1 to understand how this service is to be configured for the Windows Services and the Windows Services – Custom tests. 

Figure 1 : The Service Properties window

Target of the test : A Windows host

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every Service name that has been configured.

Configurable parameters for the test
  1. TEST PERIOD - How often should the test be executed
  2. Host - The host for which the test is to be configured
  3. Port - the port to which the specified host listens
  4. ServiceName - Name of the service that is to be checked. More than one service name can also be provided with comma as the separator.


    When configuring the servicename, make sure that you specify the Service Name and not the Display Name of the service.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Service availability

Indicates the availability of the service.


A value of 100 indicates that the specified service has been configured and is currently executing. A value of 0 for this measure indicates that the specified service has been configured on the server but is not running at this time.  A value of –1 indicates that the service has not been configured on the target system.