General requirements for Windows Remote Server connection
It is important to verify the following on the target servers:
* Remote Registry Service is enabled on the target server. (This is very important)
* RPC Service is enabled on the target server.
* Server Service is enabled on the target server.
* TCP NetBIOS Helper Service is enabled on the target server.
* Performance Counter DLL Host
* Performance Logs & Alerts
* Remote Procedure Call (RPC)
* Secondary Logon
* File and Print Sharing is enabled on the Remote.
* NetBIOS over TCP-IP is enabled on the Remote.
* Ports 137-139 and 445 are open between the SiteScope server and the Remote.
* The UAC is disabled or managed in the registry (See below)
* Prerequisites (for Windows 10 Pro Windows Server 2008, 2012 remote servers): SiteScope supports monitoring on Microsoft Windows Server 2008 remote servers with User Account Control (UAC) enabled or disabled. Where UAC is enabled, you must disable the UAC remote restrictions as follows:
? Click Start, click Run, type regedit, and then press ENTER.
? Locate and then click the following registry subkey:
? If the LocalAccountTokenFilterPolicy registry entry does not exist, follow these steps:
§ On the Edit menu, select New > DWORD Value.
§ Type LocalAccountTokenFilterPolicy, and then press ENTER.
§ Right-click LocalAccountTokenFilterPolicy, and then click Modify.
§ In the Value data box, type 1, and then click OK.
§ Exit Registry Editor.
* User Permissions: Should be a member of the following groups (Not all are required)
? Backup Operations
? Performance Log Users
? Performance Monitor Users
? Remote Management Users
First, a brief overview of how SiteScope connects to remote Windows machines.
* Remote Windows servers are accessed via the Windows Perfmon API.
* The program SiteScope uses to access the Windows Perfmon API is called Perfex.exe
* Since data is pulled from a windows API, remote Windows servers canonlybe accessed by SiteScope installed on Windows.Unix and Linuxservers simply do not have access to Windows APIs.
* The username and password information supplied in the Remote NT setup page will be passed to the remote Windows server via the Remote Registry service for authentication. The user being specified should have administrator level access to the remote server in order to access the appropriate .dll's and pull data.
Use Perfex to validate connection
Diagnosing Perfex Issue (SiteScope Perfmon Connection)
Run the following command from the directory indicated:
C:SiteScopetools>perfex \[Server Name or IP -u [SystemUserId] -p [Password] =238
perfex \Earth.router.home -u EarthJester -p Jester =238
A successful connection will report the following: If not, then google the error message.
Successful local logon as EarthTester
Connected to \Earth as EarthTester
Any error messages returned from Perfex are Windows errors. To check what it means, windows will have to be queried. To do that, from the command line run the command:
C:>net helpmsg xx
Substitute the error number returned from Perfex for the xx above.
For more information of the Perfex command and what options it has, seeDocument ID 16479 - How to Solve Monitoring Problems with Perfex.
Instructions for Enabling NetBios over TCP/IP
* From the Control Panel, open theNetwork