Tivoli Endpoint Manager for Remote Control Version 8 Release 2. User s Guide

(1)

Tivoli Endpoint Manager for Remote Control

Version 8 Release 2

User’s Guide

(2)

(3)

Tivoli Endpoint Manager for Remote Control

Version 8 Release 2

User’s Guide

(4)

Note

Before using this information and the product it supports, read the information in “Notices” on page 89

This edition applies to version 8, release 2, modification 0 of IBM Tivoli Endpoint Manager for Remote Control and to all subsequent releases and modifications until otherwise indicated in new editions.

(5)

About this publication

What's new

This section explains what has changed in this publication since the integration of TRC 5.1.2 with TEM 8.1.

v A server component has been included as part of Tivoli Endpoint Manager for Remote Control. For an overview of this component see Chapter 1, “Overview,”

on page 1 and for server requirements details see Chapter 2, “System requirements,” on page 3. For deployment details see “Installing the server component.” on page 9.

v To help with determining which type of Tivoli Endpoint Manager for Remote Control Server installation would be best suited to your environment a set of guidelines has been provided. See Chapter 3, “Server environment guidelines,”

on page 5.

v You can deploy command line tools. These tools contain two utilities that you can use to start a remote control session with a target or run commands on a target system without target user interaction. For details see “Deploying from the console” on page 27.

v Gateway support can be installed and configured to establish connections between targets, controllers and severs on different networks. See “Deploying from the console” on page 27.

v You can now install the latest enhancements and fixes that have been applied to the Tivoli Endpoint Manager for Remote Control target and controller

components by using the Updates node in the Tivoli Endpoint Manager console to update your target and controller component configurations to a newer version. For more details see “Updating Tivoli Endpoint Manager for Remote Control components” on page 45.

v Establishing a remote control session section has been updated to include sessions initiated from the Tivoli Endpoint Manager for Remote Control server and also updates to establishing peer to peer sessions.

– For server initiated remote control sessions see “Starting a server initiated remote control session” on page 53.

– For updated peer to peer session details see “Starting a peer to peer session”

on page 50.

v You can create server installation configurations, using the Tivoli Endpoint Manager for Remote Control Server Installer Wizard that you can use to install the Tivoli Endpoint Manager for Remote Control server component . For more details see “Creating Tivoli Endpoint Manager for Remote Control server installation tasks” on page 56.

v The Tivoli Endpoint Manager for Remote Control Target Wizard has been updated to include additional target configuration properties. For more details see “Creating Tivoli Endpoint Manager for Remote Control target configuration tasks” on page 63.

v The Analyses section has been updated to include the analyses for gathering the new target installation, security, user, session and performance options. For more details see “Analyses” on page 77.

(8)

(9)

Chapter 1. Overview

The Tivoli Endpoint Manager for Remote Control site masthead contains information about Tivoli Endpoint Manager for Remote Control content that performs certain tasks and analyses within your deployment. You must be subscribed to the Tivoli^®Remote Control "site" in order to collect data from the client. This data will be utilized for reporting and analysis.

Using the Tivoli Endpoint Manager for Remote Control solution you can deploy and configure the components required for establishing remote control sessions with workstations and servers across your enterprise . This Users's Guide will describe some of the primary components of Tivoli Endpoint Manager for Remote Control, how to install and configure these from the TEM console and their use in establishing a remote control session. See the IBM Tivoli Remote Control User's Guide for details of the functions available within a remote control session.

There are three infrastructure components available in your Tivoli Endpoint Manager for Remote Control solution whose features are listed below.

Server

v User Account Management . v Target Management.

v Policy engine for users and target endpoints.

v Centralised depot for session information relevant for audit purposes.

v Authentication broker for each session.

v Web interface for administrators and controller users.

Controller

v Participates in a remote control session.

v Records audit information which can be stored locally and in the Tivoli Endpoint Manager for Remote Control server, if running.

Target

v Resides on the endpoint (client) to be controlled.

v Presents a Graphical User Interface to the endpoint user.

v Controls the policies set for the session.

v Records audit information locally.

v Additionally if you have the Tivoli Endpoint Manager for Remote Control server component

– Registers and maintains current state information on the Tivoli Endpoint Manager for Remote Control server about the endpoint.

– Receives connection requests and can authenticate them against the infrastructure server if the Tivoli Endpoint Manager for Remote Control server is running.

– Stores audit information on the server.

(10)

(11)

Chapter 2. System requirements

Server requirements

The computer on which you install the Tivoli Endpoint Manager for Remote Control server must have the minimum following items or capability:

1. At least a 2GHz Intel or AMD processor.

2. A minimum of 1Gb of memory.

3. A minimum of 2Gb of storage or hard drive space to install, and an average of 2MB per client in the database.

4. A minimum screen resolution of 800 x 600 pixels is required when performing an automated server install.

5. Adequate space for storing session video recordings. Recordings are stored on the hard drive and their size can vary depending on the duration and screen activity of the session. On average a 5 minutes session (8 bits mode) would use about 2MB of space.

6. A network card that supports TCP/IP.

7. IE 6, 7, 8 and 9 (for local console administration ) or Firefox 3.6 to 7.0.1.

8. OS for server is Windows Servers, Linux RHEL 4/5/6, SUSE (SLES) 10, 11.

9. When using Oracle as the database you must use the 10.2g JDBC 4 drivers for Oracle. Alternatively, if you are using the Oracle 11g drivers the following property must be set in the trc.properties file, oracle.increment.keys.off=1 . When this is done you will need to restart the server service.

Platform Support

The following platforms are supported when using the installation tasks 1. Windows 2000 Server and Windows 2000 Advanced Server.

2. Windows Server 2003 Standard R2 (32 and 64 bit) and Windows Server 2003 Enterprise (32 and 64 bit)

3. Windows 2008 Server (R1) Standard / Enterprise (32 and 64 bit ) and (R2) Standard / Enterprise / Datacenter (32 and 64 bit ) .

4. Red Hat Enterprise Linux 4.0, 5.0 and 6.0 for Intel x86 (32 bit only) and 5.0 and 6.0 for AMD/eMT 64 bit.

5. SUSE Linux Enterprise Server 10 and 11 for Intel x86 and AMD/eMT 64 bit.

Controller requirements

The Controller is a Java^™based application that can run on any platform with the following prerequisites:

v Java Run Time environment: Sun 1.5-1.6 or IBM^®1.4, 1.5, 1.6.

Note: The Sun Java JRE is not supported in FIPS mode, you should use the IBM Java JRE in this mode.

v Web Browser: either Microsoft Internet Explorer 6, 7, 8, 9 or Mozilla Firefox 3.6 to 7.0.1.

(12)

Target requirements

The computer on which you install the Tivoli Endpoint Manager for Remote Control target must have the minimum following items or specification:

1. At least a 166MHz Intel or AMD processor.

2. A minimum of 64Mb of memory.

3. A minimum of 50Mb hard disk space.

The following Platforms are supported

1. Windows 2000 Pro, Server, Advanced Server.

2. Windows XP Pro (32 bits), (64 bits).

3. Windows Server 2003 Standard R2 (32 bit), Standard R2 (64 bit), Enterprise R2 (32 bit), Enterprise R2 (64 bit).

4. Windows Server 2003 R2 Datacenter Edition x86-32 , x86-64.

5. Windows Vista (32 bit), (64 bit).

6. Windows Vista Enterprise x86-32 and x86-32 with FDCC

7. Windows 2008 Server (Standard , Enterprise and Datacenter editions).

8. Windows 7 Enterprise x86 ( 32 and 64 bit) and 32 bit with FDCC.

9. RHEL 4.0, 5.0 and 6.0 for Intel x86, 5.0 and 6.0 for AMD/eMT 64bit . 10. SLES 9 / 10 for Intel x86, AMD/eMT 64bit.

11. SLED 10, 11 for Intel x86, AMD/eMT 64bit . 12. SUSE (SLES) 10/11 - x86-32 , x86-64

Gateway requirements

The computer on which you install the Tivoli Endpoint Manager for Remote Control gateway must have the minimum following items or specification:

1. At least a 1GHz Intel^® or AMD processor.

2. A minimum of 512Mb of memory.

3. A minimum of 50Mb hard disk space.

The following Platforms are supported

1. Windows Server 2003 Standard R2 (32 bit), Standard R2 (64 bit), Enterprise R2 (32 bit), Enterprise R2 (64 bit).

2. Windows Server 2003 R2 Datacenter Edition x86-32 , x86-64.

3. Windows 2008 Server (R1) Standard / Enterprise (32 and 64 bit ) and (R2) Standard / Enterprise / Datacenter (32 and 64 bit )

4. RHEL 4.0, 5.0 and 6.0 for Intel x86, 5.0 and 6.0 for AMD/eMT 64bit . 5. SLES 9 / 10 for Intel x86, AMD/eMT 64bit.

6. SUSE (SLES) 10/11 - x86-32 , x86-64

(13)

Chapter 3. Server environment guidelines

As well as determining the system requirements for installing the Tivoli Endpoint Manager for Remote Control components you should also determine which type of server installation is best for your environment. This section provides information which can be used as a guide when making this decision.

Table 1. Tivoli Endpoint Manager for Remote Control Server installation types Server

installation type Components installed

Install using the TEM console

Install using the installation files

1 embedded Websphere Application

Server, embedded Derby database

Yes Yes

2 embedded Websphere Application

Server, using an already installed DB2^®, MSSQL or Oracle database

Yes Yes

3 stand-alone Tivoli Endpoint

Manager for Remote Control Server accessing Websphere Application Server, using an already installed DB2, MSSQL or Oracle database

No Yes

Note: Server installation types 1 & 2 are only available when using Windows or Linux.

Small environment guidelines

For environments containing up to 5K targets you can use server installation types 1 or 2 in Table 1.

The following additional requirements should also be taken into consideration.

v Processors - 1 Quad core or 2 dual core processors - 2.40 Ghz (with supported OS)

v Memory - 4 GB RAM

v Storage see “Server requirements” on page 3.

v Heartbeat configuration

Table 2. heartbeat configuration properties: suggested values for a small environment property in trc.properties value

heartbeat.timeout 60

Note: Can be changed to 1440 ( 24 hours) instead of the default 60 (1hour) if there are performance issues. For example: when there is heavy usage of reports, especially with derby.

heartbeat.retry 10

heartbeat.delay 20

heartbeat.on.wake 0

heartbeat.on.user.change 1 heartbeat.on.change 0

(14)

Table 2. heartbeat configuration properties: suggested values for a small environment (continued)

property in trc.properties value

heartbeat.on.stop 0

Note: Installation type 1 can be suitable for demos or pilot projects and installation type 2 can give better performance, which may be preferred for production

systems in these environments.

Medium environment guidelines

For environments containing from 5K to 75K targets you can use server installation types 2 or 3 in Table 1 on page 5. In terms of performance, installation type 2 is suitable however with installation type 3 you can also use the admin capabilities of the installed WAS.

v Processors - 1 Quad core or 2 dual core processors - 2.40 Ghz Windows 2003 64 bit/32 bit

v Memory - 8 GB RAM

v Storage - RAID 5 - 6 HDD (DB2, Oracle or MS SQL 64 bit/ 32 bit) v Heartbeat configuration -

Table 3. heartbeat configuration properties: suggested values for a medium environment property in trc.properties value

Note: If there are specific group of machines where more regular updates are needed, a smaller heartbeat timeout setting can be applied as a group attribute for those specific groups of targets. See the chapter that explains how to create a target group in the IBM Tivoli Remote Control Administrator's Guidefor details of setting this attribute at group level.

heartbeat.retry 10

Note: In an environment containing target numbers nearer the top of the range, setting this value to 20 could help with performance.

heartbeat.delay 20

Note: In an environment containing target numbers nearer the top of the range, setting this value to 40 could help with performance.

heartbeat.on.wake 0

heartbeat.on.stop 0

Note: In this type of environment you should ensure that the target deployment is performed in stages to avoid overload in the server when the targets try to register with the server. The RegistrationDelay target property should be given a value that will distribute the target machine registration evenly through the staged deployment to avoid too many machines trying to register at the one time.

(15)

Large environment guidelines

For environments containing from 75K to 225K targets you can use server installation type 3 in Table 1 on page 5.

To host Websphere Application Server

v Processors - 2 Quad core processors - 2.40 Ghz (supported OS) v Memory - 16 GB RAM

v Storage - RAID 5 - 6 HDD v Heartbeat configuration -

Table 4. heartbeat configuration properties: suggested values for a large environment property in trc.properties value

Note: If there are specific group of machines where more regular updates are needed, a smaller heartbeat timeout setting can be applied as a group attribute for those specific groups of targets. See the chapter that explains how to create a target group in the IBM Tivoli Remote Control Administrator's Guidefor details of setting this attribute at group level.

heartbeat.retry 60

Note: In an environment containing target numbers nearer the top of the range, setting this to a higher value could help with performance.

heartbeat.delay 60

Note: In an environment containing target numbers nearer the top of the range, setting this to a higher value could help with performance.

heartbeat.on.wake 0

heartbeat.on.stop 0

v Optional: 2 network cards, one for target communications and one for database communications which could aid in performance tuning.

To host the database (DB2, Oracle or MS SQL supported)

v Processors - 4 Quad core processors - 2.40 Ghz Windows 2003 64 bit/32 bit v Memory - As recommended by DB supplier

v Storage - RAID 5 - 6 HDD 146 GB

Note: The database administrator should tune the database for performance as appropriate.

The following guidelines should also be taken into consideration when using large reports as some performance degradation can be experienced .

v Ensure that the All targets report is not the default home page report

v Ensure staged deployment of the targets to avoid overload in the server when they try to register

Chapter 3. Server environment guidelines 7

(16)

Note: The RegistrationDelay target property should be given a value that will distribute the target machine registration evenly through the staged deployment to avoid too many machines trying to register at the one time.

Note: If you have configured LDAP and LDAP synchronization is enabled, set a reasonable frequency for the synchronization, that is, every 24 hours particularly if your LDAP configuration is set up to import a large number of users and groups.

(17)

Chapter 4. Installing Tivoli Endpoint Manager for Remote Control

The Tivoli Endpoint Manager for Remote Control components can all be deployed by using the Tivoli Endpoint Manager console, using the installation DVD or by downloading the installation files from Passport Advantage^®.

Installing the server component.

When installing the Tivoli Endpoint Manager for Remote Control server component use the “Server requirements” on page 3 and Chapter 3, “Server environment guidelines,” on page 5 sections to determine which type of server installation is best suited for your environment. See the IBM Tivoli Remote Control Installation Guidefor more details of the types of installations that can be carried out. When you have determined your installation type you can use the following options to install the component.

When you have installed the server component use the IBM Tivoli Remote

Control User's Guide, IBM Tivoli Remote Control Administrator's Guide and the Tivoli Endpoint Manager for Remote Control Release Notes^®for details of the server features and functionality.

Installing from the TEM console

You can use the TEM console to install the Tivoli Endpoint Manager for Remote Control Server with embedded Websphere Application Server by creating server installation tasks. See “Creating Tivoli Endpoint Manager for Remote Control server installation tasks” on page 56.

Using the installation media

You can use the installation DVD to install the Tivoli Endpoint Manager for Remote Control Server in two ways

v installed with embedded Websphere Application Server - see “Installing a server with embedded components”

v installed on a stand-alone Websphere Application Server - see “Installing a stand-alone server” on page 10

Installing a server with embedded components

This type of server installation is only available when using Windows or Linux.

To install the Tivoli Endpoint Manager for Remote Control Server with embedded components complete the following steps :-

1. Insert the installation DVD.

Note: When mounting the Tivoli Endpoint Manager for Remote Control DVD on AIX^®, select the udfs file system and not the default cdfs file system.

2. Navigate to the trc\ [osdir] directory, where osdir is relevant to your operating system. For example \trc\windows.

3. Run the trc_server_setup.XXX file where XXX is relevant to your operating system.

(18)

Windows

trc_server_setup.exe Linux trc_server_setup.bin

Note: If you are using Red Hat 6.0 64-bit the following libraries along with their dependencies, need to be installed if they are not already installed, glibc.i686, libgcc.i686, libXft.i686, libXmu.i686, libXp.i686, libXtst.i686.

4. For the remainder of the installation follow from step 4 in Running an automated server installin the IBM Tivoli Remote Control Installation Guide Note: If you are using an MSSQL 2008 database select the MSSQL 2005 option on the select database server installer screen.

Installing a stand-alone server

To install a stand-alone server component complete the following steps :- 1. Follow the steps in the following sections of the chapter in the IBM Tivoli

Remote Control Installation Guide which deals with running a manual server installation

v Setting up the database

v Setting up the application server

2. Insert the Tivoli Endpoint Manager for Remote Control installation DVD and follow from step 1 in the chapter that explains how to deploy the IBM Tivoli Remote Control application in the IBM Tivoli Remote Control Installation Guide.

3. Navigate to the Disk1\InstData directory and then relevant operating system directory on the DVD.

Note: If you are using Red Hat 6.0 64-bit the following libraries along with their dependencies, need to be installed if they are not already installed, glibc.i686, libgcc.i686, libXmu.i686, libXtst.i686, libXp.i686.

Passport Advantage: server installation files

To install the server component you will require the following e-images from Passport Advantage depending on your operating system.

Table 5. Parts required for installing the Tivoli Endpoint Manager for Remote Control Server Installation type Part Number File name

server with embedded Websphere Application Server. See “Installing a server with embedded components” on page 9 for the installation steps when using these e-images.

Windows

CI3N8ML - IBM Tivoli Endpoint Manager for Remote Control V8.2.0 Image 1.

TEM_Rem_Cntrl_V820_Image_1.zip

Linux CI3N9ML - IBM Tivoli Endpoint Manager for Remote Control V8.2.0 Image 2.

TEM_Rem_Cntrl_V820_Image_2.tar

(19)

Table 5. Parts required for installing the Tivoli Endpoint Manager for Remote Control Server (continued)

Installation type Part Number File name stand-alone server. See

“Installing a stand-alone server” on page 10 for the installation steps when using this e-image.

Windows, Linux, AIX, Solaris CI3NAML -

IBM Tivoli Endpoint Manager for Remote Control V8.2.0 Image 3.

When you have downloaded the required files and unpacked them take note of the following directory references when carrying out the installation steps.

v If you are using TEM_Rem_Cntrl_V820_Image_1.zip or

TEM_Rem_Cntrl_V820_Image_2.tarto install the server with embedded components replace any references to the \trc directory with

\TEM_Rem_Cntrl_V820_Image_X, where X is 1 or 2 depending on the file that you have downloaded.

v If you are using TEM_Rem_Cntrl_V820_Image_3.tar to install a stand-alone server replace any references to Disk3 with \TEM_Rem_Cntrl_V820_Image_3.

Installing the target component

When you have installed the target component use the IBM Tivoli Remote

Control User's Guide, IBM Tivoli Remote Control Administrator's Guide and the Tivoli Endpoint Manager for Remote Control Release Notes for details of the target features and functionality.

Installing from the TEM console

You can use the TEM console to install the Tivoli Endpoint Manager for Remote Control target using the fixlets contained in the deployment node. See “Deploying from the console” on page 27.

Installing using the installation media

Windows target installation

Carrying out an attended target installation:

During an attended target installation you will navigate through installer screens to configure or accept default values for various target property values. To carry out an attended target installation complete the following steps :-

2. Navigate to the trc\windows directory.

3. Start the trc_target_setup..exe file.

4. For the remainder of the installation follow from step 12 in Running an automated target installin the IBM Tivoli Remote Control Installation Guide.

Note: If you select an option to peer to peer on the Peer to Peer Failover screen and click Peer to Peer Policies, see step 2 on page 63, Selecting

configuration valuesfor definitions of the peer to peer policies that can be set.

Carrying out a custom installation:

Chapter 4. Installing Remote Control 11

(20)

You can carry out a target custom installation to install the target software using parameters by carrying out one of the following types of installation.

unattended and silent

No interaction is required by the user and no UI windows or progress bars are displayed to the user.

unattended

No interaction is required by the user and an installation progress bar is displayed to the user.

attended

The full installation UI is displayed and requires user interaction. You can customise installation settings and also assign the target to a specific group at install time.

To carry out a target custom installation complete the following steps :-.

2. Navigate to the trc\windows directory.

3. For the remainder of the installation follow the steps in Performing a target custom install on Windowsin the IBM Tivoli Remote Control Installation Guide

Note:

a. The trc_target_setup.exe file should be copied from the DVD to the IBMTRC directory.

b. See step 2 on page 63 for definitions of the target properties that can be set.

Linux target installation

Installing the target using the RPM file:

The installation DVD contains a default target RPM file which you can install and then configure the target after the installation. To extract and install the RPM file complete the following steps :-

1. Navigate to the \Disk1\InstData\VM\ [osdir] directory, where [osdir] is the operating system that you will use to run the additional setup file on. For example: you can run the additional setup file on a windows machine to extract the target installation files and then copy the relevant files to the machine that you want to install the target component on.

2. Start the additional setup file.

Windows

trc_additional_setup.exe Linux, Solaris, AIX

trc_additional_setup.bin

Note: If you are using Red Hat 6.0 64-bit the following libraries along with their dependencies, need to be installed if they are not already installed, glibc.i686, libgcc.i686, libXmu.i686, libXtst.i686,libXp.i686,libXi.i686.

3. Follow from step 2 in Using the additional setup utility for installation in the IBM Tivoli Remote Control Installation Guide to extract the target installation files.

4. Navigate to the RCTarget directory and you will see the ibm-trc-target- 8.2.0.i386.rpmfile. If required copy this file to the machine that you want to install the Linux target on.

(21)

5. To install the Linux target type the following command rpm -ivh ibm-trc-target-8.2.0.i386.rpm

When the target is installed you can configure the target properties by editing the etc/ibmtrc.conf file. See Selecting Configuration values in step 2 on page 63 for details of target properties and their definitions.

Note: To create a customised rpm file see the chapter that explains how to install and configure the target using the RPM file in the IBM Tivoli Remote Control Installation Guide

Installing the target using the SPB file:

You can install the Tivoli Endpoint Manager for Remote Control Windows and Linux target components using the Software Package Block (SPB) installation method which requires IBM^®Tivoli^®Provisioning Manager. The files required for this installation are extracted using the additional setup utility. To install the target using the SPB installation method complete the following steps :-

1. Extract and run the additional setup utility files.

Extracting the additional setup utility from the installation media a. To extract the additional setup files using the installation DVD

follow from step 1 on page 12 to step 4 on page 12.

b. In step 4 on page 12 when you navigate to the RCTarget directory you will see the spb files

Windows

trc_target_win.spb Linux trc_target_linux.spb

Note: If you are using Red Hat 6.0 64-bit the following libraries along with their dependencies, need to be installed if they are not already installed, glibc.i686, libgcc.i686, libXmu.i686, libXp.i686, libXtst.i686.

Extracting the additional setup utility from the Passport Advantage e-image a. To extract the additional setup files using Passport Advantage you

need to download e-image TEM_ Rem_Cntrl_V820_3.tar. See Table 6 on page 14 for the part number required.

b. Unpack this file and follow from step 1 on page 12 to step 4 on page 12.

c. In step 4 on page 12 when you navigate to the RCTarget directory you will see the spb files

Windows

trc_target_win.spb Linux trc_target_linux.spb

Note: If you are using Red Hat 6.0 64-bit the following libraries along with their dependencies, need to be installed if they are not already installed, glibc.i686, libgcc.i686, libXft.i686, libXmu.i686, libXp.i686, libXtst.i686.

2. For details of installing the software package block file please refer to the IBM Tivoli Provisioning Manager information center at : http://

publib.boulder.ibm.com/infocenter/tivihelp/v28r1/index.jspand the chapter that explains installing software products.

(22)

Note: Tivoli Common Agent (TCA) needs to be installed on the computers before the target can be installed using the SPB method.

Passport Advantage: target installation files

To install the target component you will require the following e-images from Passport Advantage depending on your operating system.

Table 6. Parts required for installing the Tivoli Endpoint Manager for Remote Control target

Operating system Part Number File name

Windows. See “Windows target installation” on page 11 for installation steps.

CI3N8ML - IBM Tivoli Endpoint Manager for Remote Control V8.2.0 Image 1.

Linux. See “Linux target installation” on page 12 for installation steps.

CI3NAML - IBM Tivoli Endpoint Manager for Remote Control V8.2.0 Image 3.

When you have downloaded the required files and unpacked them, take note of the following directory references when carrying out the steps.

v For TEM_Rem_Cntrl_V820_Image_1.zip - when installing a Windows target replace any references to the \trc directory with \TEM_Rem_Cntrl_V820_Image_1.

v For TEM_Rem_Cntrl_V820_Image_3.tar - when installing a Linux target replace any references to Disk3 with \TEM_Rem_Cntrl_V820_Image_3.

Installing the controller component

When you have installed the controller component use the IBM Tivoli Remote Control User's Guide, IBM Tivoli Remote Control Administrator's Guide and the Tivoli Endpoint Manager for Remote Control Release Notes for details of the controller features and functionality.

Installing from the TEM console

You can use the TEM console to install the Tivoli Endpoint Manager for Remote Control controller using the fixlets, relevant to you operating system, contained in the deployment node. See “Deploying from the console” on page 27.

Installing using the installation media

To install the TEM for Remote Control controller component using the installation DVD complete the following steps :-

2. The operating system that you are using will determine which installation files are required.

Windows^®

To install the controller in Windows see Installing the controller in Windowsin the IBM Tivoli Remote Control Installation Guide using the \trc and \Disk1 directories on the DVD during the installation steps.

AIX, Linux, Solaric (SPARC)

To install the controller in AIX, Linux or Solaris (SPARC) see Installing the controller in Linuxin the IBM Tivoli Remote Control Installation Guide using the \Disk1 directory on the DVD during the installation

(23)

Note: The controller command line package that will be installed will be ibm-trc-controller-8.2.0.noarch.rpm.

Other supported operating systems

To install the controller on a system that is running another supported operating system (with the correct version of Java) that is not

WIndows, Linux, AIX or Solaris (SPARC) you can use the files in the

\Disk1directory of the installation DVD. To install the controller see Installing the controller on other supported operating systemsin the IBM Tivoli Remote Control Installation Guide.

Passport Advantage: controller installation files

To install the controller component you will require the following e-images from Passport Advantage depending on your operating system.

Table 7. Parts required for installing the Tivoli Endpoint Manager for Remote Control controller

Operating system Part Number File name

Windows CI3N8ML - IBM Tivoli

Endpoint Manager for Remote Control V8.2.0 Image 1.

Windows, Linux, AIX, Solaris (SPARC) or any other supported operating system which is running the correct version of Java.

CI3NAML - IBM Tivoli Endpoint Manager for Remote Control V8.2.0 Image 3.

When you have downloaded the required files and unpacked them you can use the steps in “Installing using the installation media” on page 14 taking note of the following references

v When using TEM_Rem_Cntrl_V820_Image_1.zip - replace any references to the

\trc directory with \TEM_Rem_Cntrl_V820_Image_1.

v When using TEM_Rem_Cntrl_V820_Image_3.tar - replace any references to Disk3 with \TEM_Rem_Cntrl_V820_Image_3.

(24)

(25)

Chapter 5. Definitions

This section defines some common terms used when using Tivoli Endpoint Manager for Remote Control.

Remote control session

Establishing a connection to a computer in your environment to observe or actively control the computer remotely. In the session the controller user's keyboard and mouse become the primary keyboard and mouse for the remote system. Functionality such as chat, guidance, reboot, and file transfer are some of the options available for use in a remote control session. See the IBM Tivoli Remote Control User's Guide for more details of the types of session that can be established, the functionality of the controller GUI and the features available within these sessions.

Peer to peer session

A remote control session that is established directly between the controller and the target. The controller user starts the controller component locally and specifies the target that they want to takeover remotely. The local properties that have been set on the target will be used for the session. See

“Managing target and server configurations” on page 56 for more

information. For details about using the controller GUI once the session is established see the IBM Tivoli Remote Control User's Guide.

Managed remote control session

A remote control session in which the controller user initiates the session from the Tivoli Endpoint Manager for Remote Control server. From here the controller component is initiated and contacts the target to send the session request. The target then contacts the server to authenticate the request and obtain the policies and permissions that will be set for the session. See the IBM Tivoli Remote Control Administrators Guide for more information on policies and permissions for a managed remote control session. If the target cannot reach the server then the session will be refused.

Session policies

Session policies define the actions that can be carried out by the controller user and the features available on the target system during a remote control session. In a peer to peer session these are determined by the local properties defined on the target and in a managed session they are determined by policies and permissions resolved from user and target group relationships. See The Policy Engine section in the IBM Tivoli Remote Control Administrators Guide for more information on how policies and permissions are derived for a managed remote control session.

(26)

(27)

Chapter 6. Using the new Tivoli Endpoint Manager console

Tivoli Endpoint Manager for Remote Control encompasses a host of new features that provide the components required for remote takeover and monitoring of workstations and servers in your deployment.

In addition, the TEM Console changed after version 7.2 which resulted in several new navigation updates for accessing your data. This section will address how to get around in the new Console. The navigation tree in the TEM Console, which is available for all Tivoli Endpoint Manager products, will serve as your central command for all Tivoli Endpoint Manager for Remote Control functionality. The navigation tree gives you easy access to all reports, wizards, Fixlet messages, analyses and tasks related to controlling and managing the target machines in your network.

Components

The TEM Console organizes content into four parts:

v Domain Panel – Includes navigation tree and list of all domains.

v Navigation Tree – Includes list of nodes and sub-nodes containing site content.

v List Panel – Contains listing of tasks and Fixlets.

v Work Area – Work window where Fixlet and dialogs display.

In the context of the TEM Console, products or sites are grouped by categories or domains. For example, Tivoli Endpoint Manager for Remote Control is one of the sites contained within the Systems Lifecycle domain, as part of the Remote Control Configuration node.

(28)

The Domain Panel is the area on the left side of the Console that includes a navigation tree and a list of all domains. The Navigation Tree includes a list of nodes and sub-nodes containing site content.

In the image below, you will see a navigation “tree” at the top with expandable and collapsible nodes, and a list of domains at the bottom. By clicking the Systems Lifecycle domain at the bottom of the domain panel, a list of sites associated with that particular domain will display in the navigation tree at the top.

The red outlined area represents the entire Domain Panel (including the navigation tree and list of domains), and the blue outlined area contains just the Navigation Tree for the Tivoli Endpoint Manager for Remote Control site.

(29)

Tivoli Endpoint Manager for Remote Control tasks are sorted through upper and lower task windows, which are located on the right side of the Console.

The upper panel (blue), called the List Panel , contains columns that sort data according to type, for example, Status, Name, Site, Applicable Computer Count.

The lower panel or Work Area (red) presents the fixlet, task screen from which you will be directed to take specific actions to customise the content in your

deployment.

Chapter 6. Using the TEM console 21

(30)

(31)

Chapter 7. Dashboards overview

Tivoli Endpoint Manager for Remote Control offers a convenient dashboard for viewing the deployment distribution of the Tivoli Endpoint Manager for Remote Control components in your environment and the distribution of the type of target deployment carried out. You can access this dashboard from the top of the Tivoli Endpoint Manager for Remote Control navigation tree by selecting Tivoli Endpoint Manager for Remote Control Overview.

Viewing deployment distribution data

The Tivoli Endpoint Manager for Remote Control Overview dashboard includes two separate sections showing the deployment distribution of Tivoli Endpoint Manager for Remote Control and the target deployment type, distribution . Each section is explained below:

The Tivoli Endpoint Manager for Remote Control Overview Deployment section displays the number of computers in your environment having the various Tivoli Endpoint Manager for Remote Control components installed. You can view different representations of the data by clicking on the buttons at the top right of the section to display a graphical version or data table version.

(32)

You can also view both representations of the data by clicking the button on the bottom left of the graph.

(33)

The Target Deployment Mode section shows the distribution of the type of target deployment that was carried out, on the computers in your environment which have the Tivoli Endpoint Manager for Remote Control agent software running. See

“Deploying from the console” on page 27 for details of the different target

deployment types.You can view different representations of the data by clicking on the buttons at the top right of the section to display a graphical version or data table version.

Both representations of the data can be viewed using the same instructions as in the previous section.

There are two icons on the top right of the dashboard that you can use for displaying the latest graphical data or for printing the data .

The refresh icon can be used to display the latest deployment distribution data.

The print icon can be used to print the dashboard data. The data will be printed to a pdf file that you can save to a specified location for future printing.

Chapter 7. Dashboards overview 25

(34)

(35)

Chapter 8. Using Tivoli Endpoint Manager for Remote Control

The Tivoli Endpoint Manager for Remote Control navigation tree provides a suite of fixlets, tasks and wizards that you can use for deploying, updating and

gathering data from the components required to configure, monitor and control the computers in your environment.

Deploying from the console

The Deployment node in the Tivoli Endpoint Manager for Remote Control

navigation tree provides two sub-nodes which are operating system specific. These sub-nodes provide the components you need to establish a remote control session as well as other utilities that you can use, to connect to targets by using the command line and for installing support for accessing machines on different networks. Select the node which is relevant to your operating system to view a list of tasks that you can use to deploy or remove the required Tivoli Endpoint

Manager for Remote Control components and utilities.

Note: The Tivoli Endpoint Manager for Remote Control can also be deployed using the installation media, see Chapter 4, “Installing Tivoli Endpoint Manager for Remote Control,” on page 9.

Controller

The controller component should be deployed on the computer(s) that will initiate the remote control session when you do not have access to a Tivoli Endpoint Manager for Remote Control server.

Target The target component should be deployed on the computer(s) that will be controlled during a remote control session. Tivoli Endpoint Manager for Remote Control offers two ways of deploying the target component depending on how you will establish a connection with the target. Both of these session types are explained in the Chapter 5, “Definitions,” on page 17 section and in more detail in the IBM Tivoli Remote Control Users Guide.

Note: It should be noted that the 'Using the Tivoli Endpoint Manager for Remote Control server' method requires a Tivoli Endpoint Manager for Remote Control server to have already been installed in your environment.

CLI tools

The command line tools contain two utilities that can be run from the command line. You can use these utilities to start a remote control session with a target or run commands on a target system without target user interaction. Once installed, these tools can be useful if you want to connect to a target without accessing the Tivoli Endpoint Manager for Remote Control Server interface or for using as part of a script to run multiple commands in an automated fashion.

Note: In order to deploy the CLI Tools you need to have the URL of a Tivoli Endpoint Manager for Remote Control server that you have access to.

Gateway

If you have targets, controllers and severs on different networks that cannot directly contact each other you can install and configure gateway

(36)

support. With the gateway support you can configure your network to allow these connections to be established.

Windows deployment

The Windows deployment node provides a set of tasks that you can use to install or remove the following components in a Windows environment.

v target and controller software v CLI tools

v gateway support

Deploying the Windows target

You can use the Deploy Tivoli Endpoint Manager for Remote Control Target for Windows task to install the target software onto a Windows computer. To initiate this task complete the following steps:

1. Click on Deployment > Windows in the navigation tree.

2. Click Deploy Tivoli Endpoint Manager for Remote Control target for Windows.

3. In the Task window, review the description and follow the instructions in the Actions box to initiate the task.

There are two actions available for this task. Determine your required installation method and follow the instructions given.

(37)

Deploy the TRC target in Peer2Peer mode

With this installation method you can establish remote control sessions directly between the controller and the target without the need for a Tivoli Endpoint Manager for Remote Control server. This deployment method will install the target without requiring a Tivoli Endpoint Manager for Remote Control server URL to be specified and the local target policies set by this installation method will be used when a remote control session is established. See “Managing target and server configurations” on page 56 for details of the target installation

properties.

In the Take Action window on the Target tab, select the required option for determining which target(s) to deploy the Tivoli Endpoint Manager for Remote Control target on.

Click OK and enter your Private Key Password.

The summary screen will show the progress of the task and will show status complete when it is finished.

Note: If you want the target to register with the Tivoli Endpoint Manager for Remote Control server in the future you can use the Tivoli Endpoint Manager for Remote Control Target Wizard to create a configuration task and specify the server URL of the required server.

Running this task on the selected target will reconfigure it and it will then be able to contact the server. See “Creating Tivoli Endpoint Manager for Remote Control target configuration tasks” on page 63.

Deploy the TRC target and specify the Tivoli Endpoint Manager for Remote Control Server

Chose this installation option for target(s) to register with the Tivoli

Chapter 8. Using Tivoli Endpoint Manager for Remote Control 29

(38)

Endpoint Manager for Remote Control server and take part in remote control sessions initiated from the server. This deployment method will require a Tivoli Endpoint Manager for Remote Control server URL to be specified. If a remote control session, initiated from the Remote Control server, is requested with this target the specified server will be contacted to authenticate the request. When the request is

authenticated, the policies set for the session will be passed from the Remote Control server to the target and the session will be established.

See “Managing target and server configurations” on page 56 for details of the target installation properties.

Enter the URL of your Tivoli Endpoint Manager for Remote Control server and click OK.

Click OK and enter your Private Key Password.

Note: This installation option should only be chosen if you have the Tivoli Endpoint Manager for Remote Control server component installed and running.

Removing the Windows target

You can use the Uninstall Tivoli Endpoint Manager for Remote Control Target for Windows task to remove the target software from a Windows computer which has the target software already installed. To initiate this task complete the

following steps:

2. Click Uninstall Tivoli Endpoint Manager for Remote Control target for Windows.

(39)

4. In the Take Action window, on the Target tab, select the required option for determining which target(s) to remove the Tivoli Endpoint Manager for Remote Control target from.

5. Click OK and enter your Private Key Password.

Note: It should be noted that after the removal of the target there might be some files, which were created as part of the normal execution of the target program, that are not deleted automatically. These files are located in Documents and Settings\All Users\Application Data\IBM\Tivoli\Remote Control.

Deploying the Windows controller

You can use the Deploy Tivoli Endpoint Manager for Remote Control Controller for Windowstask to install the controller software onto a Windows computer.

Note: If you want to be able to start a remote control session with targets from the TEM console ( see “Starting a peer to peer session from the TEM console” on page 50 ) you should deploy the controller to the same machine as the console is installed on. However it should be noted that when the controller is deployed it is only the current user who is logged on to the machine that you are deploying to that will have the rights to see the menu item that allows you to start a session, it will not be visible to other users.

To initiate this task complete the following steps:

2. Click Deploy Tivoli Endpoint Manager for Remote Control Controller for Windows.

(40)

4. In the Take Action window on the Target tab, select the required option for determining which target(s) to deploy the controller on.

Removing the Windows controller

You can use the Uninstall Tivoli Endpoint Manager for Remote Control Controller for Windowstask to remove the controller software from a Windows computer which has the controller software already installed. To initiate this task complete the following steps:

2. Click Uninstall Tivoli Endpoint Manager for Remote Control Controller for Windows.

(41)

4. In the Take Action window, in the Target tab, select the required option for determining which target(s) to remove the Tivoli Endpoint Manager for Remote Control controller from.

Deploying the Windows CLI tools

You can use the Deploy Tivoli Endpoint Manager for Remote Control CLI Tools for Windowstask to install the CLI tools onto a Windows computer. To initiate this task complete the following steps:

Note:

1. You do not need to deploy the CLI tools on any computers that you have deployed the target on as these computers will already have the CLI tools installed along with the target.

2. In order to deploy this task you need the URL for a Tivoli Endpoint Manager for Remote Control server that you have access to.

2. Click Deploy Tivoli Endpoint Manager for Remote Control CLI Tools for Windows.

(42)

4. Enter the URL of the Tivoli Endpoint Manager for Remote Control server and click OK.

5. In the Take Action window on the Target tab, select the required option for determining which target(s) to deploy the CLI tools on.

You should now have the following two CLI utilities installed in the \Program Files\IBM\tivoli\Remote Control\Target directory on the target(s) that were selected when you ran the deployment task.

wrc.exe

You can use this tool to start a remote control session with a target.

wrcmdpcr.exe

You can use this tool to run a command on a target and see the output from the command on the machine that you issued the command from.

For more details on how to use the command line tools see Using remote control commands from the command linein the IBM Tivoli Remote Control User's Guide.

Removing the Windows CLI tools

You can use the Uninstall Tivoli Endpoint Manager for Remote Control CLI Tools for Windowstask to remove the CLI tools from a Windows computer which has the CLI tools already installed. To initiate this task complete the following steps:

2. Click Uninstall Tivoli Endpoint Manager for Remote Control CLI Tools for Windows.

(43)

4. In the Take Action window, in the Target tab , select the required option for determining which target(s) to remove the CLI tools from.

The summary screen will show the progress of the task and will show status complete when it is finished. The CLI tools should no longer be present on the selected target(s).

Note: It should be noted that after the removal of the cli tools there could be some files, which were created as part of the normal execution of the cli installation program, that are not deleted automatically. These files are located in Documents and Settings\All Users\Application Data\IBM\Tivoli\Remote Control.

Deploying the Windows gateway support

You can use the Deploy Tivoli Endpoint Manager for Remote Control Gateway for Windowstask to install gateway support onto a Windows computer. To initiate this task complete the following steps:

2. Click Deploy Tivoli Endpoint Manager for Remote Control Gateway for Windows.

4. In the Take Action window on the Target tab, select the required option for determining which target(s) to deploy the gateway support on.

You should now have gateway support installed on the target(s) that were selected when you ran the deployment task. The files for this will have been installed in the \Program Files\IBM\tivoli\Remote Control\Gateway directory on the selected target(s).

(44)

To make use of the gateway support you will need to setup a gateway

configuration for your environment. See Configuring the gateway support in the IBM Tivoli Remote Control Administrator's Guide for details.

Removing the Windows gateway support

You can use the Uninstall Tivoli Endpoint Manager for Remote Control Gateway support for Windows task to remove the gateway support files from a Windows computer which has these files already installed. To initiate this task complete the following steps:

2. Click Uninstall Tivoli Endpoint Manager for Remote Control Gateway for Windows.

4. In the Take Action window, in the Target tab , select the required option for determining which target(s) to remove the gateway support from.

The gateway support files should no longer be present on the selected target(s).

Linux deployment

The Linux deployment node provides a set of tasks that you can use to install or remove the following components in a Linux environment.

v target and controller software v CLI tools

v gateway support

Note: If you are installing the target, cli and gateway components on a Red Hat 6.0 64 bit machine the following libraries along with their dependencies, need to be installed if they are not already installed. For all: glibc.i686 and additionally for the

(45)

Deploying the Linux target

You can use the Deploy Tivoli Endpoint Manager for Remote Control Target for Linuxtask to install the target software onto a Linux computer. To initiate this task complete the following steps:

1. Click on Deployment > Linux in the navigation tree.

2. Click Deploy Tivoli Endpoint Manager for Remote Control target for Linux . 3. In the Task window, review the description and follow the instructions in the

Actions box to initiate the task.

There are two actions available for this task. Determine your required installation method and follow the instructions given.

Deploy the TRC target in Peer2Peer mode

With this installation method you can establish remote control sessions directly between the controller and the target without the need for a Tivoli Endpoint Manager for Remote Control server. This deployment method will install the target without requiring a Tivoli Endpoint Manager for Remote Control server URL to be specified and the local target policies set by this installation method will be used when a remote control session is established. See “Managing target and server configurations” on page 56 for details of the target installation

properties.

Click OK and enter your Private Key Password.

Note: If you want the target to register with the Tivoli Endpoint Manager for Remote Control server in the future you can use the Tivoli

(46)

Endpoint Manager for Remote Control Target Wizard to create a configuration task and specify the server URL of the required server.

Running this task on the selected target will reconfigure it and it will then be able to contact the server. See “Creating Tivoli Endpoint Manager for Remote Control target configuration tasks” on page 63.

Deploy the TRC target and specify the Tivoli Endpoint Manager for Remote Control Server

Choose this installation option for target(s) to register with the Tivoli Endpoint Manager for Remote Control server and take part in remote control sessions initiated from the server. This deployment method will require a Tivoli Endpoint Manager for Remote Control server URL to be specified. If a remote control session, initiated from the Remote Control server, is requested with this target the specified server will be contacted to authenticate the request. When the request is

authenticated, the policies set for the session will be passed from the Remote Control server to the target and the session will be established.

See “Managing target and server configurations” on page 56 for details of the target installation properties.

Enter the URL of your Tivoli Endpoint Manager for Remote Control server and click OK.

Click OK and enter your Private Key Password.

Note: This installation option should only be chosen if you have the Tivoli Endpoint Manager for Remote Control server component installed and running.

Removing the Linux target

You can use the Uninstall Tivoli Endpoint Manager for Remote Control Target for Linuxtask to remove the target software from a Linux computer which has the target software already installed. To initiate this task complete the following steps:

1. Click on Deployment > Linux > in the navigation tree.

2. Click Uninstall Tivoli Endpoint Manager for Remote Control target for Linux.

(47)

4. In the Take Action window, on the Target tab, select the required option for determining which target(s) to remove the Tivoli Endpoint Manager for Remote Control target from.

Note: It should be noted that after the removal of the target there might be some files, which were created as part of the normal execution of the target program, that are not deleted automatically. These files are located in the following directories /opt/ibm and /var/opt/ibm/trc/target.

Deploying the Linux controller

You can use the Deploy Tivoli Endpoint Manager for Remote Control Controller for Linuxtask to install the controller software onto a Linux computer.

Note: If you are installing the controller on a Red Hat 6.0 64 bit machine you require the following additional libraries, along with all their dependencies, to be installed: libXft.i686 libXmu.i686 libXp.i686 libXtst.i686 .

2. Click Deploy Tivoli Endpoint Manager for Remote Control Controller for Linux.

(48)

4. In the Take Action window on the Target tab, select the required option for determining which target(s) to deploy the controller on.

5. Click OK and enter your Private Key Password.

Removing the Linux controller

You can use the Uninstall Tivoli Endpoint Manager for Remote Control

Controller for Linuxtask to remove the controller software from a Linux computer which has the controller software already installed. To initiate this task complete the following steps:

1. Click Deployment > Linux in the navigation tree.

2. Click Uninstall Tivoli Endpoint Manager for Remote Control Controller for Linux.

(49)

4. In the Take Action window, in the Target tab, select the required option for determining which target(s) to remove the Tivoli Endpoint Manager for Remote Control controller from.

Deploying the Linux CLI tools

You can use the Deploy Tivoli Endpoint Manager for Remote Control CLI Tools for Linuxtask to install the CLI tools onto a Linux computer.

Note:

1. You do not need to deploy the CLI tools on any computers that you have deployed the target on as these computers will already have the CLI tools installed along with the target.

2. In order to deploy this task you need the URL for a Tivoli Endpoint Manager for Remote Control server that you have access to.

2. Click Deploy Tivoli Endpoint Manager for Remote Control CLI Tools for Linux.

Tivoli Endpoint Manager for Remote Control Version 8 Release 2. User s Guide

Tivoli Endpoint Manager for Remote Control

Version 8 Release 2

User’s Guide

Tivoli Endpoint Manager for Remote Control

Version 8 Release 2

User’s Guide

Contents

About this publication

What's new

Chapter 1. Overview

Chapter 2. System requirements

Server requirements

Controller requirements

Target requirements

Gateway requirements

Chapter 3. Server environment guidelines

Small environment guidelines

Medium environment guidelines

Large environment guidelines

Chapter 4. Installing Tivoli Endpoint Manager for Remote Control

Installing the server component.

Installing from the TEM console

Using the installation media

Installing a server with embedded components

Installing a stand-alone server

Passport Advantage: server installation files

Installing the target component

Installing from the TEM console

Installing using the installation media

Windows target installation

Linux target installation

Passport Advantage: target installation files

Installing the controller component

Installing from the TEM console

Installing using the installation media

Passport Advantage: controller installation files

Chapter 5. Definitions

Chapter 6. Using the new Tivoli Endpoint Manager console

Components

Chapter 7. Dashboards overview

Viewing deployment distribution data

Chapter 8. Using Tivoli Endpoint Manager for Remote Control

Deploying from the console

Windows deployment

Deploying the Windows target

Removing the Windows target

Deploying the Windows controller

Removing the Windows controller

Deploying the Windows CLI tools

Removing the Windows CLI tools

Deploying the Windows gateway support

Removing the Windows gateway support

Linux deployment

Deploying the Linux target

Removing the Linux target

Deploying the Linux controller

Removing the Linux controller

Deploying the Linux CLI tools