How to monitor a Process/Service/Performance Counter on a Remote/Different Computer

From WebWatchBotWiki
Jump to: navigation, search


WebWatchBot monitors processes and services on a remote computer by querying performance counters. Monitoring a performance counter on a remote computer typically requires security settings to be configured properly. If the security is not configured properly, an error message may be displayed, stating that a process/service/performance counter could not be queried


The computer where WebWatchBot is installed, and the computer being monitored must be on the same subnet of the network. To test connectivity, one must be able to map a network drive between the two.


Step 1: Remote Registry Service

Performance counters require access to the system registry. If monitoring performance counters on a non-local machine, the [remote registry service] must be running on the remote machine.

Step 2: Set Registry Permissions

You must have at least Read access to the following registry keys on the remote computer:

  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib

Step 3: Set User Account Permissions

If the systemroot is on an NTFS partition, you must have at least Read access to the following two files:

  • %SystemRoot%\System32\Perfc009.dat
  • %SystemRoot%\System32\Perfh009.dat
If your computers are part of a domain:

Ensure that the user account for the WebWatchBot service (WWBserver) on the monitoring computer has at least read permission to the two above files. Ensure that the user account using the WebWatchBot Manager Application (WWBGui) has at least read permission to the two above files.

The Windows user account for the WebWatchBot service (WWBServer) should be set to a user account that has access to both machines. NOTE: Use of a domain administrator account does not guarantee access to both computers and required permissions for both files. If the domain administrator account fails to query a service on the remote computer, try a different user account.

If your computers are part of a workgroup:

The most straightforward method of configuring security is to create an identical local user account on both computers and configure the WebWatchBot service to log in with this user account. This allows WebWatchBot to connect to the remote computer without any type of authentication.

  1. On the WebWatchBot server, create a local (non-domain/non-Active Directory) user account.
  2. On the remote computer, create a local (non-domain/non-Active Directory) user account with the same username and password. NOTE: You must log into that user account on the remote machine in order for permissions and access to be set up properly by Windows.
  3. Change the user account that the WebWatchBot service uses to log on with.To change the user account of the WebWatchBot Service:
    1. For version 5.0.4 and older: Delete log files and saved output (This is necessary to ensure that the logs and output do not retain permissions from the old user account):
      1. Open WebWatchBot Manager
      2. Select from the menu: Help -> ExclamationSoft Support -> View Data Folder
      3. When the Windows Explorer/My Computer window opens, close WebWatchBot Manager.
      4. Select all of the numbered folders and delete. This will only delete log files and last saved output and your data will remain intact.
      5. Close the window
    2. Start (Windows Start Button)
    3. Control Panel
    4. Administrative Tools
    5. Services
    6. Find "WWBServer" (the WebWatchBot Service name)
    7. Stop the service
    8. Right-click on WWBServer and select "Properties"
    9. Click the "Log on" tab.
    10. Select the "This account tab"
    11. Enter the user account and password. You should enter a user account that has high enough privilege to create, modify, read and write to files on the computer, send email, and access network resources.
    12. Click OK
    13. Start WebWatchBot Manager.
    14. When prompted, start the WebWatchBot service.

More information:

"Unable to Connect to Machine" Error Message When You Try to View Remote Counters -