Home  Administration > Monitor Administration > SiteScope Data Collector Configuration > Managing SiteScope > SiteScope Preferences > Windows Remote Preferences > Windows Server Profile Settings



Windows Server Profile Settings

The following describes the settings used for Windows Server Profiles.

Main Settings

You use the Main Settings section to enter information that defines the Windows Server Profile. Complete the Main Settings section for the Windows Server Profile as described below.

Host

The IP address or UNC style name of the NT server you wish to monitor. An IP hostname will also work provided that the SiteScope server has a way to resolve this common name into an IP address (for example, by the use of a hosts file, DNS, or WINS/DNS integration). To use the same login credentials to configure multiple servers at the same time, enter the server addresses separated by commas. For example, if you are using NetBIOS to connect to other servers in an NT domain, you can enter a comma-separated string of server addresses such as: \\server1,\\server2,\\server3,\\server4. When you complete the other required entries on the form and click Add Remote NT Server, SiteScope creates a new remote connection profile for each server address in the list.

Note: When adding multiple servers in a single operation, SiteScope does not automatically test connectivity with each server. You can use the Test links in the Remote NT Server Table to test connectivity after the profiles have been added.

Login

The login for the remote server. If the server is within the same domain as the SiteScope machine, include the domain name in front of the user login name. For example: <domainname>\<user>. If you are using a local machine login account for machines within or outside the domain, include the machine name in front of the user login name. For example: <machinename>\<user>.

Password

The password for the remote server or the passphrase for the SSH key file. When using SSH authentication with public/private key based authentication enter the passphrase for the identity file here.

Name

A name by which the remote machine should be known. This name will appear in the Server drop-down list of monitors that can use this connection profile.

Trace

Check this box to have trace messages to and from the subject server recorded to the SiteScope RunMonitor.log file.

Method

SiteScope can use one of two connection types for monitoring Windows server resources. These are:

Remote Machine Encoding

If the remote server is running an operating system version that uses a different character encoding than the server on which SiteScope is running, enter the encoding to use for the remote server. This will enable SiteScope to display encoded content correctly. By default, SiteScope uses Cp1252 encoding. Examples of other encodings are Cp1251, Cp1256, Shift_JIS and EUC_JP.

Advanced Settings

You use the Advanced Settings section to customize the Windows Server Profile. Complete the entries as needed and click the Add or OK button to save the settings.

Description

Enter an optional description text to further describe this Windows Server Profile. For example, you may enter some text describing the purpose or conditions relating to the use of this Windows Server Profile.

SSH Connection Method

The SSH client to use for this connection. The currently supported clients are:

Client
Description
Internal Java Libraries
Connect using the Java SSH client integrated with SiteScope.
Plink/External SSH Client
Connect using an external SSH client. On NT, SiteScope ships with Plink on UNIX or Linux SiteScope will use an installed client such as OpenSSH.

SSH Port Number

Enter the port that the remote SSH server is listening on.

Disable Connection Caching

Check this option to turn off connection caching for this remote. By default SiteScope caches open connections.

Connection Limit

This setting controls the number of open connections that SiteScope will allow for this remote. If you have a large number of monitors configured to use this connection then set this number high enough to relieve the potential bottleneck.

Note: This setting does not effect the running of tests for a remote, tests will always create a new connection.

SSH Authentication Method

The authentication method to use for SSH connections. The currently supported methods are:

Authentication
Description
Password
Authenticate using a password.
Key File
Authenticate using public/private key authentication. When this option is selected SiteScope uses the private key in the file SiteScope/groups/identity to authenticate. The corresponding public key must be listed in the authorized_keys file on the remote host. See the document on Secure Shell in the Advanced SiteScope Topics section for more information on SSH requirements.

Key File for SSH connections

Select the file that contains the private key for this connection. The default key file is SiteScope\groups\identity. This setting only applies when the authentication method is Key File .

SSH Version 2

Check this option to force SiteScope to use SSH protocol version 2 only. This option only applies when using the integrated Java Client in SiteScope. See the section on Configuring SSH Using an External Client for information on configuring an external SSH client to use SSH2 protocol.

Custom Commandline

Enter a custom commandline for a remote using the External Client. This option can be used when needing to pass specific options to the external client being executed. Valid substitution variable are




Copyright 2006 Mercury Interactive Corporation