Configuring Service for Windows Checks

From ServersCheck Wiki

Configuring Service for Windows Checks

By default, the ServersCheck Monitoring service is logged on using the local system account. This is very secure, and allows launched applications to be interactive, but one limitation of this account is that it does not have access to network resources.

The Perfcount, Services, Process, CPU, Memory, Drive and File Checks are checks designed for the Windows operating system. When performing one of those checks on another computer than the one running ServersCheck, then those checks will fail. By design, the local system account has no access to those remote computers and will cause ServersCheck to fail.

There is a way to allow the ServersCheck service to have access to the network. To achieve this you need to change the account under which the service runs. The image below shows how to do it. The changes only take effect after stopping and starting the service again.

The account you assign for the service has to be an account have sufficient access rights on the remote computer (to perform WMI calls, retrieve Performance Counter information etc...). Important note: the account also needs to have local admin rights or otherwise ServersCheck will fail.

If necessary, you may have to assign the "Log on as a service" right to the login in the Local Security Policy's SecuritySettings/LocalPolicies/UserRightsAssignment option.