Administration > Monitor Administration > SiteScope Data Collector Configuration > Managing SiteScope > SiteScope Preferences > Windows Remote Preferences > Monitoring Remote Windows Servers > Remote Windows Server Connection Profiles
Remote Windows Server Connection Profiles
Monitoring of remote Windows server data requires authenticated access to the remote server. A Windows Server connection profile provides the necessary address and login credentials for SiteScope to login to a remote server and to access the Windows performance registry on that remote machine. To be able to use this method you will also need to create or modify a user account on the remote server that corresponds with the connection method and login permissions used in the SiteScope connection profile for that server. This applies for monitoring servers running Windows operating systems from SiteScope running on Windows and when using an SSH connection from SiteScope running on UNIX.
Setting Domain Privileges for SiteScope Monitoring
SiteScope for Windows will automatically populate a list of servers that are visible in the local domain for selection for the Choose Server page for monitor types that require that a server be specified. SiteScope running on Windows may be able to use this list to monitor remote Windows servers without having to create individual connection profiles for each server. There are three options that can be used to enable monitoring in this environment:
- Set the SiteScope service to run as a user in the Domain Admin group - By default SiteScope is installed to run as a Local System account. You can set the SiteScope Service to log on as a user with domain administration privileges. This will give SiteScope access to monitor server data within the domain.
- Add the server where SiteScope is running to the Domain Admin group in ActiveDirectory (for Windows 2000 or later). With this option, the SiteScope Service is set to log on as a Local System account but the machine where SiteScope is running is added to a group having domain administration privileges.
- Edit the registry access permissions for all machines in the domain to allow non-admin access. See the Microsoft Knowledge Base Article - 158438 for details on Enabling Non-Admin Users to Remotely Monitor with PERFMON. This option requires changes to the registry on each remote machine that you want to monitor. This means that while the list of servers in the domain will include all machine in the domain, only those where the registry has been modified can be monitored without use of a connection profile.
After you provide the necessary domain administration privileges or define a Windows Server connection profile, you can create monitors to watch the resources and performance counters for that server. Multiple monitors can use the same connection profile.
Adding a New Windows Server Profile
Use the following steps to create a new Windows Server Profile.
To create a new Windows Server Profile:
- Expand the SiteScope container element for which you want to configure the Windows Server Profile and click on the Preferences container for that SiteScope. The content panel displays the Preferences container contents.
- Click on the Windows Remote Preferences on the left menu tree or under the applicable section in the content panel. A list of current Windows Server Profile is displayed.
- Click the New Windows Remote Preferences button near the top of the content panel. Alternately, you can right-click the container in the left Enterprise menu to display the container action menu and select New Windows Remote Preferences. The New Windows Server Profile page is displayed.
- Complete the items in the Main Settings section as described below. If necessary, complete the items in the Advanced Settings and other sections as described below.
- When the required settings are defined, click the Add button to create the Windows Server Profile.
After defining the Windows Remote Preferences definition for SiteScope, you can have SiteScope test the settings by clicking on the Test link for the applicable server in the Remote NT Server table.
| Copyright 2006 Mercury Interactive Corporation |