|
2. Installing and Running the iServer
You can obtain the installation program for the iServer from the Tridia FTP site or the iTivity Product CD. In order to use the iServer, it must be licensed for the number of connections you will run. Refer to Section 2.4, Licensing the iServer on Windows, or Section 2.10, Licensing the iServer on Linux for more information. 2.1 Windows
System Requirements
The minimum platform for the iServer includes the following. Hardware· 500 MHz x86 CPU · 64MB RAM · At least 10MB free disk space SoftwareAny of the following: · Windows NT Server with Service Pack 6 or higher · Windows NT Workstation with Service Pack 6 or higher · Windows 2000 Workstation · Windows 2000 Server · Windows XP Professional · Windows XP Server · Windows 2003 Server 2.2 Resource Requirements
While the iServer is running, it uses the following resources. Baseline Requirements· 14 MB Incremental RequirementsThe following are additional incremental resource requirements for the iServer. Note: An agent registration occurs each time a computer running one of the iTivity agents connects to the iServer. View and remote control sessions occur when an iTivity iManager opens a session with one of those connected agents. · 250 KB per agent registration · 350 KB per remote view connection · 150 KB per remote control session 2.3 Installing the iServer on Windows
You can obtain the iServer installation program via FTP download or on CD from Tridia. Contact Tridia for more information. Note: You can automate installation on Windows. See the Appendix in this guide. After installing the iServer component, it is recommended
that you review the Readme file for the most current product information. You
will find this file located at C:\Program Files\iTivity\README.txt. 1. Download the distribution EXE file the Tridia FTP site. After saving this file to disk, open the file. Or, insert the Tridia Product CD into your CD-ROM drive. The Autorun feature starts the installation program. The following Welcome dialog is displayed:
2. Click Next. The License Agreement page is displayed.
3. Press the Page Down key to view the entire agreement. Then click Yes to indicate your acceptance. The following dialog is displayed.
4. Click the Browse button to change the Destination Folder if desired. Otherwise, click Next to continue. The Setup Type dialog is displayed.
5. Highlight the iTivity iServer and click Next. Note: This option automatically installs both the iServer and the Support Module, as described below. If you want to choose which modules to install, highlight the Custom option and use the next dialog to select the modules.
Note: One reason for choosing Custom install is if you are want to use the Live Support Agent without the Chat feature. Chat support is included by default, but it increases the file size and download time for one-click install of the Live Support Agent. After selecting the modules to install, click Next. 6. The Select Program Folder dialog is displayed.
7. Change the Folder if desired. Click Next. The following dialog is displayed.
8. Click Next to begin copying files. After copying files, the program displays the following dialog:
9. If you want to install the files for downloading the Support Module to your web server, click Yes and continue with Step 10. Otherwise, click No and continue with Step 11. The following dialog is displayed, for you to specify the folder location on your web server.
10. Specify the path to the correct folder on your web server and click OK. The files are copied to the web server location. The following dialog is displayed when the process is complete.
Click OK to close the dialog. 11. The Authentication Method dialog is displayed:
These choices define how a user of iTivity iManager must authenticate before being allowed to open a connection to the iServer. Choose one of the following authentication methods, then click Next to continue. s NTLM (Microsoft Authentication): iTivity iManager authenticates the username and password against a Microsoft Domain or local database, eliminating the need for a separate local password on every system. NTLM authentication can be used both in an NT domain environment as well as on a standalone Windows NT, 2000 or XP system. Note: If you choose the NTLM option, the installation creates an empty Windows User Group called iTivity Users. After the installation is complete, an administrator must add users to this group to enable them to view the computer through iTivity Manger. s
LDAP/NDS: iTivity iManager authenticates against
a server running either the Lightweight Directory Access Protocol (LDAP) or
Novell Directory Services (NDS). s
Simple Password: Each agent system has its own
password that must be entered by the remote user trying to view. Use this
option if you want iTivity iManager authentication to use separate passwords
from Microsoft (NTLM) authentication. s
No Authentication Required: No login is
required. This option is strongly discouraged. 12. This step depends on which method you chose in Step 11. A. If you chose the NTLM option in Step 11, you are asked if the computer is running Microsoft Terminal Server.
Click Yes or No to continue. The Installation program then asks if you want to use Bi-level Authentication Security, which is recommended.
Click Yes to choose Bi-level Authentication or No to use Standard Authentication. B. If you chose LDAP/NDS in Step 11 you are asked to enter configuration information for the LDAP/NDS server to be used for authentication.
See the topic titled Security in Section 4.1.4.4, Options for a description of the LDAP configuration data. Enter the information and click Next to continue. C. If you choose the Simple Password option in Step 11, you are prompted to enter the password
Enter and confirm the password, then click OK. D. If you chose No Authentication Required in Step 11, no action is required. Go to Step 13. 13. The following dialog is displayed, allowing you to change the iServer registration port if desired.
Change the default port if desired. Click Next. 14. The following prompt appears, asking if you want to enable the secure dial feature.
The secure dial feature enables you to establish encrypted dial-up connections to Linux/UNIX servers through the iServer. For information on configuring your Linux or UNIX server to secure dial, contact Tridia technical support. Click Yes or No (the default). Installation is now complete. 2.4 Licensing the iServer on Windows
After installing, you must license the iServer to make it operable. As explained in the Welcome to iTivity section of this guide, there are two types of connections: interactive and always-on. The license you purchase determines the number of interactive and always-on connections that your iServer supports. 2.4.1 Obtaining the License KeyWhen you purchase your license, Tridia provides a license key. The license key is a series of numbers with hyphens: Example: 533-0025-32-112012527 2.4.2 Creating the License FileAfter obtaining your license key, follow these steps to license the iServer: 1. Select Start > Programs > iTivity > Tridia Licensing > Create or Locate Tridia License File. The Create New Tridia Software License File dialog is displayed.
2. Click Open to create the file with the default name and location. The license file is created and opened in Notepad.
3. Below the comment area, enter your license key Example: 533-0025-32-112012527 4. Save the file and exit Notepad. The iServer is now licensed. 2.4.3 Editing the License FileYou can use the Start > Programs > iTivity > Tridia Licensing > Edit Tridia License File option to add a new license key to a license file that you previously created. This option is typically used to add licenses to allow the iServer to support additional connections. 2.5 iServer Windows Start Menu Options
After the iServer is installed, the following Window Start menu options are available.
2.5.1 Administrative ToolsChoosing Start > Programs > iTivity > Administrative Tools opens a flyout menu with additional options.
2.5.1.1 Configure Automatic iTivity iServer Start
Choose this option to set up the iServer to start automatically each time the system starts. 2.5.1.2 Configure Manual iTivity iServer Start
Choose this option to set up the iServer to start on command. You can then start the iServer by choosing Start > Programs > iTivity > Start iTivity iServer. 2.5.1.3 Reload iTivity iServer Changes
Choose this option to reload iServer operating parameters without having to stop and restart the iServer. This allows you to change iServer settings without interrupting live connections. For example, if a new license key is added to expand the number of licensed users, an administrator can use this option to load the new license data without interfering with current users. 2.5.1.4 Remove iTivity iServer Configure
Choose this option to temporarily disable the iServer software. This option causes the iServer Windows services to be removed from the Services database. To re-enable the iServer, choose Start > Programs > iTivity > Administrative Tools > Configure Automatic iTivity iServer Start or Start > Programs > iTivity > Administrative Tools > Configure Manual iTivity iServer Start. 2.5.1.5 Set iServer Simple Password
You can use this option to change the password used by a remote user of iTivity iManager to connect to this iServer. This password applies only if Simple Password was chosen as the Authentication Method when the iServer was installed. If another Authentication Method was chosen, any entry in this dialog is ignored. Enter the password twice, then click OK to reset the password.
2.5.2 DocumentationChoose Start > Programs > iTivity > Documentation to display the iTivity online Help. 2.5.3 Tridia LicensingUse this option to create or edit your license file for the iServer. See Section 2.4, Licensing the iServer on Windows, for instructions. 2.5.4 About iTivity iServerChoose Start > Programs > iTivity > About iTivity iServer to display the About dialog containing version information.
2.5.5 Start iTivity iServerChoose Start > Programs > iTivity > Start iTivity iServer to start the iServer software. You need to use this option only if the iServer is not configured to start on system startup. 2.5.6 Stop iTivity iServerYou can use the Start > Programs > iTivity > Stop iTivity iServer option to stop the iServer whenever it is running. Caution: All current connections to the iServer are immediately lost. 2.6 iServer Windows System Tray Menu
When the iServer is started, the following icon is displayed in the Windows System tray:
Right-click on this icon to display the System Tray menu.
2.6.1 Show Active SessionsThis option displays a dialog showing active remote control sessions currently connected to the iServer. You can use the buttons to select and close any or all of the sessions. When NTLM authentication is used, the NTLM user name is shown for each session. The name of the iServer is shown in the remote host column.
2.6.2 Show Certificate FingerprintThe iServer automatically generates a local default 1024-bit RSA encryption certificate the first time it runs. This unique certificate is presented to the iTivity iManager to ensure encryption of all session data transmitted between the Admin Module and the iManager. Selecting the Show Certificate Fingerprint option displays the Certificate Fingerprint.
The first time the iTivity iManager attempts to connect to this iServer, the user is asked to confirm the certificate fingerprint. After the first connection, the remote machine retains the fingerprint in its cache for the next viewing session. Note: iTivity also supports commercial SSL digital certificates purchased from Verisign or other Certificate Authorities. Contact Tridia if you need to configure your iServer to us a commercial digital certificate. 2.6.3 About iTivity iServerChoose this option to display the About dialog containing version information.
2.6.4 Stop iTivity iServerYou can click this option to immediately stop the iServer. Caution: All current connections to the iServer are immediately lost. 2.7 Linux System Requirements
The Linux version of iServer runs of the following platform. Software· Red Hat 9.0 or Red Hat Enterprise or later Hardware· 60 MB minimum disk space · 8MB RAM baseline, plus 336 KB per iServer connection · 300 Mhz minimum CPU Note: Active remote control (viewing) sessions use approx. 20 to 100 Mhz each depending on bandwidth and number of screen updates. 2.8 Installing
the iServer on Linux
Note: For information on configuring the iServer after installation, see Section 2.9, Configuring the iServer on Linux. Please follow the instructions provided under your chosen method for obtaining the IServer distribution (via download or CD), then skip to Continuing the Installation for further installation instructions. Download1. Contact Tridia for the URL and password for downloading the IServer Linux distribution. The filename is iserverversion.tar, where version is the particular version number. Example: iserver4.2.00.tar Note: Many popular Window's based ZIP file utilities do not properly extract the contents of our distribution file. Please do not attempt to use them with any of the distribution files. 2. Place the downloaded file in your home directory on the Linux server where you want to install the iServer. Example: /home/username/ 3. Skip to Continuing Your Installation. VIA CDNote: Reserved for a future release. CONTINUING YOUR INSTALLATION1. Logon as the root user or issue the su command. 2. Change to the /tmp directory. cd/tmp
[Enter] 3. To verify the presence of the distribution file, list the directory contents of your home directory: ls –l
/home/username/*.tar [Enter] 4. Extract the distribution (*.tar) file: tar
xvf /home/username/<filename> Several files are extracted into
the /tmp folder. One of these is the install script. Note: At this point you can remove the distribution file by moving
it to a different directory or using the rm command. 5. Run the install-iserver script. ./install-iserver A Welcome screen is displayed:
6. Type y to proceed. The program checks for a prior version of the iServer and preserves the license information if it exists.
Press Enter to continue. If a prior version exists, the files are removed.
7. Press Enter again to continue. The following screen is displayed, allowing you to change the Registration Port if needed.
8. Change the port if desired. Otherwise just press Enter. The Host Description screen is displayed.
9. Enter a Description to be used to identify this iServer in iTivity iManager. Then press Enter. The iServer Install Directory Screen is displayed.
10. Press Enter to accept the default directory, or type a different directory and then press Enter. If the specified directory does not already exist, you are prompted to confirm creating it. Type Y to confirm. The program extracts the iServer files. You are then prompted to specify whether you want to install the Support Module files on your web server.
For more information on the Support Module, see Section 5.2, Installing the Support Module. 11. If you want to copy the Support Module files, type y and continue with Step 12. Otherwise, type n and continue with Step 13. 12. Enter the directory where you want to copy the Support Module files and press Enter. If the directory does not already exist, type Y to confirm creating it.
The Support Module files are installed and a message is displayed when the process is complete. Press Enter to continue. 13. The installation continues and a number of status messages are displayed. Press Enter to continue. You are prompted to specify whether or not to start the iServer listening daemon at system startup. The daemon must be running for the iServer to accept connections. It can also be started by issuing the start_iServer command.
Type y to start the daemon at boot time or n to cancel this option. 14. The program prompts you to specify whether or not to remove temporary installation files. Type y to confirm or n to cancel. If you typed y, the files are removed. Press Enter to continue.
Installation is now complete.
2.9 Configuring the iServer on Linux
2.9.1 Editing the iServer.conf FileFor the Linux version of iServer, all configuration settings are controlled by an ASCII text file called iServer.conf, which is placed in the installation directory on the Linux computer. You can change the settings by
opening the file in any text editor. The following table describes the settings
in the file.
|
