Windows-based servers provide access to their performance parameters via the Performance Data Helper (PDH) component. This component is part of the Windows Management Infrastructure (WMI) and is available in every Windows operating system (since Windows NT 4.0).
Depending on the provider you want to use to get performance data, the following requirements must be met:
SmartBear Provider and Standard CountersSmartBear Provider and Standard Counters
In order for LoadComplete to get SmartBear provider counters or standard counters from your tested web server, the server must have LoadComplete Remote Agent installed and running. You can download the Remote Agent installation pack from our web site. To learn how to install the agent, see Installing Remote Agent.
Standard Counters and Windows Performance Monitor
-
If the LoadComplete workstation and the tested server belong to different domains, there must be a two-way trust relationship between the workstation's and the server's domains.
If the tested server does not belong to any domain (for instance, if it is located in the cloud), LoadComplete will not be able to get the server's metrics.
-
The user account under which LoadComplete is running must be a member of one of the following user groups on the remote machine:
-
Performance Monitor Users
-
Performance Log Users
-
Administrators
-
-
The Remote Registry Windows service must be enabled and started on the monitored server.
The service is disabled by default on Windows 7 and later operating systems.
This requirement is optional, if the server resides on the same computer where LoadComplete is running (that is, if you monitor the localhost server).
-
The File and Printer Sharing for Microsoft Networks service must be installed and enabled on the remote server to be monitored. If the server resides on the same computer where LoadComplete is running (that is, if the localhost server is being monitored), this requirement is not obligatory.
-
The Server Windows service must be enabled and started on the remote machine to be monitored. If the server resides on the same computer where LoadComplete is running (that is, if the localhost server is being monitored), this requirement is not obligatory.
-
If you use a firewall, make sure that it does not block TCP ports 139 and 445 (they are required by the File and Printer Sharing for Microsoft Networks service). If the server resides on the same computer where LoadComplete is running (that is, if the localhost server is being monitored), this requirement is not obligatory.
-
The user account, under which LoadComplete is running, or a user group, to which the user belongs, must have read permission for the following registry keys on the monitored server:
- HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT \CurrentVersion\Perflib
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg
-
The HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT \CurrentVersion\Perflib\009 registry key on the remote machine to be monitored must contain the Counter value holding the list of available performance counters.
-
The following files must exist on the monitored server and the user account, under which LoadComplete is running, or a user group, to which the user belongs, must have permission for these files on the monitored server:
- <Windows>\System32\Perfc009.dat
- <Windows>\System32\Perfh009.dat
-
If the monitored server resides on the same computer, where LoadComplete is running (that is, if you monitor the localhost server), and the UAC (User Account Control) is enabled on that computer, launch LoadComplete with administrator privileges. See Using LoadComplete With Administrator Privileges for instructions.