Tivoli Remote Controlpublib.boulder.ibm.com/tividd/td/remote/rc37ug/en_US/PDF/... · 2002-11-09 · Authorization roles ..... 4 Default policy ... a working knowledge of Tivoli Management

Tivoli RemoteControlUser’s GuideVersion 3.7

Tivoli RemoteControlUser’s GuideVersion 3.7

Tivoli Remote Control User’s Guide (July 2000)

Copyright Notice:

Copyright © 2000 by IBM Corp., Copyright © 1996, 2000 Tivoli Systems Inc., includingthis documentation and all software. All rights reserved. May only be used pursuant to aTivoli Systems Software License Agreement, an IBM Software License Agreement, orAddendum for Tivoli Products to IBM Customer or License Agreement. No part of thispublication may be reproduced, transmitted, transcribed, stored in a retrieval system, ortranslated into any computer language, in any form or by any means, electronic, mechanical,magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBMCorp. IBM Corp. grants you limited permission to make hardcopy or other reproductions ofany machine-readable documentation for your own use, provided that each such reproductionshall carry the IBM Corp. copyright notice. No other rights under copyright are grantedwithout prior written permission of IBM Corp. The document is not intended for productionand is furnished “as is” without warranty of any kind. All warranties on this document arehereby disclaimed including the warranties of merchantability and fitness for aparticular purpose.

Note to U.S. Government Users—Documentation related to restricted rights—Use,duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contractwith IBM Corporation.

Trademarks

IBM, Tivoli, OS/2, Tivoli Management Environment, Tivoli Remote Control, and TME aretrademarks of International Business Machines Corp. or Tivoli Systems Inc. in the UnitedStates, other countries, or both. In Denmark, Tivoli is a trademark licensed fromKjøbenhavns Sommer - Tivoli A/S.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registeredtrademarks of Microsoft Corporation.

UNIX is a registered trademark in the United States and other countries licensed exclusivelythrough X/Open Company Limited.

NetWare and Novell are trademarks of Novell, Incorporated.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the UnitedStates, other countries, or both.

Other company, product, and service names mentioned in this document may be trademarksor servicemarks of others.

NoticesReferences in this publication to Tivoli Systems or IBM products, programs, or services donot imply that they will be available in all countries in which Tivoli Systems or IBMoperates. Any reference to these products, programs, or services is not intended to imply thatonly Tivoli Systems or IBM products, programs, or services can be used. Subject to TivoliSystem’s or IBM’s valid intellectual property or other legally protectable right, anyfunctionally equivalent product, program, or service can be used instead of the referencedproduct, program, or service. The evaluation and verification of operation in conjunction withother products, except those expressly designated by Tivoli Systems or IBM, are theresponsibility of the user.Tivoli Systems or IBM may have patents or pending patent applications covering subjectmatter in this document. The furnishing of this document does not give you any license tothese patents. You can send license inquiries, in writing, to the IBM Director of Licensing,IBM Corporation, North Castle Drive, Armonk, New York 10504-1785, U.S.A.

ISO 9001 Certification

This product was developed using an ISO 9001 certified quality system.

Certification has been awarded by Bureau Veritas Quality International (BVQI) (CertificationNo. BVQI - 92053).

BVQI is a world leader in quality certification and is currently recognized by more than 20accreditation bodies.

iiiTivoli Remote Control User’s Guide

iv Version 3.7

Contents

Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiWho Should Read This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

What This Guide Contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Conventions Used in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Platform-Specific Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Tivoli Remote Control Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Accessing Publications Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Ordering Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Providing Feedback about Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1What You Can Do With Tivoli Remote Control . . . . . . . . . . . . . . . . . . . . . . . 1

Tivoli Remote Control Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Tivoli Remote Control Security Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Authorization roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Default policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Notice generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Log generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

What’s New in Tivoli Remote Control Version 3.7? . . . . . . . . . . . . . . . . . . . . 5

Chapter 2. Installing Tivoli Remote Control . . . . . . . . . . . . . . 7High-level Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Operating Systems and Protocols Supported. . . . . . . . . . . . . . . . . . . . . 10

vTivoli Remote Control User’s Guide

Product Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Components Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Installing Tivoli Remote Control with SIS . . . . . . . . . . . . . . . . . . . . . . 14

Installing Tivoli Remote Control from the Tivoli Desktop . . . . . . . . . . 14

Installing Tivoli Remote Control Using the winstall Command. . . . . . . 16

Installing on Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Installing Tools, Plugins, and Diagnosis Packs . . . . . . . . . . . . . . . . . . . 18

TEC Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Product Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Upgrading Tivoli Remote Control from the Tivoli Desktop. . . . . . . . . . 22

Uninstalling the Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Uninstalling the Server and Remote Control Gateway . . . . . . . . . . . . . 24

Uninstalling Tools, Plugins, and Packs . . . . . . . . . . . . . . . . . . . . . . . . . 25

Uninstalling Controller and Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Uninstalling File Transfer, Chat, and Remote Diagnosis Console . . . . . 36

Uninstalling Remote Diagnosis Target . . . . . . . . . . . . . . . . . . . . . . . . . 44

Uninstalling Packs from a Remote Diagnosis Target. . . . . . . . . . . . . . . 45

Uninstalling Tools from a Remote Diagnosis Target . . . . . . . . . . . . . . . 46

Uninstalling Plugins from a Remote Diagnosis Console . . . . . . . . . . . . 46

Chapter 3. Configuring and Starting Tivoli RemoteControl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Configuration Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Adding Tivoli Remote Control to a Policy Region . . . . . . . . . . . . . . . . 50

Assigning Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Assigning Targets to a Policy Region. . . . . . . . . . . . . . . . . . . . . . . . . . 53

Changing the Values of Activity and Display Settings . . . . . . . . . . . . . 55

Creating a New Policy Default Object . . . . . . . . . . . . . . . . . . . . . . . . . 75

vi Version 3.7

Changing the Default Policy of the Tivoli Remote Control Dialog . . . . 76

Using the Tivoli Remote Control Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Starting a Tivoli Remote Control Action . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

From the Tivoli Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

From a Web Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

From a Terminal Server Environment . . . . . . . . . . . . . . . . . . . . . . . . . 84

From a Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Chapter 4. Using Remote Control and Reboot Actions 87Using the Reboot Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Using the Remote Control Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Starting and Ending a Remote Control Session . . . . . . . . . . . . . . . . . . 88

The Remote Control Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Changing the Session State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Switching between Keyboard Modes . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Sending System Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Mixed Keyboards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Chapter 5. Using the Chat Action . . . . . . . . . . . . . . . . . . . . . . . 95Starting and Ending a Chat Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

The Chat Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Exchanging messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Suspending and Reactivating a Chat Session . . . . . . . . . . . . . . . . . . . . . . . . 98

Recording Chat Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Using Chat with Remote Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Chapter 6. Using the File Transfer Action . . . . . . . . . . . . . 101Starting and Ending a File Transfer Session . . . . . . . . . . . . . . . . . . . . . . . . 101

The File Transfer Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

viiTivoli Remote Control User’s Guide

Copying files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Making Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Deleting Directories and Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Recording File Transfer Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Chapter 7. Using the Remote Diagnosis Action . . . . . . . 105Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Starting and Ending a Remote Diagnosis Session . . . . . . . . . . . . . . . . . . . . 106

The Remote Diagnosis Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Using Save Configuration and Stop . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Analyzing and Solving Target Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Saving Target Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Restoring Target Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Running a Diagnosis Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Customizing Web Browser and Mail Options . . . . . . . . . . . . . . . . . . . 118

Saving Remote Diagnosis Sessions for Later Use . . . . . . . . . . . . . . . . 118

Viewing a Saved Remote Diagnosis Session. . . . . . . . . . . . . . . . . . . . 119

Chapter 8. Optional Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Remote Execution Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

The CIM Browser Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Using the CIM Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

What Do You Need to Run CIM Browser? . . . . . . . . . . . . . . . . . . . . 123

Starting and Ending the CIM Browser Tool . . . . . . . . . . . . . . . . . . . . 123

CIM Browser Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

How to Build a Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

How to Clear a Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Appendix A. Frequently Asked Questions . . . . . . . . . . . . . 131Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

viii Version 3.7

Controlling and Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Appendix B. Files Changed on Installation . . . . . . . . . . . . 139Windows Controller Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Windows 95 and Windows 98 Controller File . . . . . . . . . . . . . . . . . . . . . . 139

WIN.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

OS/2 Controller File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

CONFIG.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Windows 95 and Windows 98 Target Files . . . . . . . . . . . . . . . . . . . . . . . . . 140

SYSTEM.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

WIN.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Windows 95 and Windows 98 Target Registry . . . . . . . . . . . . . . . . . . . . . . 140

Windows NT and Windows 2000 Target Registry. . . . . . . . . . . . . . . . . . . . 141

OS/2 Target Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

CONFIG.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

SYSTEM.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

OS2.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Appendix C. Command Line Interface . . . . . . . . . . . . . . . . . 143Command Line Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

wcreaterc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

wrc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

wrcinstep. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

wrcmdpcr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Appendix D. Troubleshooting and ImprovingPerformance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

ixTivoli Remote Control User’s Guide

Setting Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Contents of the Trace File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Setting Traces on the Remote Control Server . . . . . . . . . . . . . . . . . . . 155

Setting Traces on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Setting Traces on OS/2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Trace File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Logging Application Events on a Windows NT or Windows 2000Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Logging Session Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Improving Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

OS/2 Tivoli Gateway Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Appendix E. Tivoli Remote Control Messages . . . . . . . . 165Windows 95 and Windows 98 Target Messages . . . . . . . . . . . . . . . . . . . . . 165

Windows NT and Windows 2000 Target Messages . . . . . . . . . . . . . . . . . . . 170

OS/2 Target Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

General Controller Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Windows Controller Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

OS/2 Controller Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

File Transfer Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Chat Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Remote Diagnosis Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

TCP/IP Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

x Version 3.7

Preface

Tivoli Remote Control enables a system administrator using acontroller (administrator’s workstation) to perform operations on atarget (remote workstation). Controllers and targets must beendpoints running Tivoli Management Agent. For new installations,targets must be endpoints.

Tivoli Remote Control provides the following actions:

Remote Control Enables the administrator to controlkeyboard and mouse input andmonitor display output of targets.

Reboot Enables the administrator to reboottargets.

File Transfer Enables the administrator to send orreceive files or directories to or fromtargets.

Chat Enables the administrator toexchange written communicationwith the user of a target.

Remote Diagnosis Enables the administrator to analyzeand solve problems on a target.

Who Should Read This GuideThis guide is intended for system administrators who use Tivoli tomanage distributed systems. Users of the guide should have at leasta working knowledge of Tivoli Management Framework.

What This Guide ContainsThis guide shows you how to set up and use Tivoli Remote Control.

xiTivoli Remote Control User’s Guide

Conventions Used in This GuideThe guide uses several typeface conventions for special terms andactions. These conventions have the following meaning:

Bold Commands, keywords, file names, authorizationroles, URLs, or other information that you must useliterally appear in bold. Names of windows, dialogs,and other controls also appear in bold.

Italics Variables and values that you must provide appear initalics. Words and phrases that are emphasized alsoappear in italics.

Bold Italics New terms appear in bold italics when they aredefined in the text.

Monospace Code examples, output, and system messages appearin a monospace font.

Platform-Specific InformationThe following table identifies the supported platform versions knownat the time of publication. For more detailed and up-to-dateinformation, please see the Tivoli Remote Control Release Notes.

Platform Supported Versions

AIX 4.x IBM RS/600 series running AIX, Version 4.1.2, 4.1.3,4.1.4, 4.1.5, 4.2 and 4.3.

HP-UX HP9000/700 and 800 series running HP-UX, Versions10.01, 10.10, 10.20 and 11.0.

OS/2 IBM-compatible PCs 486 or higher running IBMOS/2 Warp 4.0T with Win-OS/2, or Warp Server fore-business.

Solaris Sun SPARC series running Solaris, Versions 2.5.1, 2.6and 2.7.

Windows® IBM-compatible PCs 486 or higher running Windows95 (OSR2.5) and Windows 98.

Windows NT® IBM-compatible PCs 486 or higher running MicrosoftWindows NT Version 4.0 SP4 or later.

xii Version 3.7

Platform Supported Versions

Windows 2000 IBM-compatible PCs 486 or higher running MicrosoftWindows 2000.

Tivoli Remote Control IconThe following icon represents the Tivoli RemoteControl managedresource:

The RemoteControl managed resource is created in the context of apolicy region.

Related DocumentsFurther information relating Tivoli Remote Control is available inthe following publications:

¶ Tivoli Remote Control Programming for Remote Diagnosis

¶ Tivoli Remote Control Release Notes

¶ Tivoli Management Framework Release Notes

¶ Tivoli Management Framework Planning and Installation Guide

¶ Tivoli Management Framework Reference Manual

¶ Tivoli Management Framework User’s Guide

¶ Tivoli Software Installation Service User’s Guide

¶ Tivoli Enterprise Console Manuals.

xiiiTivoli Remote Control User’s Guide

Accessing Publications OnlineThe Tivoli Customer Support Web site(http://www.tivoli.com/support/) offers a guide to support services(the Customer Support Handbook); frequently asked questions(FAQs); and technical information, including release notes, user’sguides, redbooks, and white papers. You can access Tivolipublications online at http://www.tivoli.com/support/documents/.The documentation for some products is available in PDF andHTML formats. Translated documents are also available for someproducts.

To access most of the documentation, you need an ID and apassword. To obtain an ID for use on the support Web site, go tohttp://www.tivoli.com/support/getting/.

Resellers should refer tohttp://www.tivoli.com/support/smb/index.html for moreinformation about obtaining Tivoli technical documentation andsupport.

Business Partners should refer to “Ordering Publications” for moreinformation about obtaining Tivoli technical documentation.

Note: For NetView OS/390 customers, additional support is alsoavailable on the NETVIEW CFORUM (Customer Forum)through the IBMLink system. This forum is monitored byNetView developers who answer questions and provideguidance. When a problem with the code is found, you areasked to open an official problem management record (PMR)to get resolution.

Ordering PublicationsOrder Tivoli publications online athttp://www.tivoli.com/support/Prodman/html/pub_order.html orby calling one of the following telephone numbers:

¶ U.S. customers: (800) 879-2755

¶ Canadian customers: (800) 426-4968

xiv Version 3.7

Providing Feedback about PublicationsWe are very interested in hearing about your experience with Tivoliproducts and documentation, and we welcome your suggestions forimprovements. If you have comments or suggestions about ourproducts and documentation, contact us in one of the followingways:

¶ Send e-mail to [email protected].

¶ Fill out our customer feedback survey athttp://www.tivoli.com/support/survey/.

Contacting Customer SupportIf you need support for this or any Tivoli product, contact TivoliCustomer Support in one of the following ways:

¶ Submit a problem management record (PMR) electronically fromour Web site at http://www.tivoli.com/support/reporting/. Forinformation about obtaining support through the Tivoli CustomerSupport Web site, go to http://www.tivoli.com/support/getting/.

¶ Submit a PMR electronically through the IBMLink™ system. Forinformation about IBMLink registration and access, refer to theIBM Web page at http://www.ibmlink.ibm.com.

¶ Send e-mail to [email protected].

¶ Customers in the U.S. can call 1-800-TIVOLI8(1-800-848-6548).

¶ Customers outside the U.S. should refer to the Tivoli CustomerSupport Web site athttp://www.tivoli.com/support/locations.html for customersupport telephone numbers.

When you contact Tivoli Customer Support, be prepared to providethe customer number for your company so that support personnelcan assist you more readily.

xvTivoli Remote Control User’s Guide

xvi Version 3.7

Introduction

Tivoli Remote Control is a set of tools for managing workstations ona network. The tools can be used by a system administrator at acentral location to monitor and control workstations at remotelocations. The tools are outlined in What You Can Do With TivoliRemote Control.

There are some security issues that you should consider beforeinstalling the tools. The issues are outlined in “Tivoli RemoteControl Security Control” on page 3.

What You Can Do With Tivoli Remote ControlA system administrator often needs to solve problems onworkstations far from the administrator’s location. Solving theproblem over the telephone is possible, but often difficult. Going tothe remote location is effective, but often impractical. Tivoli RemoteControl addresses this issue by giving the administrator direct accessto the remote workstation.

When using Tivoli Remote Control, the administrator’s workstationis known as a controller. The remote workstations are known astargets. From the controller, the system administrator can:

¶ Monitor the display of a target. See “Using the Remote ControlAction” on page 87.

¶ Control the keyboard and mouse input to a target. See “Usingthe Remote Control Action” on page 87.

1

1Tivoli Remote Control User’s Guide

1.In

trod

uctio

n

¶ Reboot a target. See “Using the Reboot Action” on page 87.

¶ Open a text conversation with a target. See “Using the ChatAction” on page 95.

¶ Transfer files or directories between controller and a target. See“Using the File Transfer Action” on page 101.

¶ Diagnose application problems on a target. See “Using theRemote Diagnosis Action” on page 105.

The period between starting an action and exiting the action isknown as a session.

Tivoli Remote Control ComponentsTivoli Remote Control is a client/server application. It has four maincomponents as follows:

¶ A server provides the Tivoli Remote Control functionality. Itmust be installed on a managed node.

¶ A controller is an administrator’s workstation. It runs clientsoftware that requests functions from the server. For newinstallations, controllers must be endpoints.

¶ A target is a user’s workstation. It runs client software thatrequests functions from the server. For new installations, alltargets must be endpoints. However, Version 3.7 of the serverand gateway support previous (3.6.5) versions of the targetclient.

¶ A gateway is an optional component that handles communicationbetween controllers and targets. It must be run on a managednode where the Remote Control server is installed.

For information about configuration issues, see “Configuring andStarting Tivoli Remote Control” on page 49.

See the Tivoli Management Framework Planning and InstallationGuide and the Tivoli Management Framework User’s Guide for moreinformation about managed nodes and endpoints.

2 Version 3.7

The example below shows a typical configuration. The administratoruses the Tivoli Desktop to manage the company’s distributedsystems.

Tivoli Remote Control Security ControlThere are four levels of security associated with using Tivoli RemoteControl actions.

¶ Authorization roles

¶ Default policy

Tivoli Remote Controlcontroller

with TCP/IP stack

Tivoli Remote Control targets with TCP/IP stack

Tivoli server

Tivoli gateway

IP

IP

IP

IP

Tivoli Desktop


1.In

trod

uctio

n

¶ Notice generation

¶ Log generation

Authorization rolesThese provide basic access to Tivoli Remote Control actions. Rolescan be assigned as follows:

¶ In the policy region that contains the target system.

¶ Across the Tivoli Management Region (TMR).

For more details, see “Assigning Roles” on page 52.

Default policyThis controls the behavior of the actions. You can configure thedefault policy to match your model of trust. For example:

¶ You could permit all administrators to perform any function thatTivoli Remote Control provides.

¶ A senior administrator could edit the default policy to restrictaccess to particular tools or to uses of those tools. For example,junior administrators could be barred from rebooting a targetwithout the target user’s permission.

To restrict an administrator’s control, you can use the methodsassociated with the default policy. For more information, see“Changing the Values of Activity and Display Settings” on page 55.

Notice generationThis is a message stating that a particular event occurred. It showsthe name of the event and its result. Tivoli Romote Control generatesa notice in the Tivoli Remote Control notice group when you start asession.

Log generationA log entry records the start and end times of a session, and theidentity of the user taking the session. The log entry does notinclude details of what is done during the session. For details, see“Logging Application Events on a Windows NT or Windows 2000Controller” on page 160.

4 Version 3.7

What’s New in Tivoli Remote Control Version 3.7?This latest release of Tivoli Remote Control, version 3.7, providesthe following enhancements and added features:

¶ You can now run a remote diagnosis session to diagnoseapplication problems on the target. This involves running adiagnosis pack, which consists of: a set of information, scriptsand tools.You use a diagnosis pack to investigate a specifictarget problem. The following sample diagnosis packs areprovided with Tivoli Remote Control:

v Internet Explorer

v Netscape Communicator

v Network printers

v Network

For additional information on creating diagnosis packs, see TivoliRemote Control Programming for Remote Diagnosis.

¶ You can configure the remote diagnosis session to run your owndiagnosis tools.

¶ Two diagnositic tools are provided with Tivoli Remote Control,these are Remote Command Execution and CIM Browser.

¶ You can start Tivoli Remote Control through the Web interface.

¶ You can run Tivoli Remote Control in a Terminal Serverenvironment.

¶ You can run a diagnostic script on a target and send the report tothe Tivoli Enterprise Console.


1.In

trod

uctio

n

6 Version 3.7

Installing Tivoli Remote Control

This chapter describes how to install Tivoli Remote Control.

Before you begin installation, read both of the following:

¶ “High-level Overview”. This describes the hardware andsoftware prerequisites for installation.

¶ Tivoli Remote Control Release Notes. The release notes includeany changes to the installation procedure, as well as solutions toknown problems.

High-level OverviewThere are three parts to the installation process, as follows:

1. Install Tivoli Remote Control.

2. Install Tools, Plugins, and Diagnostic Packs on gateway.

3. Manual distribution of Tools, Plugins, and Diagnostic Packs onendpoints (using the wrcinstep command).

You can install Tivoli Remote Control using any of the followinginstallation mechanisms:

¶ Tivoli Software Installation Service (SIS)

¶ Tivoli Desktop

¶ Tivoli Management Framework commands, winstall or wpatch

2


2.In

stalling

Tivoli

Rem

ote

Co

ntro

l

When you install Tivoli Remote Control for the first time, youshould check that your hardware and software matches or exceedsthe requirements shown in this section.

For information about the files that are changed by the installation,see Appendix B on page 139.

Hardware RequirementsYour workstation must have at least 32 megabytes of RAM in orderto run Tivoli Remote Control.

The following table shows the hard disk space required in megabytesby the Tivoli Remote Control target, controller, and server for thepossible operating system configurations.

It also shows the disk space needed when File Transfer, Chat, andRemote Diagnosis are installed. The Java run-time environment filesare downloaded only the first time one of these Java applications(Chat, File Transfer, Remote Diagnosis) is started.

Tivoli RemoteControlSoftware

Windows95/98

WindowsNT/2000

UNIX OS/2

Remote ControlTarget

2.0 2.0 - 2.0

Remote ControlController

1.7 1.7 - 1.6

Remote ControlServer

- 71.0 (NT only) 71.0 -

File TransferController

0.2 0.2 - 0.2

File TransferTarget

0.1 0.1 - 0.1

Chat controller 0.9 0.9 - 0.9

Chat target 0.9 0,9 - 0.9

RemoteDiagnosisConsole

1.7 1.7 - 1.7

8 Version 3.7

Tivoli RemoteControlSoftware

Windows95/98

WindowsNT/2000

UNIX OS/2

RemoteDiagnosisTarget

6.67 5.78 - -

Java run-timeenvironment

9.64 9.64 - 11.84

Software RequirementsTivoli Remote Control cannot coexist with IT Director, DCAF,Netfinity, SystemView, SMS, and other remote control softwaretypes.

Before installing Tivoli Remote Control, you must have thefollowing software installed and running:

¶ A supported operating system and protocol. See “OperatingSystems and Protocols Supported” on page 10

¶ Tivoli Management Framework 3.6.2 or later.

In addition:

¶ Tivoli Management Agent (TMA) 3.6.2 or later must be installedon all controllers and targets.

¶ To use the Tivoli Remote Control graphical user interface, TivoliDesktop must be installed.

¶ To use the Tivoli Remote Control Web interface, a browser mustbe installed.

¶ To use the Remote Diagnosis target on Windows 95, Winsock2must be installed on the target. Winsock2 can be downloadedfrom:http://www.microsoft.com/windows95/downloads/contents/WUAdminTools/S_WUNetworkingTools/W95Sockets2

¶ To use the Remote Diagnosis target on Windows NT 4.0, youmust set the Primary DNS suffix on the target. If this is not


2.In

stalling

Tivoli

Rem

ote

Co

ntro

l

done, the Remote Diagnosis target will not start. To set thePrimary DNS suffix from the Windows NT 4.0 desktop, do thefollowing:

1. Right-click the Network Neighbourhood icon

2. Click the Properties option. The Network window appears

3. Select the Protocolstab

4. Double click on TCP/IP Protocol. The Microsoft TCP/IPProperties window appears

5. Select the DNS tab

6. Enter the domain name in the Domain field

7. Click OK

¶ To use the Remote Diagnosis target on Windows 2000, you mustset the Primary DNS suffix on the target. If this is not done, theRemote Diagnosis target will not start. To set the Primary DNSsuffix from the Windows 2000 desktop, do the following:

1. Right-click the My Computer icon

2. Click the Properties option

3. Click the Network Identification tab

4. Click the Properties button

5. Click the More button

6. Complete the Primary DNS suffix of this computer box

7. Click OK

Operating Systems and Protocols SupportedThe following table lists the Tivoli Remote Control Actions that aresupported by various operating systems:

RemoteControlSoftware

Windows UNIX OS/2

95/98 NT/2000 NT TS

Target U U U

Controller U U U U

10 Version 3.7

RemoteControlSoftware

Windows UNIX OS/2

95/98 NT/2000 NT TS

Server U (NTonly)

U U

Gateway U (NTonly)

U

File TransferTarget

U U U

File TransferController

U U U U

Chat Target U U U

Chat Controller U U U U

RemoteDiagnosisconsole

U U U U

RemoteDiagnosistarget

U U

To know where packs, tools and plugins should be installed see“Installing Tools, Plugins, and Diagnosis Packs” on page 18.

You can connect a controller to targets that run any of the followingoperating systems, provided the corresponding protocols are installedon the target:

Operating System Protocol

OS/2 Warp 4.0 orOS/2 Warp Serverfor e-business

IBM TCP/IP 4.2 for OS/2 or later.

Windows 2000,Windows NT 4.0,Windows 95 orWindows 98

TCP/IP stack built in.


2.In

stalling

Tivoli

Rem

ote

Co

ntro

l

For more information about the supported TCP/IP stack, refer to theTivoli Management Framework Release Notes.

TCP/IP ConnectionThe following table shows the software you need to use TivoliRemote Control with a TCP/IP connection:

Type Operatingsystem

Tivoli product Protocol

Target (seenote)

All Tivoli Management Agent TCP/IP stack

Controller All Desktop plus TivoliManagement Agent

TCP/IP stack

For more information about the supported TCP/IP stack, refer to theTivoli Management Framework Release Notes.

Note: Remote Diagnosis Action runs only on Windows 95,Windows 98, Windows NT, and Windows 2000

Product InstallationYou can install Tivoli Remote Control in the following ways:

¶ The Tivoli Software Installation Service (SIS) is the mostreliable way to install a Tivoli product. See “Installing TivoliRemote Control with SIS” on page 14.

¶ With the Tivoli Desktop. For more details see “Installing TivoliRemote Control from the Tivoli Desktop” on page 14.

¶ With the Tivoli Management Framework command, winstall.For more details see “Installing Tivoli Remote Control Using thewinstall Command” on page 16.

If you are upgrading the product from a previous version, see“Product Upgrade” on page 21.

12 Version 3.7

Components AvailableThe following table lists the components of Tivoli Remote Controlthat you can install.

Component name Index File Product Tag

Tivoli Remote ControlServer 3.7

RC_ALI RC_ALI

Internet-Explorer DiagnosisPack

INTERNET RCL_DPack_Internet-Explorer

Netscape-CommunicatorDiagnosis Pack

NETSCAPE RCL_DPack_Netscape-Communicator

Diagnosis Pack toconfigure the NetworkOptions

NETWORK RCL_DPack_Network

Remote Diagnosis toconfigure the PrintersOptions

PRINTERS RCL_DPack_Printers

Tivoli CIM BrowserPlugIn for Tivoli RemoteControl

CIMBROWS RCL_PlugIn_CIMBrowser

Tivoli CIM Browser Toolfor Tivoli Remote Control

CIM_BROW RCL_Tool_CIM_Browser

Tivoli Remote CommandExecution Tool for TivoliRemote Control

REMOTE_C RCL_Tool_Remote_Command_Execution

The installation images are in the following directories of thecompact disc (CD).

Image Name CD Directory

Tivoli Remote Control Server 3.7 \RC

trdbaroc.tar ReadMe.txt \TEC

Tivoli CIM Browser Tool for Tivoli RemoteControl

\TOOLS\CIM\TOOL

Tivoli CIM Browser PlugIn for TivoliRemote Control

\TOOLS\CIM\PLUGIN


2.In

stalling

Tivoli

Rem

ote

Co

ntro

l

Image Name CD Directory

Tivoli Remote Command Execution Toolfor Tivoli Remote Control

\TOOLS\RCE\TOOL

Internet-Explorer Diagnosis Pack \PACKS \Explorer

Netscape-Communicator Diagnosis Pack \PACKS \Netscape

Diagnosis Pack to configure the NetworkOptions

\PACKS\Network

Remote Diagnosis to configure the PrintersOptions

\PACKS\NetPrint

Installation OptionsThere are no installation options for Tivoli Remote Control.

Installing Tivoli Remote Control with SISThe basic procedure for using the Tivoli Software InstallationSystem (SIS) to install the components of the Tivoli Remote Controlproduct is as follows:

1. Import the product images into the SIS depot.

2. Select the components to be installed.

3. Select the machines where each component is to be installed.

4. Click the Install button.

For detailed information on using SIS to install the components,refer to the Tivoli Software Installation Service User’s Guide.

Installing Tivoli Remote Control from the TivoliDesktop

The procedure for installing the components of the Tivoli RemoteControl product is as follows:

1. From the Desktop menu, select Install > Install Product todisplay the Install Product dialog.

If the Tivoli Remote Control components are not listed underSelect Product to Install, proceed to step 2. Otherwise, skip tostep 3.

14 Version 3.7

2. Click Select Media to display the File Browser dialog.

File Browser enables you to identify or specify the path to theinstallation media.

¶ If you know the path to the CD-ROM image:

a. Enter the full path in the Path Name field.

b. Click Set Path to change to the specified directory.

c. Click Set Media & Close to save the new media pathand return to Install Product. The dialog now lists theproducts that are available for installation.

¶ If you do not know the exact path to the CD-ROMimage:

a. From Hosts, choose the host on which the install mediais mounted. This updates Directories to list thedirectories of the host you chose.

b. From Directories, choose the directory that contains theinstall media.

c. Click Set Media & Close to save the new media pathand return to Install Product. The dialog now lists theproducts that are available for installation.

3. Select the components from the Select Product to Installscrolling list.

4. To specify the clients on which the selected component will beinstalled, click the arrow keys to move client names between theClients to Install On and Available Clients.

Note: An error message is displayed if you attempt to install aTivoli Remote Control component on an invalid machinetype.

5. Click Install to install the component.

You will be prompted with a Product Install dialog. This liststhe operations that will take place during the installation. Thisdialog also warns of any problems that you may want to correctbefore you install the component.


2.In

stalling

Tivoli

Rem

ote

Co

ntro

l

6. Click Continue Install to begin the installation. The ProductInstall dialog presents status information during the installation.

When the installation is complete, Product Install returns acompletion message.

7. Click Close to return to the Install Product dialog.

8. If you have downloaded the target or controller component to anOS/2 endpoint workstation, you must reboot the workstationlocally to complete the installation.

Installing Tivoli Remote Control Using the winstallCommand

The following example command installs a Tivoli Remote Controlcomponent on a managed node. Run winstallwinstall -c cdrom_dir -s product_server -i fileCreatePaths=1 node1 node2

where:

-c cdrom_dirSpecifies the path to the CD-ROM image.

-s product_serverSpecifies the name of the managed node where theCD-ROM image of the Tivoli Remote Control applicationresides.

-i file Specifies the index file from which the Tivoli RemoteControl components are installed. The file argument is thefollowing:

RC_ALI Installs the Tivoli Remote Control server andgateway components on the Tivoli server orother managed nodes in the local TMR.

INTERNET Installs the Internet Explorer pack template.

NETSCAPE Installs the Netscape pack template.

NETWORK Installs the network configuration packtemplate.

PRINTERS Installs the network printer pack template.

16 Version 3.7

This pack is designed for use only withWindows NT and Windows 2000.

CIMBrows Installs the CIM Browser plugin. You needto install this component to work with theCIM Browser tool.

CIM_BROW Installs the CIM Browser Tool. You need toinstall this component to work with the CIMBrowser tool.

REMOTE_C Installs the Remote Command Executiontool.

node1 node2Specifies the names of the managed nodes on which toinstall the server if the node protocol is TCP. If no node isspecified, the installation runs on all nodes of the currentregion.

For additional information on this command, type winstall from acommand prompt.

See “Components Available” on page 13 for the name of the indexfile.

For detailed information on the winstall command, see the TivoliManagement Framework Reference Guide.

Installing on EndpointsYou do not need to install Remote Control software manually onendpoints. When you start a Remote Control session for the firsttime from an endpoint, through either the desktop or using the wrccommand (as described in “wrc” on page 145) or Web interface, thecontroller software is installed on that endpoint. If the target is alsoan endpoint, the target software is installed on that endpoint. Thesame kind of installation occurs when you start the File Transfer,Chat or Remote Diagnosis session for the first time.


2.In

stalling

Tivoli

Rem

ote

Co

ntro

l

If you have downloaded the target or controller components to anOS/2 endpoint workstation, you must reboot the workstation locallyto complete the installation.

If, in a large environment, you need to install the software on severalendpoints at the same time, you can use the wrcinstep command asdescribed in “wrcinstep” on page 150.

Notes:

1. The first time you attempt a Remote Control action, thefollowing message appears on the controller side:Tivoli Remote Control binaries were installed/updated on endpoint<endpoint-label>. It needs to be rebooted.

2. If you want to install the controller on an endpoint that is also amanaged node and whose label is different from the host name,you must create an instance of the class controller by using thefollowing command from a bash shell:$BINDIR/TME/PCREMOTE/createcontroller.sh <host_name> <controller_label>

where: <host_name> must be the controller host name.<controller_label> must be the controller label.

3. If you want to delete an instance of the class controller use thefollowing command from a bash shell:$BINDIR/TME/PCREMOTE/deletecontroller.sh <host_name>

where: <host_name> must be the controller host name.

Installing Tools, Plugins, and Diagnosis PacksInstruments are available to fully exploit Remote Diagnosis Actions.These should be downloaded to the gateway, using either the TivoliDesktop or the winstall command (see the Tivoli ManagementFramework Reference Guide). After downloading, use the wrcinstepcommand (see “wrcinstep” on page 150) to install the instruments intheir appropriate locations.

18 Version 3.7

The following table shows where each item should be installed:

Type Items

Controller Plugins

Target Tools

Diagnosis Packs

For example, to install Diagnosis Packs on the target use thecommand:wrcinstep -t k -l target_endpoint_label

To install Tools on the target use the command:wrcinstep -t t -l target_endpoint_label

To install Plugins on the controller use the command:wrcinstep -c p -l controller_endpoint_label

TEC IntegrationTivoli Remote Control Version 3.7 is supplied with the ability tointegrate the Remote Diagnosis action with the Tivoli EnterpriseConsole (TEC).

To configure the TEC, do the following:

1. Enter the \TEC\trdbaroc.tar file and copy the file\TEC\trd.baroc from the Tivoli Remote Control CD-ROM to adirectory on the TEC server

2. Configure, compile, and load the rule base associated to the trdevent. To do so, run the following commands from a Tivolienvironment:

a. wcrtrb -d <directory_name> <rule_base_name>

b. wcprb Default <rule_base_name>

c. wimprbclass trd.bar <rule_base_name>

d. wcomprules <rule_base_name>


2.In

stalling

Tivoli

Rem

ote

Co

ntro

l

e. wloadrb <rule_base_name>

From the TEC Server GUI, add:

a. A new source by setting the source name to RemoteDiagnosis

b. A new filter by setting the Event Class to Trd_event and theSource name to Remote Diagnosis

For more information, see the Tivoli Enterprise Console User’sGuide.

To send Tivoli Remote Diagnosis events to Tivoli EnterpriseConsole, do the following:

1. Make sure that the Remote Diagnosis session on the targetmachine you want to use is closed.

2. Enter the following command line:wrc <RemoteControlName> trd2tec @Endpoint:<endpoint_name>-U:<pack_name>[/<perlscript>[?parm1[&parm2[...&parmn]]]]

where:

? inserts the parameters

& is the separator between parameters

parmn is the generic parameter. It has the formatparmn=value.

For further information on the wrc command, see Appendix C.

The secure events related to the specified pack are displayed in theTivoli Enterprise Console.

Examples of the -U parameter:

1. wrc RC_37 trd2tec @Endpoint:lab80"-U:/test/print_parameters.pl?String=CICCIO+PLUTO&Sint32=56525"

This invokes a specific Perl script with parameters String andSint32.

20 Version 3.7

2. wrc RC_37 trd2tec @Endpoint:lab80″-U:<pack_name>[/<perlscript>]″

This invokes a specific Perl script without any parameters

3. wrc RC_37 trd2tec @Endpoint:lab80 ″-U:<pack_name>″

This invokes the root script of the diagnosis pack. If previouslyprotected, it also invokes the Verify script of the vital objects.

After the integration command has been run, each diagnosis packreport message is converted into a TEC event.

Product UpgradeIf you wish you can use SIS to upgrade Tivoli Remote Control. Forfurther details see Tivoli Software Installation Service User’s Guide.

For compatibility with previous versions, targets can be any resourcesupported by previous (3.6.5) versions of Tivoli Remote Control.

InteroperabilityTivoli Remote Control Version 3.7 supports targets at Version 3.6.5,and later.

For a smooth migration of targets towards this release, you need toupgrade Tivoli Remote Control Server to Version 3.7 on all managednodes in the TMR.

When you upgrade this component, you have the following situation:

¶ Tivoli Remote Control Version 3.6.5 installed on target andcontroller endpoints of the migrated TMR, migratesautomatically to Tivoli Remote Control Version 3.7.

¶ Tivoli Remote Control Targets Version 3.6.5 installed on PCmanaged nodes will work correctly.

¶ Tivoli Remote Control Targets Version 3.6.5 installed onmanaged nodes will not work. To solve this, install endpoints onthe required managed node workstations. In this way the first


2.In

stalling

Tivoli

Rem

ote

Co

ntro

l

time you start a session between two workstations, the targetsand controllers of Tivoli Remote Control Version 3.7 areautomatically installed.

Tivoli Remote Control Targets earlier than Version 3.6.5 are notsupported.

Note: If you migrate your TMR server to Tivoli Remote ControlServer Version 3.7 while you maintain the interconnectedTMR server to Tivoli Remote Control Server Version 3.6.5,you can connect a controller with Tivoli Remote ControlVersion 3.7 to any target (endpoint, managed node, PCmanaged node) that has Tivoli Remote Control Version 3.6.5.

Tivoli Remote Control cannot coexist with IT Director, DCAF,Netfinity, SystemView, SMS, and other remote control softwaretypes.

Upgrading Tivoli Remote Control from the TivoliDesktop

Migration of Tivoli Remote Control Server, Tivoli Remote ControlController, Tivoli Remote Control Target components to TivoliRemote Control Version 3.7 requires one of the following items:

¶ Uninstalling these three components of Tivoli Remote ControlVersion 2.1, 2.1.1, 3.6 or 3.6.1

or,

¶ Migrating to Remote Control Version 3.6.5 through the followingpath: 2.1->2.1.1->3.6 or 3.6.1->3.6.5

Notes:

1. If you decide to migrate the endpoints from Remote ControlVersion 3.6 or 3.6.1 to Remote Control Version 3.6.5, you donot update the Remote Control existing binaries, but youinstall Remote Control Version 3.6.5 on a different hardcodedpath.

2. When you are upgrading any Remote Control componentfrom Version 3.6 or 3.6.1 to Version 3.6.5 on your

22 Version 3.7

workstation, you must also upgrade all other Remote Controlcomponents installed on the same workstation from Version3.6 or 3.6.1 to Version 3.6.5.

3. If you have the Tivoli Remote Control Controller or TivoliRemote Target components installed on managed nodes andPC managed nodes and you want to maintain theseworkstations as controllers or targets, do the following:

a. Migrate Remote Control Controller and Remote ControlTarget components to Version 3.6.5.

b. Install endpoints on these workstations. In this way thefirst time you start a session between two workstations,the targets and controllers of Tivoli Remote ControlVersion 3.7 are automatically installed.

When you have Tivoli Remote Control Version 3.6.5 installed onyour machines and you want to migrate to Tivoli Remote ControlVersion 3.7, perform the following steps:

1. From the Desktop menu, select Install > Install Patch... todisplay the Install Patch dialog.

2. If the Tivoli Remote Control components are not listed underSelect Patch to Install, click Select Media to identify the pathof the installation media.

3. Select the following Tivoli Remote Control component fromthe Select Patch to Install list:

Server Upgrade 3.7Upgrades the Tivoli Remote Control server andthe Tivoli Remote Control gateway on theTivoli server or other managed nodes in thelocal Tivoli Management Region (TMR).

4. To install the new components see “Installing Tools, Plugins,and Diagnosis Packs” on page 18.

5. To specify the clients on which the selected component will beupgraded, click the arrow keys to move client names betweenthe Clients to Install On and Available Clients.


2.In

stalling

Tivoli

Rem

ote

Co

ntro

l

6. Click Install to install the component patch.

The Patch Install dialog lists operations that will take placeduring the installation. It also warns of problems that you maywant to correct before you install the component patch.

7. Select Continue Install to begin the installation. The PatchInstall dialog displays the status during the installation.

When the installation is complete, Patch Install returns acompletion message.

8. Click Close to return to the Install Patch dialog.

9. Repeat steps 3-8 until you have completely upgraded TivoliRemote Control. You must upgrade the server and the gatewaycomponents.

10. Restart each PC on which you installed the Tivoli RemoteControl target patch in order to load new device drivers intosystem memory. You can use Tivoli Remote Control to do thisif you have fully configured the resources and the roles for theproduct. See the Remote Control User’s Guide for moreinformation.

11. On a Windows 95 or Windows 98 target, check that the valueof CommandEnvSize under [NonWindowsApp] section in thesystem.ini file is set to 2048.

Uninstalling the ProductTivoli Management Framework provides a command to uninstallTivoli applications from a specified managed node or from the entireTMR. The wuninst command is a wrapper script that invokesproduct-specific uninstall scripts.

For detailed information on the wuninst command, refer to theTivoli Management Framework Reference Manual.

Uninstalling the Server and Remote Control GatewayYou can uninstall the Tivoli Remote Control server from anymanaged node in your environment or from the TMR. To do this,use the wuninst command with an application-specific tag.

24 Version 3.7

Note: The wuninst command must be run from a bash shell if youuse Windows NT.

The syntax of the command is as follows:wuninst comp_tag node_name [–rmfiles][-all]

where:

comp_tag Specifies the tag of the Tivoli Remote Controlcomponent that you want to uninstall. It must be thefollowing:

RC_ALIUninstalls the Tivoli Remote Control server.

node_name Specifies the node from which the component isuninstalled. If node_name is the TMR (TivoliManaged Region) server and the -all option isspecified, the application is removed from the entireTMR. You will be prompted with a confirmationmessage before the application is removed from theTMR.

–rmfiles Specifies that all associated files are removed,regardless of whether they are shared files.

-all If this option is used when the node_name is theTMR server, the application is removed from theentire TMR.

The default behavior without the –rmfiles option is to remove thedatabase entries for only the specified node. If the node is the TMRserver, using this option removes all database objects.

Uninstalling Tools, Plugins, and PacksYou can uninstall Remote Control Packs, Tools, and Plugins from amanaged node. To do this, use the wuninst command.

Note: The wuninst command must be run from a bash shell if youuse Windows NT.

The syntax of the command is as follows:


2.In

stalling

Tivoli

Rem

ote

Co

ntro

l

wuninst comp_tag node_name [–rmfiles] [-all]

where:

comp_tag Specifies the tag of the Tivoli Remote Controlcomponent that you want to uninstall. It must be thefollowing:

RCL_DPack_Internet-ExplorerUninstalls the Internet Explorer packtemplate.

RCL_DPack_Netscape-CommunicatorUninstalls the Netscape packtemplate.

RCL_DPack_NetworkUninstalls the network configurationpack template.

RCL_DPack_PrintersUninstalls the network printer packtemplate.

RCL_PlugIn_CIMBrowserUninstalls the CIM Browser plugin.

RCL_Tool_CIM_BrowserUninstalls the CIM Browser tool.

RCL_Tool_Remote_Command_ExecutionUninstalls the Remote CommandExecution tool.

node_name Specifies the node from which the component isuninstalled. If node_name is the TMR (TivoliManaged Region) server and the -all option isspecified, the application is removed from the entireTMR. You will be prompted with a confirmationmessage before the application is removed from theTMR.

–rmfiles Specifies that all associated files are removed,regardless of whether they are shared files.

26 Version 3.7

-all If this option is used when the node_name is theTMR server, the application is removed from theentire TMR.

The default behavior without the –rmfiles option is to remove thedatabase entries for only the specified node. If the node is the TMRserver, using this option removes all database objects.

Uninstalling Controller and TargetThis section describes how to uninstall a Tivoli Remote Controlcontroller or target from endpoints.

Uninstalling the ControllerTo uninstall a Tivoli Remote Control controller, follow the procedurethat relates to the operating system of the controller.

Windows NT or Windows 2000 EndpointPerform the following steps locally on the endpoint:

1. If you wish to uninstall the file transfer and chat features, runregedit. The Registry Editor window appears:

a. From HKEY_LOCAL_MACHINEselect SOFTWAREandthen Tivoli.

b. Delete the Remote Control Controller entry.

c. Change the following entry:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services Delete the TME10RC key.

2. Delete the EQNRSMAI.INI file from the %WINDIR%directory.

3. Restart the machine.

4. Delete the RCSERV.EXE (only if you are uninstalling the wholeTivoli Remote Control product) file from the %WINDIR%directory.


2.In

stalling

Tivoli

Rem

ote

Co

ntro

l

5. Delete the following files from the<LCF_dir>\PCREMOTE\w32-ix86\CTL directory (where<LCF_dir> is the directory where the Tivoli Management Agenthas been installed):EQNRSMAI.EXEEQNRSMGR.DLLEQNWTO.DLLMFC40.DLLMSVCRT.DLLMSVCRT40.DLLLOCALE\*.*

6. Delete the following files from the directory<LCF_dir>\PCREMOTE\w32-ix86\LEVELS:RCSERV.LVLREGCTL.LVLRC_CTL.LVL

7. If you are uninstalling the whole Tivoli Remote Control product,delete the following directory:<LCF_dir>\DAT\<n>\cache\bin\w32-ix86\TME\ PCREMOTEwhere:

<n> is the integer value that specifies the endpoint connectionnumber

Windows 95 or Windows 98 EndpointPerform the following steps locally on the endpoint:

1. If you are also uninstalling the file transfer and chat features, runregedit. The Registry Editor window appears.

a. From HKEY_LOCAL_MACHINE select SOFTWARE andthen Tivoli.

b. Delete the Remote Control Controller entry.

2. Delete the following file from the %WINDIR% directory:EQNRSMAI.INI

3. Reboot the workstation.

28 Version 3.7

4. Delete the following files from the directory<LCF_dir>\PCREMOTE\win95\CTL (where <LCF_dir> is thedirectory where the Tivoli Management Agent has beeninstalled):EQNRSMAI.EXEEQNRSMGR.DLLEQNWTO.DLLMFC40.DLLMSVCRT.DLLMSVCRT40.DLLLOCALE\*.*

5. Delete the following files from the directory<LCF_dir>\PCREMOTE\win95\LEVELS:REGCTL.LVLRC_CTL.LVL

6. If you are uninstalling the whole Tivoli Remote Control product,delete the directory<LCF_dir>\DAT\<n>\cache\bin\win95\TME\ PCREMOTEwhere:

<n> is the integer value that specifies the endpointconnection number

OS/2 EndpointPerform the following steps locally on the endpoint:

1. In the CONFIG.SYS file remove the following lines:CALL=<product_dir>\EQNINNEW.EXECALL=<product_dir>\EQNKCTLD.EXESET RCCTLPATH=<product_dir>

where:

<product_dir> is the directory where Tivoli Remote Control hasbeen installed

2. Remove the string <product_dir> from the following entries inthe CONFIG.SYS file:LIBPATH=SET PATH=SET DPATH=SET HELP=


2.In

stalling

Tivoli

Rem

ote

Co

ntro

l


4. Delete the following files from the<LCF_dir>\PCREMOTE\os2-ix86\CTL directory (where<LCF_dir> is the directory where the Tivoli Management Agenthas been installed):EQNRSMAI.EXEEQNCTRBM.DLLEQNINCON.DLLEQNKCDWN.DLLEQNKCD.NEWEQNKRAS.DLLEQNKCTR.NEWEQNKMSG.DLLEQNKSCLG.DLLEQNKSVGR.DLLEQNCM03.DLLEQNCM04.DLLEQNKDIRP.DLLEQNKWC.DLLEQNQUE.NEWEQNRBCRP.DLLEQNKCTKB.NEWEQNKCTLD.EXEEQNINNEW.EXEEQNSYNCH.DLLEQNH.MSGEQN.MSGEQNKSCLG.HLPLOCALE\*.*

5. From the directory <LCF_dir>\PCREMOTE\os2-ix86\LEVELSdelete the following files:CONFIGC.LVLINNEWC.LVL

6. If you are uninstalling the whole Tivoli Remote Control product,delete the following directory:<LCF_dir>\DAT\<n>\cache\bin\os2-ix86\TME\ PCREMOTEwhere:


30 Version 3.7

Uninstalling the TargetTo uninstall a Tivoli Remote Control target, follow the procedurethat relates to the operating system of the target.

Windows NT or Windows 2000 EndpointTo uninstall a Tivoli Remote Control target, perform the followingsteps locally on the endpoint:

1. Run regedit. The Registry Editor window appears.

2. If you are also uninstalling the file transfer and chat features,from HKEY_LOCAL_MACHINE select SOFTWARE andthen Tivoli. Delete the Remote Control Target entry.

3. Change the following entries:

¶ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services Delete the KeyEx2 key.

Note: If you have installed the Tivoli Remote Control targetas a patch, select Control Panel > Devices to displaythe Devices window. Then check that the status of theTivoli Remote Control Keyboard Filter is set toStarted, and Startup is set to Automatic.

¶ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services Delete the MouEx2 key.

Note: If you have installed the Tivoli Remote Control targetas a patch, select Control Panel > Devices to displaythe Devices window. Then check that the status of theTivoli Remote Control Pointer Filter is set to Started,and Startup is set to Automatic.

¶ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services Delete the TGrab key.

¶ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services If you are uninstalling the whole Tivoli RemoteControl product, delete the TME10RC key (only if you arealso uninstalling the controller).

4. Restart the machine.


2.In

stalling

Tivoli

Rem

ote

Co

ntro

l

5. Delete the following files:

a. From the %WINDIR% directory:EQNRCMAI.INIRCSERV.EXE

(only if you are uninstalling the whole Tivoli Remote Controlproduct)

b. From the %WINDIR%\SYSTEM32 directory:VDDFIFO.DLL

c. From the %WINDIR%\SYSTEM32\DRIVERS directory:KEYEX2.SYSMOUEX2.SYSTGRAB.SYS

6. Delete the following files from the directory:<LCF_dir>\PCREMOTE\w32-ix86\TGT (where <LCF_dir> isthe directory in which the Tivoli Management Agent has beeninstalled):EQNTC.DLLNTREBOOT.EXE (for reboot action)VDD.DLLVDDFIFO.DLLVDDHOOK.DLLEQNRCDKY.DLLEQNRCDMO.DLLEQNRCGVD.DLLEQNRCMAI.EXEFLT32.DLLEQNTFC32.DLLMFC40.DLLMSVCRT.DLLMSVCRT40.DLLEQNHOOK.DLLEQNDSS.EXEKEYEX2.SYSMOUEX2.SYSTGRAB.SYSLOCALE\*.*

7. Delete the following files from the directory<LCF_dir>\PCREMOTE\w32-ix86\LEVELS:RC_TGT.LVLRCSERV.LVLMOUEX2.LVL

32 Version 3.7

KEYEX2.LVLTGRAB.LVLVDDFIFO.LVLREGTGT.LVLEQNRCG40.LVLDUMMY.LVL

8. If you are uninstalling the whole Tivoli Remote Control product,delete the following directory:<LCF_dir>\DAT\<n>\cache\bin\w32-ix86\TME\ PCREMOTEwhere:


Windows 95 or Windows 98 EndpointTo uninstall a Tivoli Remote Control target, perform the followingsteps locally on the endpoint:

1. Delete the following entry from the [386Enh] section of the%WINDIR%\SYSTEM.INI file:device=VDCFD95.386


3. Delete the following files from the directory<LCF_dir>\PCREMOTE\win95\TGT (where <LCF_dir> is thedirectory in which the Tivoli Management Agent has beeninstalled):EQNTC.DLL16REBOOT.EXE (for the reboot action)EQNDSS.EXEEQNKRN.DLLEQNRCMAI.EXEEQNWNOV.DLLEQNWTCP.DLLEQNWTPER.DLLEQNWTROU.DLLEQNWUSH.EXEEQNWUSH2.DLLFLT16.DLLTLI_SPX.DLLTLI_WIN.DLLEQNRCTSL.EXETESTIT.BATTHK16.DLL


2.In

stalling

Tivoli

Rem

ote

Co

ntro

l

THK32DLL.DLLVDCFD95.386EQNTFC.DLLLOCALE\*.*

4. From the %WINDIR%\SYSTEM directory delete the followingfile:VDCFD95.386

5. From the directory <LCF_dir>\PCREMOTE\win95\LEVELSdelete the following files:RC_TGT.LVLVDCFD95.LVLDUMMY.LVL

6. If you are uninstalling the whole Tivoli Remote Control product,delete the following directory:<LCF_dir>\DAT\<n>\cache\bin\win95\TME\ PCREMOTEwhere:


OS/2 EndpointTo uninstall a Tivoli Remote Control target, perform the followingsteps locally on the endpoint:

1. Remove the following entries from the CONFIG.SYS file:CALL=<product_dir>\EQNINNEW.EXEDEVICE=<product_dir>\EQNRCSHD.EXECALL=<product_dir>\EQNRCLD.EXEDEVICE=<product_dir>\EQNVKBD.SYSSET RCTGTPATH=<product_dir>

where:

<product_dir> is the directory where Tivoli Remote Control hasbeen installed

2. Remove the string <product_dir> from the following entries inthe CONFIG.SYS file:LIBPATH=SET DPATH=SET PATH=SET HELP=

34 Version 3.7

3. Delete the value of the Text keyword from the following entriesin the OS2.INI file: (The EDITINI.EXE program can be usedfor editing the OS2.INI file.)Application name: PM_ED_HOOKSKey name: MODULENAMEText: EQNPMGREApplication name: SYS_DLLSKey name: LoadText: EQNCLHOT

4. If the Win-OS2 support is installed on the workstation, edit theC:\os2\mdos\winos2\system.ini file and modify the value of theOS2SHIELD= entry from:OS2SHIELD=<product_dir>\EQNSEADA.EXE

to:OS2SHIELD=WINSHELD.EXE


6. Delete the following files from the directory<LCF_dir>\PCREMOTE\os2-ix86\TGT (where:<LCF_dir> isthe directory in which the Tivoli Management Agent has beeninstalled):EQNTCOS2.EXEREBOOT.EXE (for the reboot action)EQNCM03.DLLEQNCM04.DLLEQNRCMAI.EXEFLTOS2.DLLEQNBKG.DLLEQNTGMAI.DLLEQNPMGRE.NEWEQNKMSG.DLLEQNSEADA.EXEEQNVKBD.SYSEQNKRAS.DLLEQNRCKB.NEWEQNSEAMG.EXEEQNPMST.EXEEQNRCUT.NEWEQNINNEW.EXEEQN.MSGEQNH.MSGEQNLLNK.DLLEQNSEAFL.DLL


2.In

stalling

Tivoli

Rem

ote

Co

ntro

l

EQNCTBOX.DLLEQNSYNCH.DLLEQNTDSH.NEWEQNRCVI.NEWEQNUT.DLLEQNRCLD.EXEEQNCLHOT.NEWEQNKDIRP.DLLEQNRCSHD.EXESTRTNWC.EXEEQNPMST0.EXEEQNTOPM.EXEEQNKCD.NEWEQNKSVGR.DLLLOCALE\*.*

7. Delete the following files from the directory<LCF_dir>\PCREMOTE\os2-ix86\LEVELS:RC_TGT.LVLCONFIGT.LVLOS2INI.LVLSYSINI.LVLINNEWT.LVLDUMMY.LVL

8. If you are uninstalling the whole Tivoli Remote Control product,delete the following directory:<LCF_dir>\DAT\<n>\cache\bin\os2-ix86\TME\ PCREMOTEwhere:


Uninstalling File Transfer, Chat, and RemoteDiagnosis Console

You can uninstall the file transfer, chat and remote diagnosis consolefeatures, together or separately. To uninstall them together follow theprocedure that relates to the operating system of your workstation.

Windows NT 4.0 or Windows 2000 WorkstationTo uninstall file transfer, chat, and remote diagnosis together,perform the following steps locally on the workstation.

1. Delete the following directories:

36 Version 3.7

<LCF_dir>\PCREMOTE\win32-ix86\classes<LCF_dir>\PCREMOTE\win32-ix86\jre<LCF_dir>\PCREMOTE\win32-ix86\cat

where:

<LCF_dir> is the directory where the Tivoli ManagementAgent has been installed

2. Delete the following files, if present, from the<LCF_dir>\PCREMOTE\win32-ix86\LEVELS directory:FT_CTL.LVLFT_TGT.LVLCH_CTL.LVLCH_TGT.LVLRD_CTL.LVLRD_TGT.LVLJAR.LVLJRE.LVLDUMMY.LVL

3. Delete the following file: <LCF_dir>\PCREMOTE\win32-ix86\CTL\TSEProp.ini

Windows 95 or Windows 98 WorkstationTo uninstall file transfer, chat, and remote diagnosis together,perform the following steps locally on the workstation:

1. Delete the following directories:<LCF_dir>\PCREMOTE\win95\classes<LCF_dir>\PCREMOTE\win95\jre<LCF_dir>\PCREMOTE\win95\cat

where:


2. Delete the following files, if present, from the<LCF_dir>\PCREMOTE\win95\LEVELS directory:FT_CTL.LVLFT_TGT.LVLCH_CTL.LVLCH_TGT.LVLRD_CTL.LVL


2.In

stalling

Tivoli

Rem

ote

Co

ntro

l

RD_TGT.LVLJAR.LVLJRE.LVLDUMMY.LVL

3. Delete the following file:<LCF_dir>\PCREMOTE\win95\CTL\TSEProp.ini

OS/2 WorkstationTo uninstall file transfer, chat, and remote diagnosis together,perform the following steps locally on the workstation:

1. Delete the following directories:<LCF_dir>\PCREMOTE\os2-ix86\classes<LCF_dir>\PCREMOTE\os2-ix86\jre118<LCF_dir>\PCREMOTE\os2-ix86\cat

where:


2. Delete the following files, if present, from the<LCF_dir>\PCREMOTE\os2-ix86\LEVELS directory:FT_CTL.LVLFT_TGT.LVLCH_CTL.LVLCH_TGT.LVLRD_CTL.LVLRD_TGT.LVLJRE.LVLJAR.LVLDUMMY.LVL

3. Delete the following file: <LCF_dir>\PCREMOTE\os2-ix86\CTL\TSEProp.ini

4. Delete the file: <LCF_dir>\PCREMOTE\os2-ix86\CTL\EQNSPU.DLL if it exists.

5. Delete the file: <LCF_dir>\PCREMOTE\os2-ix86\TGT\EQNSPU.DLL if it exists.

To uninstall file transfer, chat and remote diagnosis consoleseparately, read the next sections.

38 Version 3.7

Uninstalling File TransferTo uninstall the file transfer feature, follow the procedure that relatesto the operating system of your workstation:

Windows NT 4.0 or Windows 2000 WorkstationTo uninstall the file transfer feature, perform the following stepslocally on the workstation:

1. Delete the following files from the<LCF_dir>\PCREMOTE\w32-ix86\classes directory:ft_ctl.jarft_tgt.jar

where:


2. Delete the following files, if present, from the<LCF_dir>\PCREMOTE\w32-ix86\LEVELS directory:FT_TGT.LVLFT_CTL.LVL

Windows 95 or Windows 98 WorkstationTo uninstall the file transfer feature, perform the following stepslocally on the workstation:

1. Delete the following files from the<LCF_dir>\PCREMOTE\win95\classes directory:ft_ctl.jarft_tgt.jar

where:


2. Delete the following files, if present, from the<LCF_dir>\PCREMOTE\win95\LEVELS directory:FT_TGT.LVLFT_CTL.LVL


2.In

stalling

Tivoli

Rem

ote

Co

ntro

l

OS/2 WorkstationTo uninstall the file transfer feature, perform the following stepslocally on the workstation:

1. Delete the following files from the<LCF_dir>\PCREMOTE\os2-ix86\classes directory:ft_ctl.jarft_tgt.jar

where:


2. Delete the following files, if present, from the<LCF_dir>\PCREMOTE\os2-ix86\LEVELS directory:FT_TGT.LVLFT_CTL.LVL

3. Delete the file: <LCF_dir>\PCREMOTE\os2-ix86\CTL\EQNSPU.DLL if it exists.

4. Delete the file: <LCF_dir>\PCREMOTE\os2-ix86\TGT\EQNSPU.DLL if it exists.

Uninstalling ChatTo uninstall the chat feature, follow the procedure that relates to theoperating system of your workstation.

Windows NT 4.0 or Windows 2000 WorkstationTo uninstall the chat feature, perform the following steps locally onthe workstation:

1. Delete the following file from the<LCF_dir>\PCREMOTE\w32-ix86\classes directory:chat.jar

where:


40 Version 3.7

2. Delete the following files, if present, from the<LCF_dir>\PCREMOTE\w32-ix86\LEVELS directory:CH_TGT.LVLCH_CTL.LVL

Windows 95 or Windows 98 WorkstationTo uninstall the chat feature, perform the following steps locally onthe workstation:

1. Delete the following file from the<LCF_dir>\PCREMOTE\win95\classes directory:chat.jar

where:


2. Delete the following files, if present, from the<LCF_dir>\PCREMOTE\win95\LEVELS directory:CH_TGT.LVLCH_CTL.LVL

OS/2 WorkstationTo uninstall the chat feature, perform the following steps locally onthe workstation:

1. Delete the following files from the<LCF_dir>\PCREMOTE\os2-ix86\classes directory:chat.jar

where:


2. Delete the following files, if present, from the<LCF_dir>\PCREMOTE\os2-ix86\LEVELS directory:CH_TGT.LVLCH_CTL.LVL


2.In

stalling

Tivoli

Rem

ote

Co

ntro

l

Uninstalling Remote Diagnosis ConsoleTo uninstall the remote diagnosis feature, follow the procedure thatrelates to the operating system of your workstation.

Windows NT or Windows 2000 WorkstationTo uninstall the remote diagnosis feature, perform the followingsteps locally on the workstation:

1. Delete the following files from the<LCF_dir>\PCREMOTE\w32-ix86\classes directory:tse.jarmail.jarxmlparse.jarorom.jarcollect.jaractiva.jar

where:


2. Delete the following files, if present, from the<LCF_dir>\PCREMOTE\w32-ix86\LEVELS directory:RD_TGT.LVLRD_CTL.LVL

3. Delete the <LCF_dir>\PCREMOTE\w32-ix86\cat directory.

4. Delete the TSEProp.ini file from the<LCF_dir>\PCREMOTE\w32-ix86\CTL directory.

5. Delete the <LCF_dir>\PCREMOTE\w32-ix86\Plugins directory.

Windows 95 or Windows 98 WorkstationTo uninstall the remote diagnosis feature, perform the followingsteps locally on the workstation:

1. Delete the following files from the<LCF_dir>\PCREMOTE\win95\classes directory:

42 Version 3.7

tse.jarmail.jarxmlparse.jarorom.jarcollect.jaractiva.jar

where:


2. Delete the following files, if present, from the<LCF_dir>\PCREMOTE\win95\LEVELS directory:RD_TGT.LVLRD_CTL.LVL

3. Delete the <LCF_dir>\PCREMOTE\win95\cat directory.

4. Delete the TSEProp.ini file from the<LCF_dir>\PCREMOTE\win95\CTL directory.

5. Delete the <LCF_dir>\PCREMOTE\win95\Plugins directory.

OS/2 WorkstationTo uninstall the remote diagnosis feature, perform the followingsteps locally on the workstation:

1. Delete the following files from the<LCF_dir>\PCREMOTE\os2-ix86\classes directory:tse.jarmail.jarxmlparse.jarorom.jarcollect.jaractiva.jar

where:


2. Delete the following files, if present, from the<LCF_dir>\PCREMOTE\os2-ix86\LEVELS directory:RD_TGT.LVLRD_CTL.LVL


2.In

stalling

Tivoli

Rem

ote

Co

ntro

l

3. Delete the <LCF_dir>\PCREMOTE\os2-ix86\cat directory.

4. Delete the TSEProp.ini file from the<LCF_dir>\PCREMOTE\os2-ix86\CTL directory.

5. Delete the <LCF_dir>\PCREMOTE\os2-ix86\Plugins directory.

Uninstalling Remote Diagnosis TargetTo uninstall remote diagnosis target follow the procedure that relatesto the operating system of your workstation.

Windows NT or Windows 2000 WorkstationTo uninstall remote diagnosis target, perform the following stepslocally on the workstation:

1. Delete the following directories:<LCF_dir>\PCREMOTE\w32-ix86\TGT\bin<LCF_dir>\PCREMOTE\w32-ix86\TGT\CONF<LCF_dir>\PCREMOTE\w32-ix86\TGT\LOGS<LCF_dir>\PCREMOTE\w32-ix86\TGT\perl<LCF_dir>\PCREMOTE\w32-ix86\TGT\temp<LCF_dir>\PCREMOTE\w32-ix86\TGT\root

where:


2. Delete the following files:<LCF_dir>\PCREMOTE\w32-ix86\TGT\SIOUX.EXE<LCF_dir>\PCREMOTE\w32-ix86\TGT\APACHECORE.DLL<LCF_dir>\PCREMOTE\w32-ix86\TGT\*.conf

Windows 95 or Windows 98 WorkstationTo uninstall remote diagnosis target, perform the following stepslocally on the workstation:

1. Delete the following directories:<LCF_dir>\PCREMOTE\win95\TGT\bin<LCF_dir>\PCREMOTE\win95\TGT\CONF<LCF_dir>\PCREMOTE\win95\TGT\LOGS<LCF_dir>\PCREMOTE\win95\TGT\perl<LCF_dir>\PCREMOTE\win95\TGT\temp<LCF_dir>\PCREMOTE\win95\TGT\root

44 Version 3.7

where:


2. Delete the following files:<LCF_dir>\PCREMOTE\win95\TGT\SIOUX.EXE<LCF_dir>\PCREMOTE\win95\TGT\APACHECORE.DLL<LCF_dir>\PCREMOTE\win95\TGT\*.conf

Uninstalling Packs from a Remote Diagnosis TargetTo uninstall a diagnosis pack from a remote diagnosis target deletethe following directories, relative to the operating system of yourworkstation.

Windows NT or Windows 2000<LCF_dir>\PCREMOTE\w32-ix86\TGT\root\guides\<pack_directory_name>

where:

<LCF_dir> is the directory where the Tivoli Management Agenthas been installed

<pack_directory_name>is the directory where the diagnosis pack has beeninstalled

Windows 95 or Windows 98<LCF_dir>\PCREMOTE\win95\TGT\root\guides\<pack_directory_name>

where:


<pack_directory_name>is the directory where the diagnosis pack has beeninstalled


2.In

stalling

Tivoli

Rem

ote

Co

ntro

l

Uninstalling Tools from a Remote Diagnosis TargetTo uninstall a tool from a target delete the following directories,relative to the operating system of your workstation.

Windows NT or Windows 2000<LCF_dir>\PCREMOTE\w32-ix86\TGT\root\tools\<tool_directory_name>

where:


<tool_directory_name>is the directory where the tool has been installed

Windows 95 or Windows 98<LCF_dir>\PCREMOTE\win95\TGT\root\tools\<tool_directory_name>

where:


<tool_directory_name>is the directory where the tool has been installed

Uninstalling Plugins from a Remote DiagnosisConsole

To uninstall a tool from a remote diagnosis console delete thefollowing directories, relative to the operating system of yourworkstation.

Windows NT or Windows 2000<LCF_dir>\PCREMOTE\w32-ix86\Plugins\<plugin_directory_name>

where:


46 Version 3.7

<plugin_directory_name>is the directory where the plugin has been installed

Windows 95 or Windows 98<LCF_dir>\PCREMOTE\win95\Plugins\<plugin_directory_name>

where:



OS/2<LCF_dir>\PCREMOTE\os2-ix86\Plugins\<tool_directory_name>

where:




2.In

stalling

Tivoli

Rem

ote

Co

ntro

l

48 Version 3.7

Configuring and Starting TivoliRemote Control

This chapter describes how to configure Tivoli Remote Control foruse by administrators. It also describes how to start a Tivoli RemoteControl session. For information about using each Tivoli RemoteControl action, see chapters 4 through 7.

For some operations, you may need to refer to the TivoliManagement Framework User’s Guide, or the Tivoli ManagementFramework Reference Manual.

Configuration TasksAfter you have installed the Tivoli Remote Control server, you mustconfigure it for use by administrators. This means:

¶ Adding the RemoteControl managed resource to the policyregion. For details, see “Adding Tivoli Remote Control to aPolicy Region” on page 50.

¶ Creating an instance of the RemoteControl managed resource inthe policy region. For details, see “Adding Tivoli RemoteControl to a Policy Region” on page 50.

¶ Adding Tivoli Remote Control roles to the existing roles of eachadministrator. For details, see “Assigning Roles” on page 52.

3


3.C

on

figu

ring

and

Startin

gTivo

liR

emo

teC

on

trol

¶ If required, assigning targets to the policy regions for whichadministrators have Tivoli Remote Control roles. For details, see“Assigning Targets to a Policy Region” on page 53.

¶ Setting the default policy. For details, see “Changing the Valuesof Activity and Display Settings” on page 55.

You may also want to:

¶ Set traces on. For details, see “Setting Traces” on page 155.

¶ Set logging on. For details, see “Logging Application Events ona Windows NT or Windows 2000 Controller” on page 160.

¶ Consider ways to improve performance. For details see“Improving Performance” on page 163.

Adding Tivoli Remote Control to a Policy RegionEach policy region maintains a list of managed resources. To useTivoli Remote Control, you must add the RemoteControl managedresource to the list. The controllers for Tivoli Remote Control mustbelong to the same region as the RemoteControl managed resource.The targets do not need to belong to the same region as theRemoteControl managed resource. You can create the instance on amanaged node other than the Tivoli server.

Note: The Tivoli Remote Control server component must beinstalled on the node that you specify.

You can perform this task from either the Tivoli desktop or thecommand line.

50 Version 3.7

Creating a Managed Resource1. From a policy region, select Create > RemoteControl to display

the Create RemoteControl dialog.

2. Enter a unique name for the instance in the Name/Icon Labelfield. The name can include spaces.

3. To create the Tivoli Remote Control resource on a managed nodeother than the Tivoli server, enter the node’s name in theManagedNode field.

Note: The Tivoli Remote Control server component must beinstalled on the managed node that you specify.

4. Click Create & Close to create the instance and return to thePolicy Region window.

Command LineThe following command creates a RemoteControl managed resourcein a policy region:wcreaterc <label> <location> <policy region>

where:

<label> Specifies the name of the new instance to be created.

<location> Specifies the managed node where the instance hasto be created.


3.C

on

figu

ring

and

Startin

gTivo

liR

emo

teC

on

trol

Note: The Tivoli Remote Control server componentmust be installed on the managed node thatyou specify.

<policy region>Specifies the policy region label where the instancehas to be inserted.

For further information about wcreaterc, refer to “Command LineInterface” on page 143.

Assigning RolesAfter creating an instance of the RemoteControl managed resource,you can assign Tivoli Remote Control roles to administrators. Youcan assign roles only if you have the appropriate access rights.

Setting roles at the policy region level enables the administrator toperform the appropriate Tivoli Remote Control tasks within thespecified policy region. These privileges do not extend to otherpolicy regions. These privileges do apply to any subpolicy regionassociated to the policy region where the remote control roles havebeen defined.

Setting TMR roles allows the administrator to perform theappropriate Tivoli Remote Control tasks in the entire TMR.

The Tivoli Remote Control roles are required in the policy regionwhere the target systems are defined. In addition to these roles, theadmin role is required where the Tivoli RemoteControl managedresource is defined.

The Tivoli Management Framework User’s Guide explains how toassign roles to administrators.

The following two tables show the activities available toadministrators of Tivoli Remote Control, and the role associated witheach activity.

52 Version 3.7

Activity Role needed in the controller’spolicy region

Use any RemoteControl action admin

Activity Role needed in the target’spolicy region

Monitor a target. See Chapter 4. remote_monitor

Monitor and control a target. SeeChapter 4.

remote_control

Run commands on a target using thewrcmdpcr CLI. See Chapter 4.

remote_probe

Reboot a target. See Chapter 4. remote_reboot

Send files to a target from thecontroller. See Chapter 5.

remote_ft_send

Receive files from a target. SeeChapter 5.

remote_ft_receive

Exchange text messages with a target.See Chapter 6.

remote_chat

Run diagnostic scripts on a target.See Chapter 7.

remote_diagnosis

Download logs and other specifieddiagnostic files from a target. SeeChapter 7.

remote_artifacts

Backup and restore critical files andsettings on a target. See Chapter 7.

remote_vitalobjects

Remote Diagnosis output to TivoliEvent Console (TEC). See Chapter 7

remote_diagnosis_to_TEC plusremote_diagnosis and/orremote_vitalobjects

Assigning Targets to a Policy RegionIn new installations of Tivoli Remote Control, all targets must beendpoints. However, the server and gateway components of version3.7 support all target components from the previous (3.6.5) version.Existing targets can be:

¶ ManagedNodes


3.C

on

figu

ring

and

Startin

gTivo

liR

emo

teC

on

trol

¶ PCManagedNodes

¶ NetWareManagedSiteClient

In the case of endpoints, the previous (3.6.5) version is supportedonly if the endpoints belong to an interconnected TMR whose serverand gateway are at level 3.6.5.

Each target must be assigned to a policy region where administratorshave Tivoli Remote Control roles.

If the target system is an endpoint, you must assign it to a policyregion where you set the Tivoli Remote Control roles as follows:

1. Use the wmv command

2. Synchronize the Tivoli gateway to which the endpoint logs on byusing the commands wep sync_gateways and wgateway<Gateway-label> restart

3. Close and restart the Tivoli desktop in order to effect thesechanges. Be sure also that the policy region where the endpointis going to be assigned has the endpoint resource in the list ofmanaged resource types valid for that specific policy region.

The following example command assigns an endpoint to a policyregion:wmv @Endpoint:<Endpoint_label> @PolicyRegion:<policy region>

where:

<Endpoint_label>Specifies the endpoint label to be assigned.

<policy region>Specifies the policy region label where the endpoint labelhas to be assigned.

For further information about these commands, see the TivoliManagement Framework Reference Manual.

54 Version 3.7

Changing the Values of Activity and Display SettingsYou can set up a default policy for each policy region. The defaultpolicy sets activity and display options for the administrators in itspolicy region. See the Tivoli Management Framework User’s Guidefor more information about the default policy, including the contextand authorization roles needed to customize it.

You set values for a Tivoli Remote Control default policy using itspolicy methods. The policy methods are implemented using the shellscript binding.

You can specify that the value set by a policy method is locked. If itis not locked, the value may be changed by an administrator usingthe Edit Settings dialog (see page 59) or the Define Targets dialog(see page 56). Setting new values in these dialogs does not changethe settings for the default policy, except for one setting: if the targetlist is saved, it becomes the value for rc_def_targets. See page 73.

The following table shows the use of each policy method.

Policy method What it controls See page

rc_def_alt_t Use of <Alt><T> on the target 61

rc_def_backgrnd Availability of wallpaper and screensaver on thetarget

61

rc_def_checkinterp Inclusion of non-Windows NT managed nodeentries in the list of targets

62

rc_def_color Number of colors used to display the target’sscreen on the controller

62

rc_def_command Activities available to administrators 63

rc_def_comp Data compression 63

rc_def_define Order of targets in the list of targets 64

rc_def_filter_mode Types of target to be included in the list of targets 65

rc_def_ftmode Types of file transfer activity available 65

rc_def_grace_time Time to wait for a user to respond to an activityrequest

66

rc_def_gw Whether or not to use a Remote Control gateway 66


3.C

on

figu

ring

and

Startin

gTivo

liR

emo

teC

on

trol

Policy method What it controls See page

rc_def_inactivity Time to wait for user activity on a target before asession times out

67

rc_def_initstate Initial state of the session. Only effective whenrc_def_rcmode is set to control

68

rc_def_polfilter_mode Whether or not to show targets only for a specifiedregion

69

rc_def_ports Ports to use for controller-target communication 69

rc_def_rate Refresh rate of the controller display 71

rc_def_rcmode Initial state of the session 71

rc_def_targets Whether a target is included in the targets list 73

rc_def_tfc Whether or not to use Pinnacle Trusted FileCommander Plus

73

rc_def_timeout_op Whether or not to abandon a session if the graceperiod expires

74

rc_def_uncheckedlist Targets to display when rc_def_define is set toUncheckedlist

74

rc_def_rd_config Browser and mail settings 72

The following two sections show the display elements affected bypolicy methods.

Methods Used for the Targets List DialogThe targets list dialog is displayed when you start Tivoli RemoteControl. There are two versions of the dialog.

The content of the dialog is governed by the value of therc_def_define policy method. See page 64.

If the value of the rc_def_define policy method isDefinableTargetList or UncheckedList, the Remote Control dialog

56 Version 3.7

is displayed with a Targets listed as follows:

The Define Targets List button is disabled if the value of therc_def_define policy method is DefinableTargetList-locked.

If the value of the rc_def_define policy method is FilteredList, theRemote Control dialog is displayed with Policy Regions and Targets


3.C

on

figu

ring

and

Startin

gTivo

liR

emo

teC

on

trol

listed as follows:.

This dialog lists the targets as set by the rc_def_UncheckedListpolicy method. See page 74.

58 Version 3.7

Methods Used in The Edit Settings DialogThe Edit Settings Dialog is displayed by clicking the Edit Settingsbutton in either of the two targets list dialogs.

The Edit Settings Dialog is displayed by clicking the Edit Settingsbutton in either of the two targets list dialogs.

For details of the settings, see the descriptions of the relevant policymethod in “Setting Values for the Default Policy” on page 60.


3.C

on

figu

ring

and

Startin

gTivo

liR

emo

teC

on

trol

Methods Used in The Define Targets List DialogThe Define Targets List Dialog is displayed by clicking the DefineTargets List button in version 1 of the targets list dialog.

Targets already selected are displayed in the Current list. Theavailable targets are displayed in the Available list. To move a targetbetween the lists, select it and click the left or right arrow, asappropriate. To restrict the type of target shown in the list, select atype from the Target Type list.

Any changes to the list are saved to the shell file associated with therc_def_targets policy method. To apply the changes, click Set orSet & Close. You are asked to confirm the change. Click Yes tochange the shell file. See “rc_def_targets” on page 73 for moreinformation.

Setting Values for the Default PolicyYou use the methods described in this section to set values for thedefault policy.

60 Version 3.7

rc_def_alt_tDetermines whether or not the target user can press the <Alt><T>key combination to change the state during a Remote Controlsession. The possible states are active, monitor and suspend.

Possible values:

ENABLEDThe <Alt><T> key combination is enabled

DISABLEDThe <Alt><T> key combination is disabled

Default value: DISABLED

If the value has the suffix -locked, it cannot be reset in the EditSettings dialog.

Sample shell script:#!/bin/shecho “DISABLED”exit 0

rc_def_backgrndDetermines whether or not to disable the desktop background andthe screensaver of the target. For OS/2 targets, only the backgroundis disabled.

Possible values:

On The background and the screensaver are disabled

Off The background and the screensaver are not disabled

Default value: On


Sample shell script:


3.C

on

figu

ring

and

Startin

gTivo

liR

emo

teC

on

trol

#!/bin/shecho “On”exit 0

rc_def_checkinterpDetermines whether or not non–Windows NT managed nodes aredisplayed in the Targets list.

If the value of rc_def_define is UncheckedList, this method isignored.

Possible values:

YES Non–Windows NT managed nodes are displayed

NO Non–Windows NT managed nodes are not displayed

Default value: YES

Sample shell script:#!/bin/shecho “Yes”exit 0

rc_def_colorSets the number of colors used to display the target screen on thecontroller.

Possible values:

0 Number of colors used on the target display

4 16 colors

8 256 colors

Default value: 8



62 Version 3.7

#!/bin/shecho “8”exit 0

rc_def_commandDetermines whether or not an action is available.

Possible values:

Any combination of the following tags, separated by a semicolon (;).

rc Remote Control

reboot Reboot

filexfer File Transfer

chat Chat

rd Remote Diagnosis

Default value: rd;reboot;chat;filexfer;rc;

The tag specified last becomes the default action.


Sample shell script:#!/bin/shecho “rd;reboot;chat;filexfer;rc”exit 0

rc_def_compDetermines whether or not to compress data transmitted to thecontroller. If the RemoteControl managed resource is configured touse a Tivoli Remote Control Gateway, this method is ignored andthe data is always compressed.

Possible values:

On Data is compressed

Off Data is not compressed


3.C

on

figu

ring

and

Startin

gTivo

liR

emo

teC

on

trol

Default value: On


Sample shell script:#!/bin/shecho “On”exit 0

rc_def_defineDetermines how the Targets list is built and displayed.

Possible values:

DefinableTargetList List by target label

FilteredList List by Policy Region

UncheckedList List according torc_def_uncheckedlist. See page 74.

Default value: DefinableTargetList

If the value is DefinableTargetList or FilteredList, then a target islisted if it is included by rc_def_targets. See page 73.

If the value is DefinableTargetList, the targets list can be resetusing the Define Targets List dialog. See “Methods Used in TheDefine Targets List Dialog” on page 60. The edited list is saved inrc_def_targets for future use.

If the value DefinableTargetList has the suffix -locked, the targetslist can be reset using the Define Targets List dialog.

Sample shell script:#!/bin/shecho “UncheckedList”exit 0

64 Version 3.7

rc_def_filter_modeDetermines whether or not the list of targets shows managed nodesor endpoints, or both. This method has effect only if rc_def_defineis set to FilteredList. See page 64.

Possible values:

node Show only managed nodes

epnode Show only endpoints

pcnode Show PC agent

nwnode Show IPX agent

Default value: all


Sample shell script:#!/bin/shecho “all”exit 0

rc_def_ftmodeDetermines what roles are needed to select the File Transfer action.

Possible values:

send The administrator can select the action only if he orshe has the role remote_ft_send

receive The administrator can select the action only if he orshe has the role remote_ft_receive

both The administrator can select the action if he or shehas either or both the remote_ft_receive andremote_ft_send roles

Default value: both



3.C

on

figu

ring

and

Startin

gTivo

liR

emo

teC

on

trol

#!/bin/shecho “both”exit 0

rc_def_grace_timeSets the number of seconds to wait for the target user to respondbefore an activity starts or times out.

Possible values:

0 0 seconds

5 5 seconds

10 10 seconds

15 15 seconds

30 30 seconds

60 60 seconds

Default value: 5

If the value is set to 0, the activity starts without displaying themessage box for user acceptance on the target.


Sample shell script:#!/bin/shecho “5”exit 0

rc_def_gwDetermines whether or not to use an installed gateway.

Possible values:

NO Do not use the gateway

YES <ManagedNode-label> <GatewayPort> <MaxSessions>IP:<IP-Port> XP:<IPX-Port>

66 Version 3.7

Use the specified gateway, where:

<ManagedNode-label> is the name of the managed node tobe used as gateway.

<GatewayPort> is the TCP/IP port used by the gateway tolisten for connection request from controllers.

<MaxSessions> is the number of Tivoli Remote Controlsessions between a controller and target that the gateway canhandle on the same incoming port. The maximum value is64.

<IP-Port> is the local TCP/IP port used by the gateway tocommunicate with TCP/IP targets. If it has the value 0, thegateway uses a port generated by the communication stack.This value is meaningful only if the gateway is a WindowsNT managed node.

<XP-Port> is the local SPX/IPX port used by the gateway tocommunicate with SPX/IPX targets. If it has the value 0, thegateway uses a port generated by the communication stack.This value is meaningful only if the gateway is a WindowsNT managed node.

Default value: NO

Sample shell script:#!/bin/shecho “YES enigm2 35000 16 IP:0 XP:0”exit 0

rc_def_inactivitySets the number of minutes that a session remains active when thereis no keyboard or mouse activity.

Possible values:

0 No session timeout

<integer> The session times out after <integer> minutes

Default value: 0


3.C

on

figu

ring

and

Startin

gTivo

liR

emo

teC

on

trol



rc_def_initstateSets the initial state of a Remote Control action. The value iseffective only if the rc_def_rcmode value is control. See page 71.

Possible values:

monitor The action is started in monitor state

active The action is started in active state

Default value: monitor


Sample shell script:#!/bin/shecho “monitor”exit 0

rc_def_polfilter_modeDetermines whether or not to show targets in the controller’s regiononly.

This method has effect only if rc_def_define value is set toFilteredList. See page 64.

Possible values:

region Show targets for the policy region selected in thetargets list dialog

myregion Show only targets in the controller’s policy region

all Show all targets

68 Version 3.7

Default value: myregion


Sample shell script:#!/bin/shecho “myregion”exit 0

rc_def_portsDetermines the ports that controllers and targets use to communicate.

Possible values:rc TIP:<target TCP/IP port>

CIP:<controller TCP/IP port>TXP:<target SPX/IPX port>CXP:<controller SPX/IPX port><\n>

filexfer TIP:<target TCP/IP port>CIP:<controller TCP/IP port>TXP:<target SPX/IPX port>CXP:<controller SPX/IPX port><\n>

chat TIP:<target TCP/IP port>CIP:<controller TCP/IP port>TXP:<target SPX/IPX port>CXP:<controller SPX/IPX port><\n>

rd TIP:<target TCP/IP port>CIP:<controller TCP/IP port>TXP:<target SPX/IPX port>CXP:<controller SPX/IPX port><\n>

where:

rc Sets the ports for the Remote Control action

filexfer Sets the ports for the File Transfer action

chat Sets the ports for the Chat action

rd Sets the ports for the Remote Diagnosis action

<target TCP/IP port>Is the target TCP/IP port. The possible values are:


3.C

on

figu

ring

and

Startin

gTivo

liR

emo

teC

on

trol

<port>Port number

0 Default port (2501 for Remote Control, 2502for File Transfer, 2503 for Chat, 2504 forRemote Diagnosis)

<controller TCP/IP port>Is the controller TCP/IP port.The possible values are:

<port>Port number

0 Port is assigned by the communication stack

<target SPX/IPX port>Is the target SPX/IPX port, used for the RemoteControl action only. The other actions do not yetsupport IPX/SPX. The possible values are:

<port>Port number

0 Default port. For Remote Control, this is0x8771.

<controller SPX/IPX port>Is the controller SPX/IPX port used for the RemoteControl action with SPX/IPX targets. If a gateway isused, this is ignored because all gatewaycommunication uses TCP/IP. If the value is 0, thecontroller uses a port assigned by the communicationstack.

<\n> Is the new line character.

Default values:rc TIP:0 CIP:0 TXP:0 CXP:0<\n>filexfer TIP:0 CIP:0 TXP:0 CXP:0<\n>chat TIP:0 CIP:0 TXP:0 CXP:0<\n>rd TIP:0 CIP:0 TXP:0 CXP:0<\n>


70 Version 3.7

#!/bin/shecho “rc TIP:0 CIP:0 TXP:0 CXP:0"echo “filexfer TIP:0 CIP:0 TXP:0 CXP:0”echo “chat TIP:0 CIP:0 TXP:0 CXP:0”echo “rd TIP:0 CIP:0 TXP:0 CXP:0”exit 0

rc_def_rateSets the refresh rate in milliseconds for the target display on thecontroller.

Possible values:

<integer> Any integer value greater than or equal to 100. Themaximum recommended value is 4000

Default value: 300



rc_def_rcmodeSets the activities available for a Remote Control action.

Possible values:

control If the administrator has the role remote_control onthe target, a control session is started. The initialstate is set by rc_def_initstate. See page 68. Theadministrator can change the state to monitor.

If the administrator has the role remote_monitor onthe target, a monitor session is started. Theadministrator cannot change the state to control.

monitor If the administrator has one or both of the roles


3.C

on

figu

ring

and

Startin

gTivo

liR

emo

teC

on

trol

remote_monitor or remote_control, a monitorsession is started. The administrator cannot changethe state to control.

Default value: control

Sample shell script:#!/bin/shecho “control”exit 0

rc_def_rd_configSets the default browser, the mail address and the mail host.

Possible values:

Any combinations of the following lines:rd_browser:<browser_name>rd_mail_from:<mail_originator_address>rd_mail_host:<mail host>

where:

rd_browserSets the default browser

rd_mail_fromSets the mail originator address

rd_mail_hostSets the mail host

Note: Use the / sign as directory delimiter.

Default value:rd_browser:<Unknown>rd_mail_from:<Unknown>rd_mail_host:<Unknown>

If the value has the suffix -locked, it cannot be reset in theCustomized Options window.

72 Version 3.7

Sample shell script:#!/bin/shecho "rd_browser:<c:/netscape/netscape.exe>-locked"echo "rd_mail_from:<[email protected]>"echo "rd_mail_host:<mail.host.com>"exit 0

rc_def_targetsDefines a list of target labels for use when the rc_def_define valueis DefinableTargetList or FilteredList. See page 64.

Possible values:

default-list All targets

OR<target_label> [{<\n><target_label>}]

where

<target_label> is the name of a managed node or an endpoint

<\n> is the new line character

Default value: default-list

Sample shell script:#!/bin/shecho “default-list”exit 0

rc_def_tfcDetermines whether or not to use Pinnacle Trusted File CommanderPlus for Tivoli to control access to the target file system for aRemote Control, Remote Diagnosis or File Transfer action.

Possible values:

NO Do not use Pinnacle Trusted File Commander Plus for Tivoli


3.C

on

figu

ring

and

Startin

gTivo

liR

emo

teC

on

trol

YES:<filepathname>[{;<filepathname>}]where <filepathname> is a fully qualified filename withforward slash (/) directory delimiter. The overall stringcannot exceed 260 characters

Default value: NO

Sample shell script:#!/bin/shecho “YES:C:/tfc/xxx.sec;D:/tfc/yyyy.sec”exit 0

rc_def_timeout_opDetermines whether or not to start a session if the user does notrespond within the grace period.

Possible values:

ENABLED Start the session if the grace period times out

DISABLED Cancel the session if the grace period times out

Default value: DISABLED


Sample shell script:#!/bin/shecho “DISABLED”exit 0

rc_def_uncheckedlistSpecifies the contents of the targets list when the methodrc_def_define is UncheckedList. See page 64.

Possible values:(<Endpoint_label>+|<ManagedNode_label>)[{<\n>(<Endpoint_label>+|<ManagedNode_label>)}]

@(Endpoint:<Endpoint_label>|ManagedNode:<ManagedNode_label>)[{<\n>@(Endpoint:<Endpoint_label>|ManagedNode:<ManagedNode_label>)}]

74 Version 3.7

where:

<Endpoint_label> is the label of an endpoint. <ManagedNode_label>is the label of a managed node. <\n> is the new line character.Default value:wgetallinst ManagedNodewgetallinst Endpoint

Note: The first syntax is supported only for compatibility withprevious changes, and could give rise to possible ambiguity.Therefore we strongly recommend using the second syntax.

Sample shell script:#!/bin/sh

wgetallinst ManagedNode | sed ‘s/.*/@ManagedNode:&/’wgetallinst Endpoint | sed ‘s/.*/@Endpoint:&/’

exit 0

Creating a New Policy Default ObjectThe following procedure can be used to create a new Policy Defaultobject for a RemoteControl managed resource and to associate itwith a PolicyRegion.

1. Create a new Policy object:wcrtpol -d RemoteControl RCPol RemoteControl_PDO(where RCPol is your new Default Policy object).

2. Verify that the Policy object exists:wlspol -d RemoteControloutput:RemoteControl_PDORCPol...

3. List what policy methods govern the resource:wlspolm -d RemoteControloutput:rc_def_commandrc_def_filter_moderc_def_grace_timerc_def_timeout_oprc_def_polfilter_mode...


3.C

on

figu

ring

and

Startin

gTivo

liR

emo

teC

on

trol

4. Associate a Policy Object with a Policy Region:wsetpr -d RCPol RemoteControl XXXXX-region(You can also do this in the GUI).

5. If another Policy Region requires different default policies, repeatthese steps to create other Default Objects.

Please refer to the Tivoli Management Framework publications formore details about the commands used above.

Changing the Default Policy of the Tivoli RemoteControl Dialog

1. Enter the following command to retrieve the shell scriptassociated with RemoteControl policy:wgetpolm -d RemoteControl RemoteControlPD_instance_namepolicy_method_name > outfile

where:

-d Indicates that the default policy is to be edited.

RemoteControlSpecifies the managed resource type.

RemoteControlPD_instance_nameSpecifies the RemoteControl Policy Defaultobject name.

policy_method_nameSpecifies the name of the policy method.

outfile Specifies the name of a temporary text file.

2. Use a line editor to modify the output file.

3. Enter the following command to replace the policy with the editpolicy script:wputpolm -d RemoteControl RemoteControlPD_instance_name policy_method_name < outfile

where the arguments are the same as those you specified for thewgetpolm command in the step 1 of this procedure.

76 Version 3.7

Using the Tivoli Remote Control GatewayTo configure the Tivoli Remote Control gateway, see rc_def_gwpolicy method on page 66.

A Tivoli Remote Control gateway handles communication betweencontrollers and targets. You can use Tivoli Remote Control withoutgateways, but you might want to configure a Tivoli Remote Controlgateway if you need:

1. IP to IPX protocol conversion between controller and target.

2. Firewall environment configurations. If you match the TivoliRemote Control gateway port to your firewall configuration, thecontrollers and targets on that gateway can communicate throughthe firewall.

On the same managed node, a gateway can handle up to 32 differentincoming ports and up to 64 sessions for each incoming port.

Supported protocols for the gateway connection are:

TCP/IP between the controllers and the gateway

TCP/IP, SPX/IPX between the gateway and the targets

Note:

1. The SPX/IPX protocol is supported only by Windows NTgateways.

2. The Tivoli Remote Control gateway cannot be used tobridge two different LAN segments.

Starting a Tivoli Remote Control ActionYou can start a Tivoli Remote Control action from the Tivolidesktop, the command line (see “wrc” on page 145), or from theWeb interface.

Each action runs independently. You can run one or more sessions,of the same or of different actions, at the same time.


3.C

on

figu

ring

and

Startin

gTivo

liR

emo

teC

on

trol

When you start a session, the following grace period can be set:

¶ If the grace period is set to 0, a session is started withoutwarning the target user.

¶ If the grace period is set to greater than 0, a dialog appears atthe target. The dialog asks the user to accept the session. If theuser does not accept the session within the grace period, one oftwo things happens, depending on the timeout setting. Either theaction continues, or the dialog disappears and a message informsthe administrator that the session has timed out.

If the target user rejects the session, a message warning ofthe rejection is displayed at the controller.

The grace period is set by the default policy, and may be changed bythe administrator. For more details, see “Changing the Values ofActivity and Display Settings” on page 55.

From the Tivoli DesktopTo start an action from the Tivoli desktop:

1. Double-click a policy region

2. Double-click the RemoteControl icon

One of two dialogs is displayed. For information about configuringthe target list dialog, see “Changing the Values of Activity andDisplay Settings” on page 55.

Remote Control Targets List DialogIf the Targets List dialog is displayed, you can select individualtargets to appear in the targets list. For an example of the TargetsList dialog, see “Methods Used for the Targets List Dialog” onpage 56.

To start a session, do the following:

1. If you want, use the Edit Settings button to change the settingsdefined by the Default policy. See “Methods Used in The EditSettings Dialog” on page 59.

78 Version 3.7

2. If you want, use the Define Targets List button to change thecontents of the targets list. See “Methods Used for the TargetsList Dialog” on page 56.

3. Select a target from the Targets list. A target name followed by a+ (plus) indicates that the target is an endpoint.

4. Select an action from the Actions list. For a description of theactions available, see chapters 4 through 7.

5. Click the Run button to start the session

You can also start the session by selecting a target then doubleclicking an action; or by selecting an action then double-clicking atarget.

Remote Control Policy Regions and Targets List DialogIf the Policy Regions and Targets List dialog is displayed, you canchange the contents of the targets list by selecting a policy regionand target type. For an example of the Policy Regions and TargetsList dialog, see “Methods Used for the Targets List Dialog” onpage 56.

To start a session, do the following:

1. If you want, use the Edit Settings button to change the settingsdefined by the Default policy. See “Methods Used in The EditSettings Dialog” on page 59.

2. Use Policy Regions Mode to select the policy regions you wantto be listed in the Policy Regions panel.

3. Use Target Type to select type of target you want to be listed inthe Targets panel.

4. Use Policy Regions to select the policy region whose targets youwant to be listed in the Targets panel.

5. Select a target from the Targets list. A target name followed by a+ (plus) indicates that the target is an endpoint.

Note: Do not select a workstation as the target if you are usingthat workstation as the controller. The result isunpredictable.


3.C

on

figu

ring

and

Startin

gTivo

liR

emo

teC

on

trol

6. Select an action from the Actions list. For a description of theactions available, see chapters 4 through 7.

7. Click the Run button to start the session

You can also start the session by selecting a target thendouble-clicking an action; or by selecting an action thendouble-clicking a target.

From a Web BrowserTo start an action from a web browser:

1. Enter the following information on your browser:http://TMR_servername:TMR_serverport

Note: The value of TMR_serverport must be the same as thatset during installation. For further information, see theTivoli Management Framework Planning and InstallationGuide.

This connects you to the Tivoli HTTP server, which is installedonly on the TMR server. The default.html page appears, showingthe available links to Tivoli applications.

Note: Internet Explorer 4 or higher and Netscape 4.6 or higherare supported.

80 Version 3.7

2. Select the Remote Control link. The first time you click on this,you are asked for the Tivoli User Name and Password. Enter thesame data you use to start the Tivoli Desktop. A list of all theTivoli Remote Control Tools in the TMR appears.

3. Select the Server ID required and click Continue. The followingpage appears:


3.C

on

figu

ring

and

Startin

gTivo

liR

emo

teC

on

trol

where: Server ID is the name of the tool Controller ID is the listof endpoints Target ID the list of endpoints Action, chosen byselecting desired button Default values for the Remote ControlWeb Access fields are loaded automatically. These come from thepolicy methods used in the policy region where the selectedRemote Control tool resides. To change the default values youmust edit the related policy methods.

4. Click one of the buttons to start the desired Tivoli RemoteControl action.

Customizing the Web InterfaceThe default.html page contains a link to the Tivoli Remote Controlapplication using the script pcremoteaccess.cgi. However, if youwish to change the default page you must use the followingguidelines.

You can customize the Remote Control web page, by editing the filedefault.html. By default, this file contains a link using the scriptpcremoteaccess.cgi. There are 5 parameters (0 to 5) available thatcan be added to this script, using the following syntax: 0-5parameters:pcremoteaccess.cgi? RCTOOL=x & RCCTRL=x & RCDISP=x & RCCOID=x &RCTARG=x & RCACTN=x & RCOPTS=Y

where:

RCTOOL The name of the Tivoli Remote Control tool

RCCTRL The controller name

RCDISP The name of the display. It is used only in aWindows Windows Terminal Server environment

RCCOID The Tivoli ObjectID of the Windows TerminalServer endpoint.

RCTARG The target name. If you specify a name, by defaultthis name is associated to an endpoint target. Todefine different kinds of targets you must use thefollowing syntax:<target_name>:[ManagedNode|PcManagedNode|NetwareManagedSite]

82 Version 3.7

RCACTN The Tivoli Remote Control action. It can have one ofthe following values:[rc|rd|reboot|filexfer|chat]

RCOPTS Displays all the Tivoli Remote Control options in theWeb Interface if its value is Y.

Note: The default.html page must be reloaded after making anychanges. To do this, issue the commands wstophttpd andwstarthttpd on the Tivoli Management Framework commandline.

Alternatively, you may enter the desired parameters in the browsercommand line.

If you wish to use your own web page, you must call thestartsession.cgi script using the following syntax:startsession.cgi ? RemoteControl=x & Controller=x & Target=x & Action=x[& G=x & P=x & D=x & B=x & C=x & T=x & Z=x & R=x & I=x & S=x]

Where:

RemoteControl The name of the Tivoli RemoteControl tool

Controller The controller name. Must have theformat: <controller_name>#Endpoint

Target The target name. To define thetarget, use the following syntax:<target_name>:[ManagedNode|PcManagedNode|NetwareManagedSite|Endpoint]

Action The Tivoli Remote Control action. Itcan have one of the followingvalues:[rc|rd|reboot|filexfer|chat]

For explanations of remaining options, see “wrc” on page 145.


3.C

on

figu

ring

and

Startin

gTivo

liR

emo

teC

on

trol

From a Terminal Server EnvironmentYou can start a Tivoli Remote Control action from a controller thatis a Terminal Client. To do so, when Windows Terminal Server is insession, run TRCWTS.EXE from the following directory:<LCF_dir>\PCREMOTE\<plw32-ix86>\CTL

where:


<w32-ix86> applies only where Windows Terminal Server issupported

This will cause the default web browser to open the default page ofthe Remote Control Windows Terminal server.

TRCWTS.EXE can also be run from the command line.

84 Version 3.7

Customizing the Web InterfaceTo customize the Web Interface page, started from a WindowsTerminal Server Client, do the following from the WTS console:

¶ Open the shortcut to TRCWTS.EXE

¶ In the Properties/Target field write:TRCWTS.EXE RCOPTS=Y&.......

When specifying parameters, use the same syntax as used in theDefault.html page. However, do not specify the RCCOID andRCDISP parameters as these are automatically added byTRCWTS.EXE

From a Command LineThe command line interface (CLI) is normally used by otherapplications to perform Tivoli Remote Control activities. You cantype commands into the CLI yourself, but many people find it hardto remember the correct parameters. For the worst case, see thecommand wrc on page 145.


3.C

on

figu

ring

and

Startin

gTivo

liR

emo

teC

on

trol

86 Version 3.7

Using Remote Control andReboot Actions

This chapter describes how to use the Remote Control action tomonitor or control a target. It also describes how you can use theReboot action to reboot a target.

The Remote Control session is independent of other Tivoli RemoteControl actions and can run concurrently with Remote Diagnosis,File Transfer, and Chat sessions.

You can run one or more Remote Control sessions at the same time.

Using the Reboot ActionTo reboot a target from the controller, you select the Reboot actionas described in “Starting a Tivoli Remote Control Action” onpage 77.

In a multi-boot target, the target is rebooted into the defaultoperating system.

Using the Remote Control ActionYou can use the Remote Control action to view the screen displayof one or more targets at the same time. Each target is shown in aseparate window. The title bar of the window includes the name ofthe current target.

4


4.U

sing

Rem

ote

Co

ntro

lan

dR

ebo

ot

Actio

ns

Starting and Ending a Remote Control SessionTo start a Remote Control session, you select the Remote Controlaction as described in “Starting a Tivoli Remote Control Action” onpage 77.

When the session starts, the state is Active or Monitor depending onthe setting for the initial state. See “Changing the Values of Activityand Display Settings” on page 55. The states are described in“Changing the Session State” on page 89.

The session state and the keyboard mode are indicated either in thetitle bar, or in the lower right corner of the window, depending onthe operating system of the controller.

To close a Remote Control session, select Exit from the File menu.

The Remote Control WindowDuring a Remote Control session, the Remote Control window isdisplayed at the controller.

The menus are:

88 Version 3.7

File Has options to save the target screen as a bitmap;print the contents of the window to the defaultprinter; display a print preview of a document (notavailable for OS/2); and to exit to the targets list.

Keystrokes Has options to switch between keyboard modes, andto send key sequences to the target. For moreinformation, see “Switching between KeyboardModes” on page 91 and “Sending System Keys” onpage 92.

State Has options to switch between active, monitor andsuspend states. For more information, see “ChangingStates from the Controller”.

View Has options to show or hide the toolbar and statusbar. This menu is not available for OS/2.

Help Provides information about the Tivoli RemoteControl product.

Changing the Session StateEither the administrator or the target user can change the sessionstate.

Changing States from the ControllerYou can change the session state by selecting an option from theState menu.

Active Takes control of the keyboard and mouse of thetarget. The target user cannot control the mouse orkeyboard unless the user presses the <Alt><T> keysequence (if authorized to do so). In that case, youare locked out until the target’s user chooses a newstate. If a session inactivity timeout applies, thesession will end if you do not move the mouse oruse the keyboard.

Monitor Displays the screen contents of the target. You donot control its keyboard and mouse input. You do notsee the mouse pointer of the target, but you see theeffects of what it does.


4.U

sing

Rem

ote

Co

ntro

lan

dR

ebo

ot

Actio

ns

Suspend Suspends the session. You are still connected to thetarget but you cannot control the target or view anyscreen updates. You can return to the active ormonitor state without restarting the session.

Terminate Ends the session and the connection to the controller.

The Active state is not available if:

¶ You have only the remote_monitor role for the target. See“Assigning Roles” on page 52.

¶ The rc_def_rcmode policy method specifies monitor mode only.See “rc_def_rcmode” on page 71.

Changing States from the TargetDuring a session, one of the following icons may be displayed onthe target, depending on the session state. The default is set by therc_def_alt_t policy method: see “rc_def_alt_t” on page 61.

¶ On the desktop of an OS/2 target (only if enabled):

¶ On the taskbar of the Windows target:

90 Version 3.7

The following dialog is displayed if the target user types the<Alt><T> key sequence, or if:

¶ On OS\2, the target user clicks the ALT+T icon

¶ On Windows, the target user double-clicks the ALT+T icon

The user can then change the session state. For an explanation of thedifferent states, see “Changing States from the Controller” onpage 89.

Switching between Keyboard ModesYou can switch keyboard modes only when the state is Active. In theActive state:

¶ If the keyboard mode is Remote, keystrokes are sent to thetarget

¶ If the keyboard mode is Local, keystrokes have a local effect

To switch between keyboard modes, either:

¶ Press the <Alt><T> key combination, -or-

¶ Select either Toggle mode to remote or Toggle mode to localfrom the Keystrokes menu


4.U

sing

Rem

ote

Co

ntro

lan

dR

ebo

ot

Actio

ns

Sending System KeysSome key sequences cannot be sent to the target using the keyboardbecause they are handled by the local operating system. However,you can send these sequences by selecting Send system keys fromthe Keystrokes menu. You can then choose the appropriate option orclick the corresponding icon.

The effect of a key sequence depends on the operating system of thetarget. The example sequences listed below are for Windowsplatforms.

Alt+Esc Switches to the next window on the target.

Alt+Tab Switches to the last window on the target.

Ctrl+Esc Displays the Task List dialog on the target.

Note: You cannot send the Windows Start keyfunction to display the task list. Use theCtrl+Esc sequence instead.

Ctrl+Shift+EscActivates the Task Manager (Windows NT 4.0 orWindows 2000 target only).

Ctrl+Alt+Del Displays the Security dialog on Windows NT andWindows 2000 targets, and the End Task dialog onWindows 95 and Windows 98 targets. This option isnot available for OS/2 targets.

Note: If the session ends abnormally when you arelogged on to a Windows NT target from acontroller, you are automatically logged off. Ifthe target user is logged on and the sessionends abnormally, the target user is notautomatically logged off.

IME hot key Enables and disables the input method editor (IME)on a DBCS (double byte character set — characterrepresentation system used in Far Eastern countries).This option is disabled if the target is SBCS (single

92 Version 3.7

byte character set — character representation systemused system used in Western countries).

Mixed KeyboardsTivoli Remote Control supports key conversion between a controllerand a target with different keyboards, that is, when you press a keyon the controller keyboard, the associated character is displayed onthe target screen. The key conversion has the following limitations:

¶ To convert a key on the controller keyboard, the associatedcharacter must be present on the target keyboard.

¶ Some key combinations on the controller keyboard are convertedto different characters on the target screen. For example, whathappens if you press an accent followed by a vowel on a Frenchkeyboard? The result is that a single character (the accentedvowel) is displayed on the controller screen, but two characters(the accent and the vowel) are displayed on the target screen.

The following table shows the keyboard types for which TivoliRemote Control supports the key conversion. Note that thekeyboards on the same table row are the same type of keyboard. Thekeyboard types are named as they are identified in the relatedoperating system.

Windows NT Windows 95 OS/2

Belgian French Belgian Belgian

Brazilian (ABNT) Portuguese Brazilian(ABNT2)

Brazilian (275)

Chinese (Simple) Chinese (Simple) Chinese (Simple)

French French French

German German German

Italian Italian Italian

Japanese (5576-002)(5576-003) (5576-A01)(5576-B01) (5576-B05)

(5576-C01)

Japanese (5576-002)(5576-003) (5576-A01)(5576-B01) (5576-B05)

(5576-C01)

Japanese (5576-002)(5576-003) (5576-A01)(5576-B01) (5576-B05)

(5576-C01)

Korean Korean Korean


4.U

sing

Rem

ote

Co

ntro

lan

dR

ebo

ot

Actio

ns

Windows NT Windows 95 OS/2

US US United States

US-Dvorak US-Dvorak

US-International US-International

94 Version 3.7

Using the Chat Action

This chapter describes how to use the Chat action to exchangemessages with the user of a target.

The Chat session is independent of other Tivoli Remote Controlactions and can run concurrently with Remote Control, File Transfer,and Remote Diagnosis sessions.

You can run one or more Chat sessions at the same time.

Starting and Ending a Chat SessionTo start a Chat session, you select the Chat action, as described in“Starting a Tivoli Remote Control Action” on page 77.

When the session starts, the Chat window appears on both controllerand target. See “The Chat Window”.

Either the administrator or the target user can close a Chat session.

To close a session, click the Terminate icon, or select the Terminateoption from the Actions menu. The Chat window disappears fromboth controller and target.

The Chat WindowDuring a Chat session, the Chat window is displayed at thecontroller and target. At the target, the title bar shows the user of thecontroller. At the controller, it shows the name of the target.

5


5.U

sing

the

Ch

atA

ction

The Chat window has two main areas, the Send zone and theHistory zone. You can move the horizontal divider separating theHistory and Send zones by clicking and dragging.

The Send zone displays the text you want to send. The History zonedisplays all the messages from the current conversation, inchronological order.

The following table describes the menus and icons in this window.

Icon Menu option Function

Actions>Suspend Suspends the Chat session on bothcontroller and target

96 Version 3.7


Actions>Active Enables the Chat session on bothcontroller and target

Actions>Terminate Terminates the Chat session

Actions>Log Enables logging of Chat messages

Actions>No Log Disables logging of Chat messages

Edit>Send Sends the text in the Send zone tothe target

Edit>Clear Deletes text from the Send zone

Exchanging messagesTo send a message from controller or target:

1. Type the text into the Send zone. You can copy and paste text inthe usual way, and use the <Backspace>, <Delete> and <Tab>keys for editing. You can clear text by pressing the keycombination <Ctrl><Shift><Delete>.

2. Press <Enter>, or click the Send icon, or select the Send optionfrom the Edit menu.

The message appears in the History zone of both sender andreceiver.

The receiver can then type and send a reply using the Send zone.The History zone is write protected, but you can copy text from it inthe usual way.

Any further messages are appended to the previous messages in theHistory zone.


5.U

sing

the

Ch

atA

ction

If logging is enabled, details of the Chat conversation are recordedin the Chat log file. See “Recording Chat Events”.

Suspending and Reactivating a Chat SessionTo suspend a Chat session, click the Suspend icon, or select Suspendfrom the Actions menu. The Send zone is suspended on both thecontroller and target.

To reactivate the Send zone, click the Active icon, or select Activefrom the Actions menu. The Send zone is disabled if the Chatwindow is minimized or put in background. If you receive amessage while the Chat window is minimized, you are informed bya system message.

Recording Chat EventsDuring a Chat session, informational events or errors are recorded inthe files: RCCTL_CH.LOG (controller) and RCTGT_CH.LOG(target).

To log the Chat conversation, click the Log icon, or select the Logoption from the Actions menu (Actions->Log).

When you enable logging, a dialog appears for you to choose thelocation of the new log file RC_CHAT.LOG. The default location isthe directory where Tivoli Remote Control is installed.

Note: To see DBCS localized characters correctly, the followingfiles must be opened using a UTF-8 viewer: RCCTL_CH.logand RCTGT_CH.log.

For more information, see “Logging Session Events” on page 161.

98 Version 3.7

Using Chat with Remote ControlWhen you start a Chat session while a Remote Control session is inan Active state, the Remote Control session is suspended. The targetuser can then use the keyboard and mouse for the Chat session.

The Remote Control session is reactivated if:

¶ The Chat session is closed or suspended

¶ The target user selects a different application.

When you start a Chat session while a Remote Control session is inMonitor state, both sessions run normally.


5.U

sing

the

Ch

atA

ction

100 Version 3.7

Using the File Transfer Action

This chapter describes how to use the File Transfer action to transmitfiles or directories between controller and target.

The File Transfer session is independent of other Tivoli RemoteControl actions and can run concurrently with Remote Control,Remote Diagnosis, and Chat sessions.

You can run one or more File Transfer sessions at the same time.

Starting and Ending a File Transfer SessionTo start a File Transfer session, you select the File Transfer action,as described in “Starting a Tivoli Remote Control Action” onpage 77.

When the session starts, the File Transfer window appears on thecontroller. See “The File Transfer Window” on page 102.

To close a File Transfer session, select the Exit option from the Filemenu.

6


6.U

sing

the

File

Transfer

Actio

n

The File Transfer WindowDuring a File Transfer session, the File Transfer window is displayedat the controller. The title bar shows the name of the target.

The File Transfer window has two main areas, the Local Systemzone and the Remote System zone. You can move the verticaldivider separating the two zones by clicking and dragging.

The Local System zone displays the file system of the controller.The Remote System zone displays the file system of the target.

To expand or contract a directory, you double-click it in the usualway.

The following table describes the menus and icons in this window.Many of the options are also available in a context-sensitive pop-upmenu that is shown by right-clicking inside the window.


File>Copy Sets the files or directories that arethe source of the copy

102 Version 3.7


File>Paste Sets the directory of the destinationand starts copying the files. Youcannot select a destination until youhave selected a source

File>Make Directory Creates a new subdirectory in theselected directory

File>Delete Deletes the selected files ordirectories

File>Refresh Refreshes the display of theselected directory

Copying filesThe File Transfer action enables a selected directory or file to becopied between machines that are both running a File Transfersession.

To copy a directory structure or file, use one of the followingmethods. In both cases, you can make selections by clicking on theappropriate file or directory icons. To select multiple items, use thecombinations <shift-click> and <ctrl-click> in the usual way.

To transfer files or directories using drag and drop:

1. Select the source files or a directory tree, then drag and dropthem on the new location.

To transfer files or directories using menu options:

1. Select the source files or a directory tree using the Copy optionfrom the File menu.

2. Select the destination using the Paste option from the File menu.Clicking in the Paste dialog starts the transfer.


6.U

sing

the

File

Transfer

Actio

n

Making DirectoriesTo make a new directory:

1. Select the parent directory for the new directory

2. Select the Make Directory icon or menu option. This displays theMake Directory dialog

3. Type the name of the new directory and click OK

Deleting Directories and FilesTo delete a file or directory:

1. Select the file or directory. To select multiple items, use thecombinations <shift-click> and <ctrl-click> in the usual way.

2. Select the Delete icon, menu option, or popup menu, or press theDel key.

3. Click Yes.

Recording File Transfer EventsDuring a File Transfer session, informational events or errors arerecorded in log files: RCCTL_FT.LOG (controller) andRCTGT_FT.LOG (target).

For more information, see “Logging Session Events” on page 161.

104 Version 3.7

Using the Remote DiagnosisAction

This chapter describes how to use the Remote Diagnosis action toidentify and solve PC problems.

You can run the Remote Diagnosis action only when both thecontroller and the target are endpoints.

The Remote Diagnosis session is independent of other Tivoli RemoteControl actions and can run concurrently with Remote Control, FileTransfer, and Chat sessions.

You can run one or more Remote Diagnosis sessions at the sametime providing the targets are different.

IntroductionRemote Diagnosis has functions for:

¶ Comparing a target configuration with a saved version, andrestoring the saved version. See “Restoring TargetConfigurations” on page 113.

¶ Running Diagnosis Packs, for each Diagnosis Pack you can:

v Run diagnostic scripts on a target. A diagnostic scriptanalyzes, and sometimes resolves, problems with applications.See “Analyzing and Solving Target Problems” on page 112.

7


7.U

sing

the

Rem

ote

Diag

no

sisA

ction

v Protect, verify, and restore vital objects. This consists ofcomparing vital objects with saved versions, and restoring thesaved versions. Vital objects are things such as configurationfiles and registry keys. See “Protecting and Restoring VitalObjects” on page 114

v Download artifacts such as traces and logs from the target.See “Working with Artifacts” on page 115

¶ Browsing a Common Information Model (CIM) database on thetarget. See “Optional Tools” on page 121

¶ Executing a remote command on the target. See “RemoteExecution Command” on page 121

Starting and Ending a Remote Diagnosis SessionTo start a Remote Diagnosis session, select the Remote Diagnosisaction, as described in “Starting a Tivoli Remote Control Action” onpage 77.

When the session starts, the Remote Diagnosis window appears onthe controller. See “The Remote Diagnosis Window” on page 107.The diagnosis packs available for the selected target (previouslyinstalled using wrcinstep) appear in the Index Tree zone, in theDiagnosis Packs folder.

To close a Remote Diagnosis session, select the Exit option from theFile menu or click the Exit button on the toolbar.

Note: The Remote Diagnosis action activates two sioux.exeprocesses on the target. If the Remote Diagnosis sessionterminates abnormally, the following message appears on thecontroller:An unexpected error occurred: The console will be closed.The Java stack trace will be saved in the fileTSEtrace.out in the <controller directory>.

In this case, the sioux process should be killed on the targetside. If it remains active, it can be killed usingshutdown.pl

106 Version 3.7

from any browser as follows:http://agent_name:agent_def_port/shutdown.pl

where:

agent_name The target host name or IP address

agent_def_portEither:

the port number defined in rc_def_ports:rd TIP:0 CIP:0 TXP:0 CXP:0

or is default port 2504

The Remote Diagnosis WindowDuring a Remote Diagnosis session, the Remote Diagnosis windowis displayed at the controller side. The title bar shows the name ofthe target.


7.U

sing

the

Rem

ote

Diag

no

sisA

ction

The Remote Diagnosis window has two main areas, the Index Treezone and the Report View zone. You can move the vertical dividerseparating the two zones by clicking and dragging.

The Index Tree zone contains two folders:

¶ The Saved Configurations folder, containing all the previoussaved configurations.

¶ The Diagnosis Packs folder, containing all the diagnosis packsfor the current target.

To expand or contract a folder, you double-click it in the usual way.

The Report View zone displays information about the diagnosticactions performed on the target.

The following table describes the menus and toolbar buttons in theRemote Diagnosis window. Many of the options are also available ina context-sensitive pop-up menu that appears by right-clicking insidethe window.


File>New Sets the interface for a new diagnosis session. Use thisoption after you run the Open option.

File>Open Opens and browses a saved report of a session.

File>Save Saves the current Remote Diagnosis session. If you usethis option for the first time, its behavior is the same asthe SaveAs option. You can save the Remote Diagnosissession in a specific disk drive or directory. Specify aname to save a new session.

File>SaveAs Saves the current Remote Diagnosis session with thefilename you specify.

File>Properties Either, shows the information specified for a savedRemote Diagnosis session. Or, enables you to enterinformation on the current session.

108 Version 3.7


File>Exit Closes the current Remote Diagnosis session.

Action>Save Config Appears when the Saved Configurations folder isselected, if the Tivoli administrator has been assignedthe remote_vitalobjects role.

Saves the current target configuration in an entry in theSaved Configurations folder.

Action>Differencing

Appears when a Saved Configurations file is selected, ifthe Tivoli administrator has been assigned theremote_vitalobjects role.

Compares the selected and current configurations. Anydifferences are displayed in a table in the Report Viewzone.

Action>Run Appears when a Diagnosis Pack is selected in the IndexTree zone. Used to run the following functions:Diagnosis, Verify, and Artifacts. This action can also beperformed by double-clicking the desired Packs icon inthe Index Tree zone. Availability of these functionsdepends upon which diagnosis pack is selected and theappropriate role(s) being assigned.

Action> Diagnosis Appears when a Diagnosis Pack is selected in the IndexTree zone. But only if the Tivoli administrator has beenassigned the remote_diagnosis role.

Starts the diagnosis script for the failing application onthe current target. The diagnostic report is displayed inthe Report View zone.

Action> VitalObjects

Appears when a Diagnosis Pack is selected in the IndexTree zone. But only if the pack contains a vital objectdefinition file and the Tivoli administrator has beenasigned the remote_vitalobjects role. It has thefollowing options:

View Appears only after Protect has been run.Displays protected vital objects.


7.U

sing

the

Rem

ote

Diag

no

sisA

ction


Protect Protects vital objects. For information onprotecting vital objects, see Tivoli RemoteControl Programming for RemoteDiagnosis.

Verify Appears only after Protect has been run.Compares the current state of a vital objectwith one previously saved with Protect. Itidentifies any changes that have occurredand you can select what must be restored.

Restore Appears only after Protect has been run.Restores all the vital objects saved with aprevious Protect.

Action> Artifacts Appears when a Diagnosis Pack is selected, but only ifthe pack contains an artifact definition file and theTivoli administrator has been assigned theremote_artifacts role.

Logs, reports, and other information, associated with thefailing application, are collected. The Artifacts actionhas the following options:

Save Zips all files and downloads the zip file onthe current controller.

Mail Sends the zip file containing all artifatcs toa mail address.

View Views the selected artifacts file using thedefault editor. For OS/2, an Open dialogappears which you must use to set theassociation between the editor and artifactfiletype. The selected editor is then used toview all artifacts files with the same filetype.

Extract Extracts a selected file on the controller.

Tools>xxx Used to run any user-installed tools, such as the CIMBrowser.

Customize> Options Used to select a Web browser and set mail configurationfields.

110 Version 3.7


Help> Help Topics Displays online help.

The History Tool bar enables you to navigate through the diagnosticreports of current or previously saved Remote Diagnosis sessions.The session is displayed as a tree of reports. The navigation iconsare shown in the following table.

Icon Function

Selects a diagnostic report

Displays the report associated with the actionthat originated the current report.

Displays the report associated with the actionthat follows the current report.

Displays the report associated with the actionthat precedes the current report.

Allows you to stop the current action.

Note: Using the stop icon stops the reception of data from thecontroller, but the action will continue to run on the target.

Using Save Configuration and StopThere is a consequence to launching a Save Configuration orProtect on a target, from a Remote Diagnosis session, andimmediately stopping it.

During the same session no new entries are displayed in the SavedConfiguration folder or no protected objects appear. But, if youestablish a new RD session with the same target, the new Saved


7.U

sing

the

Rem

ote

Diag

no

sisA

ction

Configuration and new protected objects are shown listed in therelated folder. You can then launch a Differencing, View, Verify orRestore .

Analyzing and Solving Target ProblemsDuring a Remote Diagnosis session, you have four ways to analyzeand try to solve problems on targets. You can:

¶ Save and restore target configurations.

¶ Launch a diagnosis action (if the appropriate diagnosis pack hasbeen downloaded to the target. See “Installing Tools, Plugins,and Diagnosis Packs” on page 18 for more information).

¶ Launch any user-installed tool:

1. Browse the target CIM database (if the tool has beendownloaded to the target and the plug-in downloaded to thecontroller. See “Installing Tools, Plugins, and DiagnosisPacks” on page 18 for more information).

2. Launch a remote command on the target.

Saving Target ConfigurationsYou can save the current configuration of the target as follows:

1. Select the Saved Configurations folder.

2. Select the Save config icon, menu option, or pop-up menu. Thetarget configuration is saved as a file in the Save Configurationsfolder. The name of the file is the date and time of its creation.

The list of objects that is protected with Save Configurations for agiven target is defined in the system.rdp file, located in theTGT/root folder. A default system.rdp is installed with the product.Be aware, though, that this system.rdp file ensures only defaultprotection of the target system.

For information on how to extend this default protection, see TheRDP File section in Tivoli Remote Control Programming for RemoteDiagnosis.

112 Version 3.7

Restoring Target ConfigurationsYou can restore a saved configuration as follows:

1. Select a saved configuration file in the Saved Configurationsfolder. For example:

2. Select the Differencing icon, menu option, or pop-up menu. Theselected configuration is compared with the current configuration.Any information that has been changed or deleted is displayed inthe Report View zone.

3. From the Report View zone, you can:

¶ Repair selected items by clicking the Repair button.

¶ Recursively repair selected and nested items by clicking theRecursive Repair button.

¶ Navigate through the objects using the Expand All, CollapseAll, Select All, Invert Selection buttons.

Running a Diagnosis PackA diagnosis pack includes three possible functions:

¶ Running diagnostic scripts

¶ Protecting and restoring vital objects such as configuration filesand registry keys

¶ Downloading traces, logs or other artifacts

A useful method of running a diagnosis pack is by selectingAction->Run from the Action menu, or using the toolbar button, orpop-up menu. This runs the root diagnostic script, verifies protectedvital objects, and displays artifacts.

For more information, see the Tivoli Remote Control Programmingfor Remote Diagnosis.

Running Diagnostic ScriptsTo run a diagnostic script, do the following:


7.U

sing

the

Rem

ote

Diag

no

sisA

ction

1. Select the diagnosis pack for the application from the DiagnosisPacks folder.

2. Select Action->Diagnosis from the Action menu, or use thetoolbar button, or pop-up menu.

3. Perform any actions that are asked for in the Report View zone.

If you need to create your own diagnosis pack, refer to the TivoliRemote Control Programming for Remote Diagnosis.

Protecting and Restoring Vital ObjectsTo protect the vital objects:

1. Select the diagnosis pack for the application from the DiagnosisPacks folder.

2. Select Vital Objects>Protect from the Action menu, or use thetoolbar button, or pop-up menu. This action is available only ifvital objects have been defined and if the Tivoli administratorhas been assigned the remote_vitalobjects role.

3. To see what has been protected, select Vital Objects>View fromthe Action menu, or use the toolbar button, or pop-up menu.

To find out if any of the vital objects of a specific diagnosis packare corrupted, do the following:

1. Select the diagnosis pack for the required application from theDiagnosis Packs folder.

2. Select Vital Objects>Verify from the Action menu, or use thetoolbar button, or pop-up menu.

In the Report View zone, the vital objects appear that havechanged since the last protect action was performed. You cannavigate through the objects using the Expand All, Collapse All,Select All, Invert Selection buttons.

To restore protected vital objects, you can:

¶ Run the Verify action. Then repair the selected vital objects byclicking the Repair button in the Report View zone.

114 Version 3.7

¶ Run the Verify action. Then recursively repair the selected andnested vital objects by clicking the Recursive Repair button inthe Report View zone.

¶ Restore all the protected vital objects by selecting VitalObjects->Restore from the Action menu, or using the toolbarbutton, or pop-up menu.

Working with ArtifactsArtifacts contain specified files, such as logs, traces, diagnostic files,and so on. For further information on defining artifacts, see theTivoli Remote Control Programming for Remote Diagnosis.

To store artifacts on the controller, do the following:

1. Select the desired diagnosis pack (if available) from theDiagnosis Packs folder.

2. Select Action->Artifacts from the Action menu, or use thetoolbar button, or pop-up menu.


7.U

sing

the

Rem

ote

Diag

no

sisA

ction

SaveUse Save to download all artifacts in a zip file on the controller.

MailUse Mail to send the zip file containing all artifatcs to an e-mailaddress.

¶ To:

¶ Cc:

¶ Subject:

116 Version 3.7

The name of the mail originator will also appear in the Cc: field.This ensures that the originator receives a copy of the mail sent.

ViewUse View to display the selected artifacts file using the defaulteditor.

The View panel has the following fields:

File System Refers to the dir, file,winfolder Vital Objects

Windows Registry Refers to the winregkey,winregvalue Vital Objects

Windows Profiles Refers to the winprofitem,winprofsection Vital Objects

Services Refers to the winservice VitalObject

Windows Shell Refers to the winshortcut VitalObject


7.U

sing

the

Rem

ote

Diag

no

sisA

ction

Note: For OS/2, an Open dialog appears which you must use to setthe association between the editor and artifact filetype. Theselected editor is then used to view all artifacts files with thesame file type.

ExtractUse Extract to extract a selected file on the controller.

Customizing Web Browser and Mail OptionsSelecting Customize->Options makes the Customized Optionswindow appear. Use the Browser tab to define your web browser.

By selecting the Mail tab you can define the following options:

Saving Remote Diagnosis Sessions for Later UseTo save a Remote Diagnosis session for later use, select Save orSave As from the File menu, or use the toolbar button, and specify afile name.

Before saving a session, you can set the session properties using theProperties dialog from the File menu (File->Properties).

118 Version 3.7

Viewing a Saved Remote Diagnosis SessionTo view a saved Remote Diagnosis session, select Open from theFile menu or select a toolbar button and specify the name and pathof the file where the session has been previously saved.

To view the properties of a saved session select Properties from theFile menu.

When you are viewing a saved session, you cannot run any actions.To run additional diagnostic actions, select New from the File menu.


7.U

sing

the

Rem

ote

Diag

no

sisA

ction

120 Version 3.7

Optional Tools

This chapter covers the optional tools that are supplied with TivoliRemote Control

Remote Execution CommandRemote Execution Command is a tool that enables you to runcommands on a remote PC from a local one.

To display the Remote Execution Command window, selectTools->Remote Command Execution from the Tools menu.

Notes:

1. All commands that you launch on the target machine are runfrom the LCF. This means, for example, that the ″net use″command does not function.

8


8.O

ptio

nal

Too

ls

2. The commands that you launch may require user intervention atthe target. Therefore, do not use commands that require inputinput from a remote location if that location is unattended. See“Frequently Asked Questions” on page 131.

The CIM Browser ToolYou use the CIM Browser tool to ivestigate target configurationproblems. To do this, the CIM Browser PlugIn must be installed onthe controller and the CIM Query tool on the target.

Using the CIM BrowserThe CIM Browser tool gives an administrator easy access to a CIM(Common Information Model) database on a target. A machine’sCIM database holds a wide range of information about the machine’shardware and software configuration. CIM database information canhelp to diagnose many kinds of system failures.

CIM databases are accessed using object oriented schema. Becauseof the large number of classes, it is not easy to find the classcorresponding to the information you need. To make the CIMinformation easier to access, CIM Browser enables you to search forthe appropriate class using natural language keywords. You can thenbuild the query to the target database using point and click selection.The results of the query are displayed as a browsable list ofproperties and values.

Note: The CIM Browser and Remote Diagnosis console support thesame platforms as follows:

¶ As controllers:

v Windows 95, Windows 98, Windows NT 4.0,Windows 2000, and OS/2

¶ As targets:

v Windows 95, Windows 98, Windows NT 4.0 andWindows 2000

122 Version 3.7

What Do You Need to Run CIM Browser?Before starting CIM Browser, you must:

1. Download Microsoft Windows Management Instrumentation(WMI) on Windows 95, Windows 98, and Windows NT 4.0targets from the following URL:http://msdn.microsoft.com/downloads/sdks/wmi/eula.asp

Note: WMI is shipped with Windows 2000, therefore no need todownload.

2. Follow the instructions that appear on the screen.

3. Install the Tivoli CIM Browser PlugIn on the controller and theCIM Query Interface Tool on the target. For further information,see “Installing Tivoli Remote Control” on page 7.

Starting and Ending the CIM Browser ToolTo start the CIM Browser Tool:

1. Run a remote diagnosis session.

2. Select Tools>CIMBrowser from the Tools menu of the RemoteDiagnosis window. The CIM Browser window appears (see thenext paragraph).

3. Check the message that appears in the report view zone, movingany windows if necessary. This message concerns the versionnumber of WMI installed.

To end the CIM Browser Tool session, select the Exit option fromthe File menu or click the Exit button on the toolbar. The sessionwill also be closed if you end the Remote Diagnosis session.

CIM Browser WindowThe CIM Browser window consists of the following elements: TitleBar, Menu Bar, Tool Bar, Class Search Panel, Schema Tree Panel,


8.O

ptio

nal

Too

ls

Query Results Panel, and Status Bar.

Title barThe title bar displays either the host name or ip address that thebrowser is connected to.

Menu barThe CIM browser menu bar contains three menus as follows:

¶ File

v Exit the CIM browser

¶ Query

v Show the current query

v Clear the query

v Send the query

v Stop the query

¶ Help

v Contents (show the available help documents)

Some menu commands have quick access buttons on the toolbar.

124 Version 3.7

ToolbarThe toolbar buttons are as follows:


Searches the conceptentered in the in theSearch a CIM conceptfield

Query>Clear Clears the current query

Query>Show Shows the currentquery

Query>Send Sends the current queryto the target

Query>Stop Cancels the currentquery

File>Exit Exits the CIM browser

Help>Contents Shows the availablehelp documents

Class Search PanelThe Class Search Panel contains a text entry field and a hit list.

In the text entry field, search a CIM concept, you type a text stringto be used for searching the CIM schema. Blank characters are


8.O

ptio

nal

Too

ls

interpreted as term separators. No boolean operators are allowed, soany standard boolean keyword (such as AND, OR, NOT) will betaken as is.

The hit list shows the list of CIM classes associated wth one or moreof the search terms. By selecting a CIM class from the hit list, theClass Schema Tree moves to the corresponding node.

Schema Tree PanelThe Schema Tree panel shows the elements of the standard CIMschema.

The schema is in accordance with the DMTF(DistributedManagement Task Force) CIM 2.2 specification. For furtherinformation, see: http://www.dmtf.org/spec/cim_spec_v22/

Schema Tree ElementsThe Schema Tree has seven kinds of elements. Homogeneouselements are grouped into standard folders.

Icon Name Description

class A CIM class

documentation The documentation of either a class or aproperty

126 Version 3.7

Icon Name Description

property A CIM class/association property, i.e. anattribute ranging over a CIM type

property value The value given to a property as aconstraint for selecting CIM instances

association role The role that class plays with respect to aCIM association

association A CIM association, i.e.a relationship thatholds between two classes

reference The reference to a class within anassociation

These elements are arranged according to the following hierarchy:

classdocumentationproperty

documentationproperty value

association roleassociationdocumentationreference

Schema Tree ActionsClicking the left mouse button on any of the Schema Tree elementshas the following context sensitive meaning:

Element Effect:

class mark the class as the query subject (e.g.SELECT * FROM <classname>)

documentation undefined

property mark the property as a query specification(e.g. SELECT * FROM <classname> WHERE<property name> EQUALS <value>)

property value constraint edit the property’s constraint value


8.O

ptio

nal

Too

ls

Element Effect:

association role undefined

association undefined

You can select only one class at a time. However, you can select anynumber of properties of the class hierarchy.

Clicking on the expand marker on documentation nodes shows thedocumentation text. Clicking on the expand marker on any othernode expands the corresponding element.

The Meaning of the Schema Tree SelectionThe selection of a (single) class of the CIM Schema Tree isinterpreted as the query subject. According to the standard relationalterminology, the selected class corresponds to the table of a SELECTclause.

Selecting a number of class properties narrows the query to thoseinstances of the selected class where all the instance properties,corresponding to those selected by the user, exactly match thespecified value. According to the standard relational terminology, theselected properties correspond to a WHERE clauses connected byAND whose terms are characterized by the EQUALS operator.

Query Results PanelAccording to the CIM terminology, an instance represents areal-world managed object that belongs to a particular class. In otherwords, instances are actual data aggregations whose structurecomply with that provided by the class they belong to.

128 Version 3.7

The Query Results Panel appears as the right area of the CIMBrowser window.

It has two components:

¶ An instance list

¶ A table of properties and their values for the instance selectedfrom the instance list

Status BarThe status bar displays the micro help associated with the toolbarbuttons. It also displays the status of the query when you send to thetarget.

How to Build a QueryTo search the CIM class you are interested in, do the following:

1. Enter search keywords in the Class Search Panel

2. Press <ENTER> or click the Search Icon. The class list appears

3. Select a desired row in the class list. You will be lead to thecorresponding entry in the Schema Tree Panel


8.O

ptio

nal

Too

ls

4. If needed, read the class documentation by expanding thedocumentation Tree element in the Schema Tree Panel

Compose and Send a QueryTo compose and send a query, do the following:

1. Select the class you are interest in.

2. If needed, refine the query by choosing properties values.

3. You may like to check the actual query string by selectingQuery->Show from the Query menu or using the Query Showbutton

4. Send the query by selecting Query->Send from the Query menuor using the the Query Send Icon

Refining the QuerySome classes have properties for which you can specify a value inthe query. Such properties are shown in the class schema tree withan ″ab″ or ″01″ or 0/1″ marker and an asterisk. You can specifyvalues for as many properties of one class as required. By selectingvalues for class properties, you narrow the query to those instancesof the selected class where the instance properties exactly matchyour specified value.

To specify a value do the following:

1. Click the marker

2. Type the value

3. Press Enter

How to Clear a QueryTo clear a query, select Query->Clear from the Query menu or usethe toolbar button.

130 Version 3.7

Frequently Asked Questions

These frequently asked questions (FAQs) are provided to help clarifysome aspects of Tivoli Remote Control or to tell you aboutworkarounds or shortcuts that are useful in daily operation.

InstallationWhat can I do if something goes wrong when I am installing acontroller or target on an endpoint?

You can look at the following file:<LCF_dir>\DAT\<n>\lcfd.log where <LCF_dir> is thedirectory in which the Tivoli Management Agent has beeninstalled and <n> is the integer value that specifies theendpoint connection number. This file contains a detailed listof informational and error events that occur on the endpoint.

Note: To view lower-level error information, set the loggingthreshold to 3 or 4 in the last.cfg file and restartthe endpoint. Alternatively, restart the endpoint fromthe command line using the -d parameter. Forexample: ’lcfd -d 3 would start the endpoint and setthe logging_threshold to 3. See the Tivoli FrameworkReference manual for details on using the lcfdcommand.

Why does installing the target software automatically not rebootthe system after the installation is completed?

A


A.

Freq

uen

tlyA

skedQ

uestio

ns

It is not always desirable to reboot a target machineimmediately, especially if the user is working. You can usethe Remote Reboot function to immediately force a restart.The reboot function uses the Tivoli Management Agent, butdoes not need the new drivers.

I just upgraded Remote Control to 3.6.5, but when I attempt totake control of certain Endpoints, I get an error message about’ADR decode string error...’. What is wrong?

This error is usually caused by the Remote Control Serverbeing at a different code level on the Endpoint Gateway thatis hosting the Endpoint that was selected when this erroroccurred. Please ensure that ALL Endpoint Gateways havethe same Remote Control Release and Patch level installed.

What should I do if after having installed the patch on agateway, I try to start a session with an endpoint of that gatewayand I receive an error message like ″Access denied″?

Check whether the target is already in session with anothercontroller. If this is the case, wait till the target is availableto start a new session with your controller.

Controlling and MonitoringWhat can I do if something goes wrong when I am working witha controller or target endpoint?

You can look at the following file:<LCF_dir>\DAT\<n>\lcfd.log

where <LCF_dir> is the directory in which the TivoliManagement Agent has been installed and <n> is the integervalue that specifies the endpoint connection number. Thisfile contains a detailed list of informational and error eventsthat occur on the endpoint.

Even if I, as administrator, have the Tivoli Remote Controlresource roles, I cannot control a target endpoint. Why?

132 Version 3.7

The endpoint must be assigned to the policy region whereyou set the Tivoli Remote Control resource roles. To definean endpoint in a policy region, use the wmv command. Forinformation about these commands, see the TivoliFramework Reference Manual.

After you have assigned the endpoint to the policy region,you need to synchronize the Tivoli gateway where thisendpoint has logged on. See “Assigning Targets to a PolicyRegion” on page 53.

I just finished using a controller. Does it matter if I leave itrunning and in session with a target?

You can, but it is not a good idea. Unless you put thecontroller in Suspend state, or you set a non-default value inthe rc_def_inactivity policy method. (See “Setting Valuesfor the Default Policy” on page 60 for details.) The target isconstantly sending a stream of messages to the controller.

Why are some of the selections on the Tivoli Remote Controldialog grayed out?

The senior administrator has set policy methods such that thechosen values for that parameter cannot be changed.

What should I use as the timeout setting for my endpoints?

It depends on your network configuration, and what productsthe Tivoli Management Agent is supporting. Tivoli RemoteControl operations take a few seconds each, so a 10-secondtimeout on a reliable ethernet connection is suitable.However, if the network connection is unreliable, slow, or ifother products, besides Tivoli Remote Control, use the TivoliManagement Agent, a longer timeout may be required(perhaps 30 seconds). Remember that attempts to connect tothe Tivoli Management Agent will wait for this time periodbefore they fail, so hosts without Tivoli Management Agentsrunning will cause significant delays when the timeout valueis too large.


A.

Freq

uen

tlyA

skedQ

uestio

ns

Are there any conditions in which a target cannot be controlled(other than when the target is turned off)?

You cannot take over control of the target if someone elsealready controls the same machine. If the target is anendpoint, the Tivoli Management Agent (TMA) is not startedor logged in.

How can I close the Tivoli Remote Control gateway?

The Tivoli Remote Control gateway is a background processthat runs on the managed node where you installed theRemote Control Server. This starts when you start a TivoliRemote Control session that needs to use the gateway.

To close the gateway, stop the related process namedpcgateway.

In any case, the gateway is closed when the TivoliFramework is closed.

Could I install a scroll pointer (wheel mouse, for exampleIntelliMouse) on a Windows NT, Windows 2000, Windows 95, orWindows 98 target?

Yes, but during a Tivoli Remote Control active session, onlybasic mouse events can be mapped remotely. So, assumingthat a similar pointer device is on the controller, you will notbe able to use the scroll pointer functions remotely.

What are the start_target and start_controller operations?

For the control and monitor operations, the target process isstarted, then the controller is started such that it can connectto the target to give the remote access. If the target processdoes not start then the controller is not run. The start_targetand start_controller operations are the Tivoli methods usedto start the target and controller processes, respectively.

When I attempt to access the chat and file transfer functions, themessage displayed on ″Operation ’filexfer’ (or chat) is not

134 Version 3.7

implemented on this type of system.″

File Transfer and Chat are available only on Endpoints.

When trying to initiate a remote control session to an Endpoint,I received the error ″unable to locate ......\pctlcf.″

Make sure that the gateway the Endpoint is logged into hasthe Remote Control Server code installed.

How can I change the directory that I want to install RemoteControl 3.7 Endpoint controller and target code to?

You cannot change the directory the Endpoint binaries getinstalled to. They will be installed in:lcf\pcremote\tgt or ctl directories

What should I do when I try to start an active remote controlsession but its state is suspend?

Look for the RC_Chat.lck file in the target endpointdirectory. If you find it, delete it.

TroubleshootingWhat hppens the first time I try to launch a Web page during aRemote Diagnosis session?

If Microsoft Internet Explorer is the default browser, theMicrosoft Internet Connection wizard will start and then seta new default internet connection.

When running Remote Command Execution, what happens ifthe command requires input from an unattended remotelocation?

If no input is made, the Remote Diagnosis console waits″forever″. In this case, you must do the following:

1. End the Remote Disgnosis console application (from theTask Manager in Windows).


A.

Freq

uen

tlyA

skedQ

uestio

ns

2. Terminate the Remote Diagnosis target application(sioux.exe). See “Starting and Ending a RemoteDiagnosis Session” on page 106.

3. Terminate the cmd.exe process associated to the RemoteCommand Execution tool on the target.

Error MessagesWhen I try to display a Tivoli Remote Control dialog, I get thefollowing error:

A failure was detected by the oserv daemon:requested resource not found

Once you have installed the Tivoli Remote Control server onthe Tivoli server, you can create a Tivoli Remote Controlobject on any managed node in the TMR. However, in orderfor the product to work, the object must be on a managednode that also contains the Tivoli Remote Control serversoftware. (The object may have been created on anothermachine in order to expedite the process of resolving IPaddresses.) To resolve this error, install the Tivoli RemoteControl server software on the node that produced the error.Use the odstat command on the Tivoli server and look forthe NOT_FOUND error to determine which node needs theserver software.

When I try to start Tivoli Remote Control, I get a messagestating that the controller is not an endpoint even though itreally is. What’s wrong?

Tivoli Remote Control can only be used from a machine thatis in the TMR as an endpoint. Tivoli Remote Control tooluses the WD_DISPLAY environment variable to determinewhich machine is trying to open the tool, and it looks for thesystem name in the TME Name Registry. However it ispossible to install a machine in a way that the name in thename registry will not match the WD_DISPLAYenvironment variable. To fix this problem you can simplyadd an alias for the machine to the name registry. For

136 Version 3.7

example, if managed node top_dog is installed as Top_dog,you can add an alias with the following commands:wregister -r Endpoint top_dog $MNO

where $MNO is the object ID of the endpoint.

The wregister command adds the lower-case alias for theendpoint to the name registry.

Why, when I try to run a Remote Diagnosis action, do I get thefollowing error:

Unable to monitor remote host.->Unable to resolve method "nd_start_se_diagnosis"starting from object <objectID>

You are probably using interconnected TMRs, and theselected target Endpoint is using a Tivoli Remote Controlversion older than the one running on the controller machine.


A.

Freq

uen

tlyA

skedQ

uestio

ns

138 Version 3.7

Files Changed on Installation

Tivoli Remote Control changes the configuration files of Windows95, Windows 98, and OS/2 machines and the registry of WindowsNT, Windows 2000, Windows 95, and Windows 98 machines. Thetables in this appendix describe these changes.

Windows Controller RegistryHKEY_LOCAL_MACHINE\SOFTWARE\Tivoli

Section Installed Uninstalled

Remote ControlController

Build:REG_DWORD:build_number (1)

Logging:REG_DWORD:0

RCPath:REG_SZ:product_dir (1)

Trace Length:REG_DWORD:0

Version:REG_SZ:3.7 (1)

Windows 95 and Windows 98 Controller File

WIN.INI


TME10RemoteControl (1) ControllerPath=product_dir

Version=3.7

Build=build_number

B


B.

Files

Ch

ang

edo

nIn

stallation

(1) Not present if the controller is an endpoint.

OS/2 Controller File

CONFIG.SYS


PATH product_dir;$PATH $PATH

DPATH product_dir;$DPATH $DPATH

LIBPATH product_dir;$LIBPATH $LIBPATH

CALL product_dir\eqnkctld.exe

Windows 95 and Windows 98 Target Files

SYSTEM.INI


386Enh device=vdcfd95.386

WIN.INI


TME10RemoteControl (1) TargetPath=product_dir

Version=3.7

Build=build_number

(1) Not present if the target is an endpoint.

Windows 95 and Windows 98 Target RegistryHKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\




140 Version 3.7

Windows NT and Windows 2000 Target RegistryHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\


KeyEx2 ErrorControl:REG_DWORD:0x1

Group:REG_SZ:Keyboard Class

Start:REG_DWORD:0x2

Type:REG_DWORD:0x1

DisplayName:REG_SZ:Tivoli RemoteControl Keyboard Filter

MouEx2 ErrorControl:REG_DWORD:0

Group:REG_SZ:Pointer Class

Start:REG_DWORD:0x2

Type:REG_DWORD:0x1

DisplayName:REG_SZ:Tivoli RemoteControl Pointer Filter

TGrab ErrorControl:REG_DWORD:0

Start:REG_DWORD:0x1

Type:REG_DWORD:0x1

BusNumber:REG_DWORD:0

DisplayName:REG_SZ:″Tivoli RemoteControl Text Grabber″

InterfaceType:REG_DWORD:0x5

HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\



Build:REG_DWORD:build_number (1)

RCPath:REG_SZ:product_dir (1)


Version:REG_SZ:3.7 (1)

Logging:REG_DWORD:0

(1) Not present if the target is an endpoint.


B.

Files

Ch

ang

edo

nIn

stallation

OS/2 Target Files

CONFIG.SYS


PATH product_dir;$PATH $PATH

DPATH product_dir;$DPATH $DPATH

LIBPATH product_dir;$LIBPATH $LIBPATH

DEVICE product_dir\eqnvkbd.sys

DEVICE product_dir\eqnrcshd.exe

CALL product_dir\eqnrcld.exe

SYSTEM.INI


boot os2shield=product_dir\eqnseada.exe os2shield=winsheld

OS2.INI

Application name Key name Installed Uninstalled

PM_ED_HOOKS MODULENAME EQNPMGRE

SYS_DLLS Load EQNCLHOT

142 Version 3.7

Command Line Interface

You can use Tivoli commands from a managed node. This is oftenuseful when you do not have access to a graphical display; forexample, if you are logging in over a modem line.

All Tivoli end-user commands begin with a ‘w’ (for example, wrcand wrcmdpcr).

Note: If you are using a Windows NT platform as a managed node,you can run bash shell to execute Tivoli commands.

Command Line SyntaxThe manual pages in this appendix use the following specialcharacters to define the command syntax:

[ ] Identify an optional argument. Arguments that are notenclosed in brackets are required.

... Indicates that you can specify multiple values for theprevious argument.

| Indicates mutually exclusive information. You can use theargument to the left of the separator or the argument to theright of the separator. You cannot use both arguments in asingle use of the command.

{ } Delimit a set of mutually exclusive arguments when one ofthe arguments is required. If the arguments are optional, theyare enclosed in brackets ([ ]).

C


C.

Co

mm

and

Lin

eIn

terface

wcreatercCreates a new instance of the RemoteControl managed resource.

SYNOPSISwcreaterc RemoteControl_label ManagedNode_labelPolicyRegion_label

DESCRIPTIONThe wcreaterc command enables you to create a new instance ofRemoteControl managed resource and insert it in a PolicyRegion.

This command can be run only on a managed node where the TivoliRemote Control server component is installed.

Authorizationsenior on TMR.

ArgumentsRemoteControl_label

Specifies the name of the instance of the RemoteControlmanaged resource to be created. If the name includes spaces,enclose it in double quotes (“ ”).

ManagedNode_labelSpecifies the name of the managed node instance where thenew RemoteControl instance resides. If the name includesspaces, enclose it in double quotes (“ ”).

PolicyRegion_labelSpecifies the name of the PolicyRegion instance where thenew RemoteControl instance is to be inserted. If the nameincludes spaces, enclose it in double quotes (“ ”).

EXAMPLESThe example below creates a new RemoteControl instance calledrc-enigma2-1, hosted by enigma2 managed node and inserts it inthe PolicyRegion south-region.wcreaterc rc-enigma2-1 enigma2 south-region

144 Version 3.7

wrcActivates one of the Tivoli Remote Control actions.

SYNOPSISwrc RemoteControlName Action RCtarget [RCcontroller] [options]

DESCRIPTIONThe wrc command allows you to activate one of the following TivoliRemote Control actions:

¶ Remote Control

¶ File Transfer

¶ Chat

¶ Reboot

¶ Remote Diagnosis

¶ Tivoli Enterprise Console (TEC) Integration

This command can be run only from a managed node where theTivoli Remote Control server component is installed.

Authorizationsenior on the RemoteControl instance.

On the target, you need to have the appropriate role, as specified onpage “Assigning Roles” on page 52.

ArgumentsRemoteControlName

Specifies the name of a RemoteControl managed resourceinstance under which you are going to operate. If the nameincludes spaces, enclose it in double quotes (“ ”).

Action Specifies the requested feature:

¶ rc for Remote Control

¶ filexfer for File Transfer

¶ chat for Chat


C.

Co

mm

and

Lin

eIn

terface

¶ reboot for Reboot

¶ rd for Remote Diagnosis

¶ trd2tec for Remote Diagnosis output to TEC

RC targetSpecifies the label of the target. This label has the followingsyntax:@(ManagedNode|PcManagedNode|Endpoint):name

or@NetwareManagedSiteClient:client_name@NetwareManagedSite_name

where:

¶ <endpoint_label> is the label of an endpoint

¶ <client_label> is the label of a NetWareManagedSiteclient

¶ <NetWareManagedSite_label> is the label of aNetWareManagedSite

If the name includes spaces, enclose it in double quotes (“”).

RC controllerSpecifies the label of the controller. This label has thefollowing syntax:

@(Endpoint:<endpoint_label>)

where <endpoint_label> is the label of an endpoint

If the name includes spaces, enclose it in double quotes (“”). This parameter is missing if the action is reboot ortrd2tec.

OptionsA combination of any of the options listed in the followingtable:

146 Version 3.7

Option Setting Default Policymethod

Actions

-B:(Y|N) Desktopoptimization

rc_def_backgrnd rc

-C:(0|4|8) Reduce Number ofColors to: 0 Nolimits 4-Reduce to16 8-Reduce to 256

rc_def_color rc

-D:<WTSID> ID of theWorkstationTerminal Serversession in which thecontroller is started.

All

E:<ESN>#<TMRName> Tivoli Event Serverlocation: <ESN> isthe Event ServerName <TMR> isTMR Server Name

trd2tec

-G:(0|5|10|15|30|60) Grace period rc_def_grace_time All

-P:(Y|N) Proceed if timeout rc_def_timeout_op All

-R:(100) Refresh rate rc_def_rate rc

-T:(Y|N) Enable change stateon target

rc_def_alt_t rc

U:(<pack_name>)[\<scriptname>[?<parm1>[&<parm2>...]]]

Diagnosis Pack tolaunch

trd2tec

-Z:(Y|N) Enable compression rc_def_comp rc, filexfer

-I:(0...) Inactivity timeout rc_def_inactivity rc

-S:(A|M) Startup state rc_def_initstate rc

If an option is missing or out of range, the value returned bythe corresponding default policy method will be used. If thepolicy method returns a locked value, the CLI value (ifpresent) will be ignored.

Note:


C.

Co

mm

and

Lin

eIn

terface

1. Old actions monitor, controla, controlm providedby previous versions of Tivoli Remote Control aresupported with the following meaning: monitor =rc with startup state monitor (wrc rc ... -S:M)controlm = rc with startup state monitor (wrc rc... -S:M) controla = rc with startup state active(wrc rc ... -S:A)

2. Old Limit to 16 colors option (-C:(Y|N))provided by previous versions of Tivoli RemoteControl is interpreted in the following way:

¶ -C:Y = -C:4

¶ -C:N = -C:0

EXAMPLESThe examples listed in this section use the rc-sunnew3-1RemoteControl instance, the enigma2-7003 endpoint target and apendpoint controller.

1. The command shown below activates a Remote Control sessionbetween enigma2-7003 endpoint target and ap endpointcontroller.wrc rc-sunnew3-1 rc @Endpoint:enigma2-7003@Endpoint:ap -B:Y -Z:Y -C:8 -G:15 -P:Y -T:Y

The requested options were:

¶ Desktop optimization (-B:Y)

¶ Enable compression (-Z:Y)

¶ Reduce target colors to 256 (-C:8)

¶ Grace period = 15 seconds (-G:15)

¶ Proceed if timeout = YES (-P:Y)

¶ Enable change state on target (-T:Y)

2. The command shown below activates a File Transfer sessionbetween enigma2-7003 endpoint target and ap endpointcontroller.

148 Version 3.7

wrc rc-sunnew3-1 filexfer @Endpoint: enigma2-7003@Endpoint:ap -Z:Y -G:15 -P:Y


¶ Enable compression (-Z:Y)


¶ Proceed if timeout = YES (-P:Y)

3. The command shown below activates a Chat session betweenenigma2-7003 endpoint target and ap endpoint controller.wrc rc-sunnew3-1 chat @Endpoint:enigma2-7003 @Endpoint:ap -G:15 -P:N



¶ Proceed if timeout = NO (-P:N)

4. The command shown below reboots the enigma2-7003 endpointtarget.wrc rc-sunnew3-1 reboot @Endpoint:enigma2-7003 -G:15 -P:N




5. The command shown below activates a Remote Diagnosissession between enigma2-7003 endpoint target and ap endpointcontroller.wrc rc-sunnew3-1 rd @Endpoint:enigma2-7003 @Endpoint:ap -G:15 -P:N




6. The command shown below reroutes remote diagnosis events ofenigma2-7003 endpoint target to TEC.wrc rc-sunnew3-1 trd2tec @Endpoint:enigma2-7003


C.

Co

mm

and

Lin

eIn

terface

wrcinstepInstalls Tivoli Remote Control software on one or more endpoints.

SYNOPSISwrcinstep {-c|-t} action_values {-l endpoint_label|-ffully_qualified_file_name} [-b]

DESCRIPTIONThe wrcinstep command installs Tivoli Remote Control software onone or more endpoints. This command can be run only from amanaged node where the Tivoli Remote Control server component isinstalled.

Authorization¶ install_product or super on the Tivoli Management Region to

install Tivoli Remote Control on one or more endpoints.

¶ remote_reboot on the Tivoli Management Region to reboot oneor more endpoints.

Arguments-c Installs Remote Control software for controller workstations.

-t Installs Remote Control software for target workstations.

action_valuesSpecifies the type of software to be installed. Valid valuesare any sequences, without spaces, of one or more of thefollowing tokens:

¶ r (Remote Control)

¶ f (File Transfer)

¶ c (Chat)

¶ d (Remote Diagnosis)

¶ k (Remote Diagnosis Packs - only for the target)

¶ t (Remote Diagnosis Tools - only for the target)

¶ p (Remote Diagnosis Plugins - only for the controller)

150 Version 3.7

¶ b (Reboot) (This token is ignored if you are installingthe software on controller workstations).

¶ l(After translated version of Remote Control is installedon server, downloads this version on endpoints.)

-l endpoint_labelSpecifies the name of the endpoint.

-f fully_qualified_file_nameSpecifies a fully qualified name of a file containing asequence of endpoint labels, one for each line, on which toinstall the software.

-b Reboots the target if needed. This option is not supported ifthe endpoint is OS/2.

EXAMPLESThe example below installs the File Transfer, Remote Diagnosis, andChat controller components on the ap endpoint. It also installs theRemote Diagnosis Packs and Remote Diagnosis Tools targetcomponents on the ap endpoint.wrcinstep -c fcd -t kt -l ap


C.

Co

mm

and

Lin

eIn

terface

wrcmdpcrRuns a command-prompt command on a Tivoli Remote Controltarget.

Notes:

1. The wrcmdpcr command does not work with any command thatrequires user input (dir /p, for example).

2. If you run wrcmdpcr on a Unix or Windows NT bash shell, use\\ instead of \ every time you specify a path.

SYNOPSISwrcmdpcr RemoteControlName RCtarget command [argument ...]

DESCRIPTIONThe wrcmdpcr command is a debugging tool that helps you resolveproblems on a Tivoli Remote Control target. This command can berun only from a command line prompt on a managed node where theTivoli Remote Control server component is installed.

Authorizationremote_probe or super on the endpoint target.

ArgumentsRemoteControlName

Specifies the name of a RemoteControl managed resourceinstance. If the name includes spaces, enclose it in doublequotes (“ ”).

RC targetSpecifies the name of an endpoint. This machine must be aTivoli Remote Control target. If the name includes spaces,enclose it in double quotes (“ ”).

commandSpecifies a command that runs on a command prompt.

argumentProvides arguments to the command. You can specify up to4 arguments.

152 Version 3.7

EXAMPLESThe examples listed in this section use the RC RemoteControlmanaged resource instance and the rbuyse end point.

1. The following command displays the environment variables onthe end point:wrcmdpcr RC rbuyse set

Information similar to the following is displayed for a WindowsNT PC end point:COMPUTERNAME=GCATASTAComSpec=D:\WINNT35\system32\cmd.exeOS=Windows_NTOs2LibPath=D:\WINNT35\system32\os2\dll;Path=D:\WINNT35\system32;D:\WINNT35;N:\gk\bin;

d:\msdev\bin;N:\CVSPROCESSOR_ARCHITECTURE=x86PROCESSOR_IDENTIFIER=x86 Family 5 Model 2 Stepping 5,

GenuineIntelPROCESSOR_LEVEL=5PROCESSOR_REVISION=0205PROMPT=$P$GSystemRoot=D:\WINNT35SystemDrive=D:windir=D:\WINNT35

2. The following command lists the contents of the windowsdirectory:wrcmdpcr RC rbuyse dir \windows

The \windows argument is valid only if you execute thecommand from a DOS prompt. If you issue the command from aUNIX machine, you must change the argument to \\windows.


C.

Co

mm

and

Lin

eIn

terface

154 Version 3.7

Troubleshooting and ImprovingPerformance

Setting TracesYou can set traces for controllers and targets running on bothWindows or OS/2. There are separate trace files for each action. Forthe Remote Control action, each session is saved in a numbered file,and all sessions remain available until deleted. For the other actions,only the last session for each action is available.

Contents of the Trace FileEach entry in the trace files contains the following data:¶ Date¶ Time¶ Communication buffer. This can contain either:

v The data sent or received by a send or receive operation. Thenumber of dumped bytes depends on the value set in theTrace Length variable. -or-

v A string showing whether the operation that executed wasconnect or close.

Setting Traces on the Remote Control ServerTo turn traces on or off, or to change the level of tracing, you mustedit the following statement:NO 6

in the following file:

D


D.

Trou

blesh

oo

ting

and

Imp

rovin

gP

erform

ance

¶ On Windows NT: \temp\rctrace\trace.cfg

¶ On Unix: /tmp/rctrace/trace.cfg

The first value can be: NO to set the traces off, and YES to set thetraces ON. The second value must be 6.

Note: The trace.cfg file is created the first time you click the TivoliRemote Control icon.

The trace file is created in the following directories:

¶ On Windows NT: \temp\rctrace

¶ On Unix: /tmp/rctrace

Its name is mmddhhss.TRC where: mm is month dd is day hh ishour ss is minutes

Setting Traces on WindowsIn Windows, to turn traces on or off, or to change the level oftracing, you edit a registry key using the registry editor regedit orregedt32.

Windows ControllerFor the controller, edit the Trace Length value of the registry key:HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\Remote Control Controller

The Trace Length value shows how many bytes are to be traced foreach communication buffer. The recommended value is 40. Thedefault value, 0, means no trace.

The trace files are created in the directory:

<LCF_dir>\PCREMOTE\<interp>\CTL

where:


<interp> can have one of the following values:

156 Version 3.7

¶ w32-ix86 for Windows NT or Windows 2000

¶ w95 for Windows 95 or Windows 98

The names of the trace files are:

Chat CHCTLTRC.TXT

File Transfer FTCTLTRC.TXT

Remote Control

TRACE\mmddhhss.TRCwhere:mm is monthdd is dayhh is hourss is minutes

Windows TargetFor the target, edit the Trace Length value of the registry key:HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\Remote Control Target

The Trace Length value shows how many bytes are to be traced foreach communication buffer. The recommended value is 40. Thedefault value, 0, means no trace.

The trace files are created in the directory:

<LCF_dir>\PCREMOTE\<interp>\TGT

where:





The names of the trace files are:


D.

Trou

blesh

oo

ting

and

Imp

rovin

gP

erform

ance

Chat CHTGTTRC.TXT

File Transfer FTTGTTRC.TXT

Remote Control

TRACE\mmddhhss.TRCwhere:mm is monthdd is dayhh is hourss is minutes

Setting Traces on OS/2To set the trace on an OS/2 controller or target, add the followingstatement to the CONFIG.SYS file:SET RCDEBUG=xxyy

where xxyy can have the following values:

Event Value Comment

Tivoli Remote Control 0100 Enables the events to be logged in a file.

TCP/IP 02yy yy represents the number of bytes for each send orreceive to be dumped in the trace file. You canspecify a maximum value of 99. The recommendedvalue is 40.

IPX (only for the OS/2controller)

04yy yy represents the number of bytes for each send orreceive to be dumped in the trace file. You canspecify a maximum value of 99. The recommendedvalue is 40.

To trace more types of event, define xxxx as the sum of the singlevalues.

For example to enable traces for the TCP/IP protocol and TivoliRemote Control event, add the following to the CONFIG.SYS file:SET RCDEBUG=0340

where 0340 is the sum of:

158 Version 3.7

¶ 0100 (the Tivoli Remote Control event value)

¶ 0200 (the TCP/IP event value)

¶ 40 (the number of bytes to be dumped for TCP/IPcommunication).

Note: After you add the above statement to the CONFIG.SYS file,restart the machine to load the changes into memory.

Trace File NamesTivoli Remote Control creates the following trace files:

¶ In the installation directory:

v EQN02TC.TRC for TCP/IP

v EQN04TC.TRC for IPX for the Remote Control controller

v EQNMGR.LOG for the Remote Control controller

v EQNTG.LOG for the Remote Control target

¶ In the <LCF_dir>\PCREMOTE\os2-ix86\CTL directory (where<LCF_dir> is the directory where the Tivoli Management Agenthas been installed):

v CHCTLTRC.TXT for the Chat controller.

v FTCTLTRC.TXT for the File Transfer controller.

v \TRACE\mmddhhss.TRC for Remote Control where: mm ismonth dd is day hh is hour ss is minutes

¶ In the <LCF_dir>\PCREMOTE\os2-ix86\TGT directory:

v CHTGTTRC.TXT for the Chat target.

v FTTGTTRC.TXT for the File Transfer target.

v \TRACE\mmddhhss.TRC for Remote Control. where: mm ismonth dd is day hh is hour ss is minutes


D.

Trou

blesh

oo

ting

and

Imp

rovin

gP

erform

ance

Logging Application Events on a Windows NT orWindows 2000 Controller

On a Windows NT or Windows 2000 controller, you can log fiveTivoli Remote Control events by setting a registry key value usingthe regedit program. The five events are:

¶ Taking over <ip_address>

¶ Closing session with <ip_address>

¶ Could not establish session with <ip_address>. Error:<error>

¶ Startup error <error>

¶ Closing session with <ip_address>. Error: <error>

To log these events, edit the Logging value of the following registrykey:HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\Remote Control Controller

Valid entries for Logging are:

0 Events are not logged

1 Events are logged

The default is 0.

If the Tivoli Enterprise Console (TEC) Adapter is installed, you canview the logged events from the controller. Each event is precededby the administrator name.

To view the logged events, perform the following steps:

1. Define the TEC host name in the tecad_nt.conf file.

2. Add the following at the bottom of the tecad_nt.baroc file:TEC_CLASS:

NT_RemoteControl_Event ISA NT_BaseDEFINES {

message: STRING;};

END

160 Version 3.7

3. Add the following at the bottom of the tecad_nt.fmt file:FORMAT NT_RemoteControl_Event FOLLOWS NT_Base%t %s %s %s %s %s Remote Control %s %s*message $8END

4. Add the following at the bottom of the tecad_nt.cds file:CLASS NT_RemoteControl_Event

SELECT1: ATTR(=,”_event_id”), VALUE(=,”79”);2: ATTR(=,”hostname”);3: ATTR(=,”origin”);4: ATTR(=,”category”);5: ATTR(=,”eventType”);6: ATTR(=,”sid”);7: ATTR(=,”sub_source”);8: ATTR(=,”id”);9: ATTR(=,”msg”);10: ATTR(=,”date1”);11: ATTR(=,”date2”);12: ATTR(=,”message”);

MAPhostname = $V2;origin = $V3;category = $V4;eventType = $V5;sid = $V6;sub_source = $V7;id = $V8;msg = $V9;date= PRINTF(”%s %s”, $V10, $V11);message = $V12;

END

For additional information on TEC, refer to the manuals for TivoliEnterprise Console.

Logging Session EventsDuring a File Transfer or Chat session, informational events or errorsare always recorded in a log file.


D.

Trou

blesh

oo

ting

and

Imp

rovin

gP

erform

ance

A log file provides a record of informational events or errors thatoccur during the session. When the size of this file reaches 20Kbytes, its contents are moved into the backup log file, which also hasa capacity of 20K bytes.

Further events continue to be recorded in the log file until it againbecomes full, and the backup process is repeated.

On the controller, the log and backup log files are namedRCCTL_xx.log and RCCTL_xx.log.bak respectively, where xx is:

CH For a Chat session

FT For a File Transfer session

These files are created in the directory:

<LCF_dir>\PCREMOTE\<interp>\CTL

where:





On the target, corresponding files are named RCTGT_xx.log andRCTGT_xx.log.bak, where xx is:

CH For a Chat session

FT For a File Transfer session

These files are created in the<LCF_dir>\PCREMOTE\<interp>\TGT directory.

The log files have the following format:

<type> <date_time> <user> <remote_system> <message_code>:<message_string> where the following definitions apply.

162 Version 3.7

type Type of message: I = information messages W = forwarning messages E = error messages.

date_time The date and time the message was written.

user The administrator’s name.

remote_system The name of the target.

message_code The message code.

message_stringThe message string.

Note: To see DBCS localized characters correctly, the followingfiles must be opened using a UTF-8 viewer: RCCTL_CH.log,RCTGT_CH.log, RCCTL_FT.log, and RCTGT_FT.log.

Improving PerformanceThe transmission delay between target and controller depends onhow the target and controller are connected, and the operatingsystem of the target.

If the target and controller are on the same LAN or on differentLANs that are connected by a T1 line, there is a shorter delay.

If the target and controller are on different LANs that are connectedby a 57.6 Kbps (or slower) line, there is a longer delay.

You can consistently reduce the delay by reducing the volume ofdata that is transmitted.

¶ With Windows targets, disable the desktop background andscreen saver of the target when the session starts. The desktopbackground and screen saver are restored when the session ends.With OS/2 targets, you can disable the desktop background, butnot the screen saver.

¶ With windows targets, limit the number of colors displayed onthe controller to 16 or 256. With OS/2 targets, transmission isalways in 16 colors.


D.

Trou

blesh

oo

ting

and

Imp

rovin

gP

erform

ance

¶ Enable compression of transmitted data.

¶ Set the refresh rate to a lower rate (higher number). The sloweryour connection, the lower refresh rate you should set. Start at300 milliseconds, and decrease the refresh rate until you get anacceptable response.

You can customize these characteristics by setting values for thedefault policy methods. See “Changing the Values of Activity andDisplay Settings” on page 55. Depending on the settings for thepolicy methods, you may be able to change the values for aparticular session. See “Methods Used in The Edit Settings Dialog”on page 59.

OS/2 Tivoli Gateway LimitationsYou may have keystroke problems when a controller or a target isinstalled on an endpoint that is also an OS/2 gateway. In this case,set the following field in the config.sys file:TRUSTEDPATH=NO

Note that a reboot is required and that this workaround disables thelogon to the Tivoli gateway.

164 Version 3.7

Tivoli Remote Control Messages

This section describes the Tivoli Remote Control messages.

Windows 95 and Windows 98 Target Messages

EQN0158E An IPX/SPX t_open error error occurred.

Explanation: Check whether the IPX/SPX communication protocol has beencorrectly installed on your workstation and retry the operation.

System Action: Processing continues but the Remote Control session could not bestarted because of an IPX/SPX error.

Operator Response: Check whether the IPX/SPX communication protocol hasbeen correctly installed on your workstation and retry the operation.

System Programmer Response: See the NOVELL NetWare Requester for OS/2Reference for an explanation of how to install IPX/SPX protocol.

EQN0159E An IPX/SPX t_bind error error occurred.

Explanation: An IPX/SPX Bind failed with the return code displayed in themessage box.


Operator Response: The possible values of the return codes are the following: - 3- Transport provider (IPX or SPX) could not allocate an address. -4 - Transport EndPoint was not defined by a t_open. - 5 - Transport provider (IPX or SPX) could notallocate an address. - 8 - A System error occurred. See the NOVELL SystemMessages Reference. - 11 - An internal processing error occurred. Contact yourSystem Programmer.

E


E.

Tivoli

Rem

ote

Co

ntro

lM

essages

System Programmer Response: See the NOVELL NetWare Requester for OS/2Reference for an explanation of how to install IPX/SPX protocol.

EQN0161E An IPX/SPX t_listen error error occurred.

Explanation: An IPX/SPX Listen failed with the return code displayed in themessage box.


Operator Response: The possible values of the return codes are the following: - 4- Transport End Point was not defined by a t_open. - 8 - A System error occurred.See the NOVELL System Messages Reference. - 11 - An internal processing erroroccurred. Contact your System Programmer. - 13 - The Listen operation did notreceive a response from the remote workstation. Contact your System Programmer. -18 - Transport provider (IPX or SPX) does not support the Connect function.

System Programmer Response: Follow your normal problem determinationprocedures.

EQN0162E An IPX/SPX t_accept error error occurred.

Explanation: An IPX/SPX Accept failed with the return code displayed in themessage box.


Operator Response: The possible values of the return codes are the following: - 1- An internal processing error occurred. Contact your System Programmer. - 2 - Aninternal processing error occurred. Contact your System Programmer. - 3 - Transportprovider (IPX or SPX) could not allocate an address. - 4 - Transport End Point wasnot defined by a t_open. - 7 - An internal processing error occurred. Contact yourSystem Programmer. - 8 - A System error occurred. See the NOVELL SystemMessages Reference. - 10 - An internal processing error occurred. Contact yourSystem Programmer. - 11 - An internal processing error occurred. Contact yourSystem Programmer. - 18 - Transport provider (IPX or SPX) does not support theConnect function.


EQN0163E An IPX/SPX t_rcv error error occurred.

Explanation: An IPX/SPX Receive failed with the return code displayed in themessage box.

166 Version 3.7


Operator Response: The possible values of the return codes are the following: - 4- Transport End Point was not defined by a t_open. - 8 - A System error occurred.See the NOVELL System Messages Reference. - 9 - A Disconnect event wasreceived. Connection with the remote workstation is terminated. - 13 - The Receiveoperation did not receive a response from the remote workstation. Contact yourSystem Programmer. - 18 - Transport provider (IPX or SPX) does not support theConnect function.


EQN0164E An IPX/SPX t_snd error error occurred.

Explanation: An IPX/SPX Send failed with the return code displayed in themessage box.


Operator Response: The possible values of the return codes are the following: - 4- Transport End Point was not defined by a t_open. - 8 - A System error occurred.See the NOVELL System Messages Reference. - 6 - t_snd was issued in the wrongsequence. Check the remote workstation state and retry. - 10 - An internalprocessing error occurred. Contact your System Programmer. - 16 - An internalprocessing error occurred. Contact your System Programmer. - 18 - Transportprovider (IPX or SPX) does not support the Connect function.


EQN0179E The Device Driver INET.SYS is not loaded. The TCP/IP communicationprotocol cannot be started.

Explanation: The TCP/IP communication protocol cannot be started because theDevice Driver INET.SYS is not loaded.

System Action: Processing terminates.

Operator Response: Check whether your TCP/IP protocol stack is correctlyinstalled.

System Programmer Response: None.


E.

Tivoli

Rem

ote

Co

ntro

lM

essages

EQN0185E A TCP/IP error occurred. Return Code return code.

Explanation: The Remote Control operation cannot be completed because of aTCP/IP error.


Operator Response: See “TCP/IP Codes” on page 234 for an explanation of thereturn code value.


EQN0186E An unknown TCP/IP error occurred.

Explanation: The Remote Control session cannot be completed because anunknown TCP/IP error occurred.


Operator Response: Check whether the TCP/IP communication protocol iscorrectly installed and configured. Try to ping the workstation that has the TCP/IPproblem.


EQN0187E The TCP/IP Network is down.

Explanation: The Remote Control operation failed because the TCP/IP Network isdown.


Operator Response: Check your TCP/IP network. Try to ping the workstation thathas the TCP/IP problem.


EQN0188E The requested Network is unreachable.

Explanation: The Remote Control operation failed because the requested Networkis unreachable.


Operator Response: Check the routing of your TCP/IP network.


168 Version 3.7

EQN0439E Not enough system resources (memory, timers) available to complete therequest. Close some applications and retry.

Explanation: Remote Control cannot start the session because of a lack of systemresources.

System Action: The session does not start.

Operator Response: Check the system resources availability and try to releasesome of them. If the problem persists, try to reboot the workstation.


EQN0507W Do you really want to terminate the session?

Explanation: You tried to exit the client interface while the communication lineswere still open. Your confirmation will close all communications.

System Action: If you confirm, processing ends normally and control returns toyour operating system. If you cancel, the client and communications keep running.

Operator Response: Click Yes to close all communications and exit the client.Click No to cancel and to keep the client and communications running.


EQN0528W The Tivoli Remote Control session has been terminated.

Explanation: The session was terminated successfully at your request.

System Action: The session ends and control returns to the operating system.

Operator Response: None.


EQN0676E Unexpected error on target workstation. The Tivoli Remote Control session isclosed.

Explanation: Because of an unexpected error, the session ends.

System Action: The Remote Control session ends.

Operator Response: Restart the session. If the problem continues, shut down andrestart the target.



E.

Tivoli

Rem

ote

Co

ntro

lM

essages

Windows NT and Windows 2000 Target Messages

Click on OK to accept a Chat session.

Explanation: If you click OK and then Yes in the confirmation panel, you start aChat session.

System Action: The system asks for a confirmation to start a Chat session.

Operator Response: To start a Chat session click OK and then Yes.


Click on OK to accept a File Transfer session.

Explanation: If you click OK and then Yes in the confirmation panel, you start afile transfer session.

System Action: The system asks for a confirmation to start a file transfer session.

Operator Response: To start a file transfer session click OK and then Yes.


Click on OK to accept a Remote Control session.

Explanation: If you click OK and then Yes in the confirmation panel, you start aRemote Control session.

System Action: The system asks for a confirmation to start a Remote Controlsession.

Operator Response: To start a Remote Control session click OK and then Yes.


Click on OK to accept a Remote Diagnosis session.

Explanation: If you click OK and then Yes in the confirmation panel, you start aRemote Diagnosis session.

System Action: The system asks for a confirmation to start a Remote Diagnosissession.

Operator Response: To start a Remote Diagnosis session click OK and then Yes.


170 Version 3.7

Click on OK to allow your system to be rebooted.

Explanation: If you select OK the system is rebooted. A confirmation message isdisplayed before the reboot.

System Action: The system asks for a confirmation to reboot the workstation.

Operator Response: To reboot the workstation click OK and then Yes.


Do you really want to terminate the session?

Explanation: If you click Yes, you terminate the session.

System Action: The system asks for a confirmation to terminate the session.

Operator Response: To terminate the session, click Yes.


OS/2 Target Messages

EQN0001I RC ACTIVE

Explanation: A session is ACTIVE.

System Action: None.



EQN0002I RC PENDING

Explanation: A session is PENDING or in the process of changing states.




EQN0003I RC CONNECTING

Explanation: The controller workstation is connecting to a target workstation. Aconnection is being established.




E.

Tivoli

Rem

ote

Co

ntro

lM

essages


EQN0004I RC SUSPENDED

Explanation: The Remote Control session is in suspend state.




EQN0006I RC MONITORING

Explanation: The target user pressed the <Alt><T> key sequence during an activeRemote Control session and changed the session state to MONITORING.




EQN0008I RC INITIATING

Explanation: The controller and target workstations have made a connection andare trying to establish a session.




EQN0009I RC TERMINATING

Explanation: The controller and target workstations are terminating a session.




EQN0010I RC BUSY

Explanation: The target user pressed the <Alt><T> key sequence and the state ofthe session is BUSY.

System Action: Processing continues.

172 Version 3.7

Operator Response: Wait for the target user to change the state of the session, orterminate the session with the target workstation.


EQN0154W No help available;name.hlp was not found or unable to complete the requestbecause of a lack of system resources.

Explanation: The.hlp file for this function was not found in the directory whereRemote Control is installed.


Operator Response: You can continue without help, or contact the systemprogrammer to restore the help file.

System Programmer Response: If the specified help file is not in the directorywhere Remote Control is installed, copy it from the Remote Control CD-ROMimage. Otherwise release some system resources and retry. If you cannot resolve theproblem, contact Tivoli Support.

EQN0155E There are not sufficient system resources (semaphores, threads, or queues)available to complete the request.

Explanation: Remote Control cannot complete the request because of a lack ofsystem resources.


Operator Response: Contact the system programmer.

System Programmer Response: Release some system resources and retry. If theproblem persists, try to reboot the workstation. If you cannot resolve the problem,contact Tivoli Support.

EQN0156E Internal processing error. Component=component. Call=call. Code=code.

Explanation: Unexpected error encountered in the specified component.

System Action: System action depends on the error encountered.


System Programmer Response: Follow your normal problem determinationprocedures. If you cannot resolve the problem, contact Tivoli Support.


E.

Tivoli

Rem

ote

Co

ntro

lM

essages

EQN0181E TCP/IP cannot assign the requested IP address.

Explanation: The local requested IP address is already in use.


Operator Response: Change the Local Port number value in the rc_def_ports andretry the operation.


EQN0185E A TCP/IP error occurred. Return Code code.



Operator Response: See “TCP/IP Codes” on page 234TCP/IP for an explanationof the return code value.





Operator Response: Check if the TCP/IP communication protocol is correctlyinstalled and configured.



Explanation: You pressed the Terminate push button.

System Action: If you choose Yes, the session ends and control returns to theoperating system. If you choose No, the Change State window reappears to chooseanother state.

Operator Response: Click Yes to continue ending the session. Click No to cancel.


174 Version 3.7

EQN0501I The device driver for the RC has been loaded.

Explanation: The Remote Control device driver was loaded successfully.




EQN0502E The device driver could not be loaded.

Explanation: The device driver could not be loaded.


Operator Response: Contact your system programmer.

System Programmer Response: Reinstall Tivoli Remote Control on the target. Ifyou cannot resolve the problem, contact Tivoli Support.

EQN0504I All of the required RC files were started.

Explanation: The Remote Control files were loaded and started successfully.




EQN0505E One or more of the required RC files was not started. The client function wasnot started.

Explanation: Either the CONFIG.SYS file was not updated correctly whenRemote Control was installed, or one or more of the following files could not befound when you started the target:

¶ EQNRCKB.EXE

¶ EQNRCLD.EXE

¶ EQNRCSHD.EXE

¶ EQNRCUT.DLL

¶ EQNRCVI.DLL

¶ EQNKRAS.DLL

¶ EQNUT.DLL



E.

Tivoli

Rem

ote

Co

ntro

lM

essages


System Programmer Response: Perform the following steps:

¶ Ensure that the following statements appear before any other DEVICE or CALLstatements in the CONFIG.SYS file (drive\dir represents the path where RemoteControl is installed):

DEVICE=drive\dir\EQNRCSHD.EXECALL=drive\dir\EQNRCLD.EXEDEVICE=drive\dir\EQNVKBD.SYS

NOTE: When you are using the High Performance File System (HPFS), theInstallable File System (IFS) statement must appear before the DEVICE andCALL statements.

¶ Verify that all the files listed in the explanation are in the path where RemoteControl is installed.

¶ If you changed the CONFIG.SYS file, shut down and then restart theworkstation.

¶ If one or more Remote Control files is missing, deinstall and reinstall TivoliRemote Control.

If you cannot resolve the problem, contact Tivoli Support.

General Controller Messages

A communication error with host host occurred.

Explanation: Remote Control cannot communicate with the specified host.

System Action: The action fails and control returns to the Remote Control tool.

Operator Response: Check whether:

¶ You can see the machine properties in the TMR from the Tivoli Desktop.

¶ The displayed properties are correct.

¶ You can ping the target machine from the controller.


ACCESS DENIED: Please try later someone else is updating the list.

Explanation: Someone else is already updating the target list in the Define TargetList window.

System Action: Control returns to the Remote Control tool.

176 Version 3.7

Operator Response: Retry later.


A protocol error occurred.

Explanation: A connection to the target could not be established.

System Action: The action terminates.

Operator Response: Contact the system administrator.


Attempt to action host host failed due to lack of required roles.

Explanation: This error message is logged in the Tivoli Remote Control Noticewhen you do not have the needed roles to perform the specified operation on thespecified host.

System Action: The operation does not start and control returns to the RemoteControl tool.

Operator Response: Check whether you have the Tivoli Remote Control roles forthe specified operation.

System Programmer Response: Assign the correct role to the operator.

Attempt to operation failed due to lack of required roles.

Explanation: This error message is logged in the Tivoli Remote Control Noticewhen you do not have the needed roles to perform one of the following operations:

¶ List the current NetWare clients.

¶ Change the rc_def_targets policy method.


Operator Response: Check whether you have the Tivoli Remote Control roles forthe specified operation.

System Programmer Response: assign the proper role to the operator.

Attempt to open input file file name failed: error.

Explanation: Remote Control is trying to spawn a method on the PC managednode target. An error occurred while the method was opening the temporary file thatis used to send the input values to the target machine.


E.

Tivoli

Rem

ote

Co

ntro

lM

essages

System Action: The operation fails and control returns to the Remote Control tool.

Operator Response: Check whether, as tmersrvd user, you are authorized to openthe file on the TMR server.


Attempt to write number bytes to input file file name failed: error

Explanation: Remote Control is trying to spawn a method on the PC managednode target. An error occurred while the method was writing in the temporary filethat is used to send the input values to the target machine.


Operator Response: Check whether, as tmersrvd user, you are authorized to writethe file on the TMR server.


Attempting to access the output file file name failed: error

Explanation: Remote Control ran a method on the PC managed node target. Anerror occurred while Remote Control was accessing the specified file that is used tosend the input values on the target machine.


Operator Response: Check whether, as tmersrvd user, you are authorized toaccess the file on the TMR server.


Attempting to allocate number bytes of memory in %7$s failed.

Explanation: Remote Control ran a method on the PC managed node target and itfailed in the memory allocation.


Operator Response: Check whether there is enough memory on the target.


Attempting to read the results file file name failed: error.

Explanation: Remote Control ran a method on a PC managed node target and itfailed. The specified file might be empty or corrupted.


178 Version 3.7

Operator Response: Check whether the file is empty or corrupted.


Attempting to send input file file name to the remote host failed.

Explanation: Remote Control ran a method on the PC managed node target and itfailed. An error occurred while Remote Control was sending the specified file to thetarget machine.


Operator Response: Check whether, as tmersrvd user, you have the full controlpermissions in the $DBDIR directory of the TMR server.


Cannot find controller system controller system name.

Explanation: The controller name you specified in the wrc command line is notrecognized as a valid Tivoli resource.

System Action: The action fails and control returns to the operating system.


¶ The controller label you specified is correct.

¶ The corresponding controller workstation is defined in your TMR.


Cannot find target system target system name.

Explanation: The target name you specified in the wrc command line is notrecognized as a valid Tivoli resource.



¶ The target label you specified is correct.

¶ The corresponding target workstation is defined in your TMR.


Controller and Target systems should be different.

Explanation: You specified the same workstation name for the controller and thetarget.


E.

Tivoli

Rem

ote

Co

ntro

lM

essages

System Action: Control returns to the operating system.

Operator Response: Specify different workstation names for the controller and thetarget.


Could not find the input file file.

Explanation: wrcinstep cannot read the file you specified with the -f: option.


Operator Response: Check whether the specified file exists.


Creating temp file names using method name failed: error.

Explanation: Remote Control is trying to spawn a method on the PC managednode target. An error occurs while Remote Control is creating a temporary file tosend the input values to the target machine.



¶ You are authorized to create a file as tmersrvd user on the TMR server.

¶ The TMR server has enough space.


Default policy method for attribute method name failed with output: error code

Explanation: Remote Control is waiting for an input value from the specifiedpolicy method.

System Action: The process stops. The Remote Control tool does not start.

Operator Response: Check whether you have unsupported characters in theprofile.


Error accessing results file file name.

Explanation: You tried to run the wrcmdpcr command but the output has not beencreated on the target machine.


180 Version 3.7



Error: Bad parameter parameter.

Explanation: You ran the wrcinstep command with an incorrect parameter.


Operator Response: Run wrcinstep without any parameter to display the syntax ofthe command.


Error: Could not find the input file file name.

Explanation: The wrcinstep command fails because it cannot read the specifiedfile.


Operator Response: Check whether the file exists.


Error trying to get results file file name from remote host

Explanation: Remote Control tried to run the wrcmdpcr command. It is waitingfor the output.




Error trying to open results file file name.

Explanation: You ran the wrcmdpcr command. An error occurred when thewrcmdpcr command opened the specified file.





E.

Tivoli

Rem

ote

Co

ntro

lM

essages

Error: wrong arguments number

Explanation: You ran the wcreaterc command with an incorrect number ofarguments.


Operator Response: Check the wcreaterc syntax by running wcreaterc withoutany parameter.

System Programmer Response:

Failed while attempting to perform operation operation on host host.

Explanation: You receive this notice message in the Tivoli Remote Control Noticeif the execution of the wrcmdpcr command on the specified host fails.




FATAL ERROR: Cannot get IP address for host host. Check resolver configuration onManagedNode node.

Explanation: Remote Control must know the IP address of the target system torun any method.


Operator Response: Check whether the managed node can resolve the hostaddress.


INTERNAL ERROR: Failed to initialize the COMM code for PLCF.

Explanation: Remote Control is trying to initialize the communication with acontroller or a target.

System Action: The action failed and control returns to the Remote Control tool.


¶ You can see the PC managed node properties in the TMR from the TivoliDesktop.

¶ The displayed properties are correct.

¶ You can ping the target machine from the TMR server.

182 Version 3.7


INTERNAL ERROR: Unable to properly parse the IP address, Path and Program from IPaddress, Path, Program.

Explanation: Remote Control is trying to initialize the communication with a PCmanaged node target. An error occurred during the parsing of the input parameters.

System Action: The action failed and control returns to the Remote Control tool.

Operator Response: Check whether the specified target IP address, path, andprogram are correct.


Invalid action action.

Explanation: The action you specified in the wrc command is invalid.

System Action: Control is returned to the operating system.

Operator Response: Change the action value to one of the following values:¶ rc¶ filexfer¶ chat¶ reboot¶ rd


Invalid option option.

Explanation: The option you entered in the wrc command line is either notrecognized as an option or its argument is invalid.


Operator Response: Check the option and its value. Run wrc without argumentsto display the help.


Invalid value for the Inactivity Timeout setting. The value must be a positive integer without sign.A value of ’0’ disables the Inactivity Timeout.

Explanation: You have inserted an invalid value in the Inactivity Timeout field ofthe Edit Settings dialog box. The inactivity timeout value determines how manyminutes a user can hold a session in active state before the session times out. Thevalue 0 means no timeout.


E.

Tivoli

Rem

ote

Co

ntro

lM

essages

System Action: The system waits for a new value.

Operator Response: Insert a value equal to or greater than zero. This setting isthe maximum amount of time in minutes that a target in active session can wait forany input from the controller before it closes the session automatically. A valueequal to zero means no limit.


Invalid value for the Refresh Rate setting. The value must be a positive integer without signgreater than 100.

Explanation: You have inserted an invalid value in the Refresh Rate field of theEdit Settings dialog box.

System Action: The system waits for a new value.

Operator Response: Insert an integer equal to or greater than 100.


Method method name (from binary file name) failed to execute on the remote host.

Explanation: Remote Control is trying to spawn a method on the PC managednode target through the REMEXEC function.



¶ The PC Agent is running.


¶ The displayed PC managed node properties are correct.


¶ The specified binary is on the target machine.


object is not an instance of RemoteControl.

Explanation: Remote Control cannot locate an instance of the RemoteControlmanaged resource labeled object.


Operator Response: Verify the correctness of the label you provided.


184 Version 3.7

Operation operation failed on the controller host.

Explanation: Remote Control ran a method on the controller system and it failed.




Operation operation failed on the target host.

Explanation: Remote Control ran a method on the target system and it failed.




Operation operation failed to start on node node label.

Explanation: This message is logged in the Tivoli Remote Control Notice whenthe specified operation does not start. The operation can be one of the following:control, monitor, filexfer, chat, reboot, remote diagnosis.




Operation operation is not implemented on this type of system.

Explanation: You tried to run the specified operation on either an unsupportedoperating system or an unsupported resource type. For example, File Transfer andChat are supported on endpoints only.

System Action: The specified operation fails and control returns to the RemoteControl tool.

Operator Response: Check on which operating system and for which Tivoliresource type the operation can run.


Operation operation was rejected by the user on node node.

Explanation: You receive this warning message in the Tivoli Remote ControlNotice if the remote user of the specified node rejects the specified operation.


E.

Tivoli

Rem

ote

Co

ntro

lM

essages

System Action: The specified operation fails.



Reboot online not supported for the os2-ix86 interpreter... skipping...

Explanation: You ran the wrcinstep command with the -b option, which rebootsthe workstation if needed. This operation is not supported for the OS/2 interpreter.

System Action: The wrcinstep command is started on the next endpoint in the list.When the program reaches the end of the list, control returns to the operatingsystem.

Operator Response: Reboot the workstation manually.


Reboot successfully initiated

Explanation: The reboot of the current endpoint is initiated successfully.

System Action: The reboot operation is started on the next endpoint in the list.When the program reaches the end of the list, control returns to the operatingsystem.



Rebooted host host successfully.

Explanation: The reboot of the specified workstation is initiated successfully. Thismessage is logged in the Tivoli Remote Control Notice.

System Action: The remote workstation reboots and control returns to the RemoteControl tool.



Remote Control controller display must be on a ManagedNode or a PcManagedNode or anEndpoint running Windows NT or Windows 95 or OS/2. The host specified by display host willnot work.

Explanation: You tried to open the Remote Control tool from either anunsupported Remote Controller controller platform (for example Unix) or a machinethat is not defined as a Tivoli resource.

186 Version 3.7

System Action: The Remote Control tool does not start.

Operator Response: Check whether the controller machine runs on one of thespecified Tivoli resources and on a supported platform.


Successfully performed operation operation on host host.

Explanation: You receive this message in the Tivoli Remote Control Notice afterthe execution of the wrcmdpcr command on the specified host.




Syntax error: error. Choose a valid managed resource type string. The possible values are@ManagedNode, @PcManagedNode, @Endpoint and @NetwareManagedSiteClient (only forRCtarget).

Explanation: You specified an incorrect RCtarget or RCcontroller parameter in thewrc command line.


Operator Response: Check the wrc syntax.The correct format of the RCtarget parameter is:

@(ManagedNode|PcManagedNode|Endpoint|NetwareManagedSiteClient):node_label

The correct format of the RCcontroller parameter is:

@(ManagedNode|PcManagedNode|Endpoint):node_label

The words ManagedNode, PcManagedNode, Endpoint, and NetwareManagedClientare case sensitive.


The controller host host is not a ManagedNode or a PcManagedNode or an Endpoint. The TivoliDesktop must be running on a ManagedNode or PcManagedNode or Endpoint for the RemoteControl controller to work.

Explanation: Tivoli Remote Control can be used only from a machine that is inthe TMR (as a managed node, a PC managed node, or an endpoint). Tivoli RemoteControl tool uses the WD_DISPLAY environment variable to determine whichmachine is trying to open the tool, and it looks for the system name in the TME


E.

Tivoli

Rem

ote

Co

ntro

lM

essages

Name Registry. However, you can install a machine in a way that the name in thename registry will not match the WD_DISPLAY environment variable.


Operator Response: Check whether the controller is a Tivoli managed resource ofthe TMR. If so, it is possible that you installed the machine in a way that the namein the name registry will not match the WD_DISPLAY environment variable. To fixthis problem, add an alias for the machine to the name registry. For example, ifmanaged node top_dog is installed as Top_dog, you can add an alias with thefollowing commands:

wregister -r ManagedNode top_dog $MNO

where $MNO is the object ID of the managed node. The wregister command addsthe lower-case alias for the managed node to the name registry.

System Programmer Response: Add the machine to the TMR.

The controller software has not been installed on node.

Explanation: Remote Control tried to run a method on the specified machine andit failed. The method is not installed.


Operator Response: Check the following to see whether you have installed theRemote Control controller correctly:

¶ On Windows operating systems:

v The Remote Control Controller entry appears in theHKEY_LOCAL_MACHINE\SOFTWARE\TIVOLI registry.

v The directory in which you installed the controller contains theEQNRSMAI.EXE file.

v The Tivoli Remote Control Service is started in the Start->Settings->ControlPanel->Services window. (Only for Windows NT)

¶ On OS/2 operating systems:

v The PATH, DPATH and LIBPATH of the config.sys file have been updatedwith the directory in which you have installed the controller.


For additional information on all the changes the controller installation determinesto the configuration files and registries, see “Files Changed on Installation” on page139.


188 Version 3.7

The default policy method rc_def_uncheckedlist returns some invalid entries. They were skipped.

Explanation: You have inserted an invalid value in the resource list that isspecified in the rc_def_uncheckedlist policy method.

System Action: Only the valid entries will be displayed in the Targets field.

Operator Response: Correct the rc_def_uncheckedlist policy method. Checkwhether the syntax you used has one of the following formats:

@(ManagedNode|PcManagedNode|Endpoint):name

or

@NetWareManagedSiteName:NetWareClientName@NetWareManagedSiteName

The key words ManagedNode, PcManagedNode, Endpoint, andNetWareManagedSiteName are case sensitive.


The interpreter information is not available... skipping...

Explanation: Remote Control cannot find the interp property for the currentendpoint.

System Action: Remote Control is not installed on the current endpoint. Thewrcinstep command installs the Remote Control software on the next endpoint inthe list. When the program reaches the end of the list, control returns to theoperating system.

Operator Response: Run the command:

wep <endpoint_label>

and check the interp value. An endpoint is valid if the interp value is one of thefollowing: w32-ix86, win95, win3x, or os2-ix86.


The RC start_gateway method failed: node is not a ManagedNode.

Explanation: Remote Control tries to start the Remote Control gatewaycomponent on a resource that is not a managed node.

System Action: The Remote Control gateway does not start. Control returns to theoperating system.

Operator Response: Specify a managed node in the rc_def_gw policy method.



E.

Tivoli

Rem

ote

Co

ntro

lM

essages

The RC start_gateway method failed on the node ManagedNode please verify if the ManagedNodeis available.

Explanation: Remote control tried to run the start_gateway method on thespecified managed node (that is also defined in the rc_def_gw policy method) and itfailed.



¶ The Tivoli Object Dispatcher (oserv) is running.

¶ You can see the managed node properties in the TMR from the Tivoli Desktop.

¶ The displayed managed node properties are correct.

You can also use the odstat command to investigate the problem.


The RC start_gateway method failed: the IP incoming port must be a known value.

Explanation: You have specified an invalid value for the gateway port in therc_def_gw policy method. The gateway port is the value following the managednode label. A correct value is an integer value greater than zero.


Operator Response: Edit the rc_def_gw policy method with a valid gateway port.


The RC start_gateway method failed: the specified IP port is busy, Remote Control is not able tocomplete the requested operation. Please change the specified IP port or try again later.

Explanation: Remote control tries to start the gateway on the managed node at theIP port specified in the rc_def_gw policy method. The IP port is already being usedby another program. Remote Control is not able to complete the operation.


Operator Response: Change the specified IP port or try again later.


190 Version 3.7

The reboot command on host host failed.

Explanation: This message is logged in the Tivoli Remote Control Notice if thereboot of the specified host fails.




The reboot command on host host timed out waiting for user confirmation.

Explanation: You receive this message in the Tivoli Remote Control Notice if theremote user on the specified host neither confirms nor rejects the operation.

System Action: Control returns to the Remote Control tool.

Operator Response: To force the reboot, set one of the following:

¶ The ″Proceed if timeout″ option from the Setting Panel of the Remote ControlTool.

¶ The -P option of the wrc command to Y.


The RemoteControl binaries on the host host are corrupted.

Explanation: The Remote Control binaries have an incorrect format.


Operator Response: Check whether you have installed Remote Control correctlyon the specified host. (For example if you are installing a tar file, do not unpack itwith WinZip).


The requested ACTION is not allowed by the policy default object settings.

Explanation: You specified an action different from the ones listed in therc_def_command policy method.


Operator Response: Add the action to the rc_def_command policy method byusing the wgetpolm and wputpolm commands.



E.

Tivoli

Rem

ote

Co

ntro

lM

essages

The required binaries are not installed on host host.

Explanation: Remote Control is not able to find the controller and target binarieson the specified PC managed node or managed node.


Operator Response: Check the following to see whether you have installed theRemote Control controller correctly:

¶ On Windows operating systems:

v The Remote Control Controller entry appears in theHKEY_LOCAL_MACHINE\SOFTWARE\TIVOLI registry (not for Windows3.11).


v The Tivoli Remote Control Service is started in the Start->Settings->ControlPanel->Services window (only for Windows NT and Windows 2000).


v The PATH, DPATH and LIBPATH of the config.sys file have been updatedwith the directory in which you have installed the controller.


Check the following to see whether you have installed the Remote Control targetcorrectly:

¶ On Windows operating systems

v The Remote Control Target entry appears in theHKEY_LOCAL_MACHINE\SOFTWARE\TIVOLI registry (not for Windows3.11).

v The directory in which you installed the target contains theEQNRCMAI.EXE file.

v The Tivoli Remote Control Service is started in the Start->Settings->ControlPanel->Services window (only for Windows NT and Windows 2000).

v The device=VDCFD95.386 entry has been added in the [386Enh] section ofthe %WINDIR%\SYSTEM.INI file (only for Windows 95 or Windows 98).

v The device=VDCFD.386 entry has been added in the [386Enh] section of the%WINDIR%\SYSTEM.INI file (only for Windows 3.x).


192 Version 3.7

v The PATH, DPATH, and LIBPATH in the CONFIG.SYS file have beenupdated with the directory in which you have installed the target.


v The OS2.INI file has been updated with the following entries:Application name:PM_ED_HOOKSKey name: MODULENAMEText: EQNPMGREApplication name: SYS_DLLSKey name: LoadText: EQNCLHOT

v The EQNPMGRE.DLL file is locked. To check it, try to renameEQNPMGRE.DLL. If you can rename it, the target has not been installedcorrectly.

For additional information on all the changes the controller or target installationdetermines to the configuration files and registries, see .


The target host host is already in session. Please, try later.

Explanation: The target you chose is already in session with another controller.

System Action: The operation fails and control returns to the operating system.

Operator Response: Try to start the session later.


The target software has not been installed on node.

Explanation: Remote Control tried to run a method on the target machine and itfailed. The method is not installed.


Operator Response: Check the following to see whether you have installed theRemote Control target correctly:

¶ On Windows operating systems

v The Remote Control Target entry appears in theHKEY_LOCAL_MACHINE\SOFTWARE\TIVOLI registry (not for Windows3.11).



E.

Tivoli

Rem

ote

Co

ntro

lM

essages

v The Tivoli Remote Control Service is started in the Start->Settings->ControlPanel->Services window (only for Windows NT).

v The device=VDCFD95.386 entry has been added in the [386Enh] section ofthe %WINDIR%\SYSTEM.INI file (only for Windows 95 or Windows 98).

v The device=VDCFD.386 entry has been added in the [386Enh] section of the%WINDIR%\SYSTEM.INI file (only for Windows 3.x).


v The PATH, DPATH, and LIBPATH in the CONFIG.SYS file have beenupdated with the directory in which you have installed the target.


v The OS2.INI file has been updated with the following entries:Application name:PM_ED_HOOKSKey name: MODULENAMEText: EQNPMGREApplication name: SYS_DLLSKey name: LoadText: EQNCLHOT

v The EQNPMGRE.DLL file is locked. To check it, try to renameEQNPMGRE.DLL. If you can rename it, the target has not been installedcorrectly.

For additional information on all the changes the target installation determines to theconfiguration files and registries, see “Files Changed on Installation” on page 139.


The TCP/IP network services on host host are not running. Operation operation cannot beperformed until the host’s network is functional.

Explanation: Remote Control cannot complete the requested operation because theTCP/IP is not working on the specified host.



¶ The TCP/IP communication protocol is correctly installed and configured.

¶ The TCP/IP connection is established by pinging the specified machine.


194 Version 3.7

The Tivoli Desktop must be running on a ManagedNode or PcManagedNode or Endpoint for theRemote Control controller to work. The controller host host has not been recognized as a validManagedNode, PcManagedNode or Endpoint. Maybe there is a mismatch between the Tivoliresource label and the hostname. Remote Control is going to execute an extended search. This cantake several minutes...Would you like to proceed?

Explanation: You started Tivoli Remote Control from a Tivoli resource (managednode, PC managed node, or endpoint) with a label that is not equal to the machinehost name.

System Action: If you click Yes, Remote Control performs an extended search toidentify a machine similar to the host name. If the search is successful, an entrycontaining the host name, the Tivoli label, and the resource type is automaticallycreated in the controller table. If you click No, the Remote Control tool does notstart.

Operator Response: Click Yes to perform an extended search for a machine witha label similar to the host name.If the search is successful, an entry is added to the controller table.To manually create an entry in the controller table, use the following command:

createcontroller host_name controller_label controller_type

where:host_name is the controller host name.controller_label is the controller label.controller_type is MN for a managed node, PCMN for a PC managed node, or EPfor an endpoint.


The TME Agent on host host is not running. Operation operation cannot be performed until thehost’s TME Agent is functional. Some systems only run TME Agents when a user is logged in.

Explanation: Remote Control cannot complete the requested operation because thePC Agent is not running.








E.

Tivoli

Rem

ote

Co

ntro

lM

essages

The user of host host rejected the operation.

Explanation: The target user did not accept the session within the specified graceperiod.

System Action: The session does not start. Control returns to the Remote Controltool.

Operator Response: To force the reboot, set one of the following:

¶ The ″Proceed if timeout″ option from the Setting Panel of the Remote ControlTool.

¶ The -P option of the wrc command to Y.


The user of node node failed to respond to consent dialog for operation operation.

Explanation: You receive this warning message in the Tivoli Remote ControlNotice if the remote user of the specified host neither confirms nor rejects thespecified operation.

System Action: The remote host does not reboot and control returns to the RemoteControl tool.



The user on host host aborted the reboot operation.

Explanation: The user interrupted the reboot on the specified workstation.

System Action: The workstation does not reboot and control returns to the RemoteControl tool.



The user on target host host did not respond to the confirmation dialog in the allotted time so theoperation was cancelled.

Explanation: This message is logged in the Tivoli Remote Control Notice if theremote user on the specified host rejects the operation within the specified graceperiod time.

System Action: The remote host does not reboot and control returns to the RemoteControl tool.

196 Version 3.7



The variable variable is not in the environment of this method. It is not possible to determinewhich system is to be used as the controller without this variable.

Explanation: Remote Control cannot determine the host name of the controllerworkstation.


Operator Response: Check whether the host name is defined in the DomainName System (DNS).


The WIN3X interpreter is not supported for operation name.

Explanation: You tried to install Remote Control Controller, Chat, or File Transferon a Windows 3.x endpoint.

System Action: Remote Control is not installed on the current endpoint. Thewrcinstep command installs the Remote Control software on the next endpoint inthe list. When the program reaches the end of the list, control returns to theoperating system.



Tivoli Remote Control binaries were installed/updated on endpoint endpoint. It needs to berebooted.

Explanation: The new binaries have been installed/updated automatically on thespecified endpoint. A reboot of the machine is necessary to run the new software.


Operator Response: If the endpoint runs on Windows NT, Windows 2000,Windows 95, Windows 98, or Windows 3.x, you can reboot the endpoint from theRemote Control tool or the wrc command line.


Tivoli Remote Control can’t install/update binaries on endpoint endpoint.

Explanation: While Remote Control is installing/updating the new binaries, asetup error occurred.


E.

Tivoli

Rem

ote

Co

ntro

lM

essages

System Action: Remote Control does not start and control is returned to theoperating system.


System Programmer Response: Check the endpoint log file on the specifiedendpoint. The name of the endpoint default log file is lcfd.log and it is located inthe directory stored in the $LCF_DATDIR environment variable. If you cannotresolve the problem, contact Tivoli Support.

Unable to connect to host at address address after 10 seconds. Either the host is not up or theTME Agent is not running.

Explanation: Remote Control tried to contact the target machine and it failed.

System Action: The action fails and control returns to the Remote Control tool







Unable to delete the input/output file file name on the remote system.

Explanation: Remote Control ran a method on the PC managed node target. Themethod is trying to delete the input/output file.


Operator Response: Check whether, as tmersrvd user, you are authorized to deletethe file. If so, try to delete it manually.


Unable to determine the type of host at address address name. This is usually due to the TMEAgent not currently running on the host.

Explanation: Remote Control is trying to contact the target machine.

System Action: The action cannot be executed.



198 Version 3.7





Unable to establish connection with TME Agent at address address name.

Explanation: Remote Control is trying to run the wrcmdpcr command but itcannot establish a connection with the target machine.



¶ The PC Agent is running

¶ The IP address is correct


Unable to find out the object_id... skipping...

Explanation: Remote Control does not find the Tivoli Object ID from theendpoint label that you have specified in the wrcinstep command.

System Action: Remote Control is not installed on the current endpoint. Thewrcinstep command installs the Remote Control software on the next endpoint inthe list. When the endpoint names in the list end and control returns to the operatingsystem.


¶ The endpoint label you specified is correct.

¶ The corresponding endpoint workstation is defined in your TMR


Unable to get output file file name from remote host. This is usually due to an abnormaltermination of the remote method method name which caused the output file not to be created.

Explanation: Remote Control ran a method on the PC managed node target andwaited for an output file from the target machine.


Operator Response: Check on the target whether the method ended abnormally.



E.

Tivoli

Rem

ote

Co

ntro

lM

essages

Unable to get the IP address for object object name.

Explanation: Remote Control tried to contact the specified PC managed node. Theaction failed because Remote Control was unable to resolve the PC managed nodeIP address.







Unable to locate RemoteControl binaries on the controller host host. Perhaps the controllersoftware is not installed on this system. If this system is a ManagedNode (not a PcManagedNode)it also needs the Server software installed.

Explanation: Remote Control cannot find the Remote Control controller binaries.



¶ You have installed the controller correctly.

¶ You have installed the Remote Control server correctly (if the system is amanaged node).


Unable to locate RemoteControl binaries on the target host host. Perhaps the target software isnot installed on this system.

Explanation: Remote Control cannot find the Remote Control target binaries.


Operator Response: Check whether you have installed the target correctly.


Unable to monitor remote host.

Explanation: Remote Control tried to run a method on the target and it failed.


200 Version 3.7

Operator Response: Check whether the target has been installed correctly.


Unable to reboot host host.

Explanation: Remote Control ran the reboot method on the target and it failed.


Operator Response: Try to reboot the machine by selecting Shutdown from theStart menu during an active session.


Unable to run command command name on remote host

Explanation: Remote Control tried to run the wrcmdpcr command.



¶ The input values you specified in the wrcmdpcr command line are correct.

¶ You have the required authorizations to run the command.


Unable to start program program name on target system.

Explanation: Remote Control tried to run the specified program on a PC managednode.

System Action: The session cannot be established.

Operator Response: Check whether the program has been installed successfullyon the failing machine.


Unable to start program program name on target system using WinExec() (error error value)

Explanation: Remote Control tried to reboot the target machine by running thespecified program on a PC managed node.

System Action: The reboot operation is not completed.

Operator Response: Try to reboot the target machine by selecting Shutdown fromthe Start menu during an active session.



E.

Tivoli

Rem

ote

Co

ntro

lM

essages

Unsupported interpreter... skipping...

Explanation: The message appears in one of the following situations:

¶ The endpoint label you specified on the wrcinstep command line has aninterpreter different from the supported ones: Windows NT (w32-ix86),Windows 2000 (w32-ix86), Windows 95 and Windows 98 (win95), OS/2(os2-ix86), Windows 3.x (win3x).

¶ You are trying to install a Remote Control component on an unsupportedoperating system.

System Action: The wrcinstep command installs the Remote Control software onthe next endpoint in the list. When the program reaches the end of the list, controlreturns to the operating system.

Operator Response: Depending on the action you are performing check whether:

¶ The endpoint label you have specified in the wrcinstep command line has oneof the following interpreter: Windows NT (w32-ix86), Windows 2000(w32-ix86), Windows 95 and Windows 98 (win95), OS/2 (os2-ix86), Windows3.x (win3x

¶ The component you are installing is supported on the current operating system.


Wrong inactivity timeout value. The default value will be used.

Explanation: The inactivity timeout option determines how many minutes a usercan hold a session in active state before the session times out. The value 0 meansno timeout. The message appears in the Tivoli Remote Control Notice if you insertan invalid inactivity timeout value in the rc_def_inactivity policy method.

System Action: The inactivity timeout setting is set to the default value: disableinactivity timeout.

Operator Response: To enable the inactivity timeout option, edit therc_def_inactivity policy method. Insert a value equal to or greater than zero.


You do not have the proper Roles on the endpoint to perform this operation.

Explanation: To execute any Remote Control operation you must have the correctTivoli and Remote Control roles.


202 Version 3.7

Operator Response: Check whether you have the required Tivoli and RemoteControl roles for the specified operation.

System Programmer Response: Set the correct roles for the operator.

You must provide a valid label for the new tool.

Explanation: You did not specify any label for the new tool.

System Action: The system is waiting for a label.

Operator Response: Define the label of the new tool.


You must select a Target

Explanation: To start a Remote Control action, select a target in the Targets list ofthe Remote Control main dialog.


Operator Response: Select a target in the Targets List.


Windows Controller Messages

A Chat session is running on the target machine.

Explanation: A Chat session is already active on the target machine. The Chatcontroller cannot set up the connection with the target machine.

System Action: The Chat application is terminated.

Operator Response: Retry later or try to establish a Chat session with a differentworkstation.


Do you really want to terminate the session?

Explanation: If you click Yes, you terminate the session.

System Action: The system asks for a confirmation to terminate the session.

Operator Response: To terminate the session, click Yes.



E.

Tivoli

Rem

ote

Co

ntro

lM

essages

If you don’t press the Cancel button within number of seconds the RC session with target will beterminated.

Explanation: The Inactivity Timeout has been set. Click Cancel within thespecified Inactivity Timeout to maintain the session.

System Action: If you press Cancel within the specified Inactivity Timeout, thesession continues. Otherwise control returns to the Remote Control tool.

Operator Response: Click Cancel within the specified Inactivity Timeout tomaintain the session.


Remote Control could not establish a session with the target machine. The target is not started orcould already be in session.

Explanation: Remote Control could not establish a session with the targetmachine. The Remote Control target could be not started or it is already in session.


Operator Response: Retry later or try to establish a session with a different targetworkstation.


Remote Control is closing the session.

Explanation: The session ends.

System Action: Processing terminates and control returns to the operating system.



The Controller cannot contact the Gateway/Target workstation with the user assigned port. Nowit will retry with a system assigned port.

Explanation: The port specified for the gateway in rc_def_gw should be busy.

System Action: The system will try to start the connection using a system port.



204 Version 3.7

The Remote Control Gateway cannot contact the Target workstation. Please check that the Targetmachine is running properly.

Explanation: The Remote Control Gateway tried to contact the target workstationand it failed.


Operator Response: Check whether the target machine is running correctly.


The session has been rejected due to file system access restrictions on the target workstation.

Explanation: Even if the security file has been defined in the rc_def_tfc policymethod, the session has been rejected for one of the following reasons:

¶ Trusted File Commander is not installed on the target.

¶ The security file you have specified in the rc_def_tfc policy method does notexist on the target.

¶ You did not specify the full path of the security file in the rc_def_tfc policymethod.



¶ The path of the security file in the rc_def_tfc policy method is correct.

¶ The security file exists.

¶ Trusted File Commander is installed on the target.


The target user terminated the Remote Control session.

Explanation: The target user terminated the session successfully.




You have reached the maximum number of available connections on Remote Control Gateway.Please retry later.

Explanation: You have tried to start a connection on Remote Control Gateway,but the maximum number of connections has been reached.


E.

Tivoli

Rem

ote

Co

ntro

lM

essages

System Action: The application is terminated.

Operator Response: Close some sessions and try again or change the maximumnumber of sessions in rc_def_gw.


OS/2 Controller Messages

EQN0001I RC ACTIVE

Explanation: A session is ACTIVE.




EQN0002I RC PENDING

Explanation: A session is PENDING or in the process of changing states.




EQN0003I RC CONNECTING

Explanation: The controller workstation is connecting to a target workstation. Aconnection is being established.




EQN0004I RC SUSPENDED

Explanation: The Remote Control session is in suspend state.




206 Version 3.7

EQN0006I RC MONITORING

Explanation: The target user pressed the <Alt><T> key sequence during an activeRemote Control session and changed the session state to MONITORING.




EQN0008I RC INITIATING

Explanation: The controller and target workstations have made a connection andare trying to establish a session.




EQN0009I RC TERMINATING

Explanation: The controller and target workstations are terminating a session.




EQN0010I RC BUSY

Explanation: The target user pressed the <Alt><T> key sequence and the state ofthe session is BUSY.


Operator Response: Wait for the target user to change the state of the session, orterminate the session with the target workstation.


EQN0154W No help available; name.hlp was not found or unable to complete the requestbecause of a lack of system resources.

Explanation: The.hlp file for this function was not found in the directory whereRemote Control is installed.



E.

Tivoli

Rem

ote

Co

ntro

lM

essages

Operator Response: You can continue without help, or contact the systemprogrammer to restore the help file.

System Programmer Response: If the specified help file is not in the directorywhere Remote Control is installed, copy it from the Remote Control CD-ROMimage. Otherwise release some system resources and retry. If you cannot resolve theproblem, contact Tivoli Support.

EQN0155E There are not sufficient system resources (semaphores, threads, or queues)available to complete the request.

Explanation: Unable to complete the request because of a lack of systemresources.



System Programmer Response: Release some system resources and retry. If youcannot resolve the problem, contact Tivoli Support.

EQN0156E Internal processing error. Component=component. Call=call. Code=code.

Explanation: Unexpected error encountered in the specified component.

System Action: System action depends on the error encountered.



EQN0181E TCP/IP cannot assign the requested IP address.

Explanation: The local requested IP address is already in use.


Operator Response: Change the Local Port number value in the rc_def_ports andretry the operation.


EQN0185E A TCP/IP error occurred. Return Code code.



208 Version 3.7

Operator Response: See “TCP/IP Codes” on page 234 for an explanation of thereturn code value.





Operator Response: Check if the TCP/IP communication protocol is correctlyinstalled and configured.



Explanation: You pressed the Terminate push button.

System Action: If you choose Yes, the session ends and control returns to theoperating system. If you choose No, the Change State window reappears to chooseanother state.

Operator Response: Click Yes to continue ending the session. Click No to cancel.


EQN0504I All of the required RC files were started.

Explanation: The Remote Control files were loaded and started successfully.




EQN0512E General communications failure. The RC has terminated.

Explanation: The communication link failed because of an undetermined error.

System Action: The session terminates.

Operator Response: Restart the Remote Control session. If the communicationscontinue to fail, contact the system programmer.

System Programmer Response: Verify that the network address parameters arecorrect. If you cannot resolve the problem, contact Tivoli Support.


E.

Tivoli

Rem

ote

Co

ntro

lM

essages

EQN0527E Client ended the RC session.

Explanation: The target has ended the Remote Control session.


Operator Response: You can start a new session with the same or other availabletargets.


EQN0529E The session has been rejected due to file system access restrictions on the targetworkstation

Explanation: The session has been rejected because of file system accessrestrictions on the target workstation

System Action: Control returns to your operating system.



EQN0537E Error occurred when starting the RC.

Explanation: An error occurred when the controller or target was started.

System Action: Processing terminates and control returns to the operating system.

Operator Response: Retry. If the error persists, contact the system programmer.

System Programmer Response: Verify that:

¶ The network address parameters are correct.

¶ Sufficient resources (such as threads, semaphores, queues, and memory) areavailable for Remote Control.

If you cannot resolve the problem, contact Tivoli Support.

EQN0551W There are no printers available.

Explanation: Either no printer is attached to the workstation or the printer iscurrently unavailable.

System Action: Processing continues, but the print function cannot be completed.

Operator Response: Click OK.


210 Version 3.7

EQN0552I The printer driver version has changed.

Explanation: The printer driver version has changed. The job properties willdefault to those of the printer object.




EQN0553I The printer device name has changed.

Explanation: The printer device name has changed. The job properties will defaultto those of the printer object.




EQN0554I No pages were printed. Select different pages to print.

Explanation: No pages were printed. Select different pages to print.




EQN0555E Unexpected error occurred at the client. The RC session will end.

Explanation: Because of an unexpected error, the session ends.

System Action: The Remote Control session ends.

Operator Response: Restart the session. If the problem continues, shut down andrestart the target.


EQN0655E Remote Control could not establish a session with the target machine. Thetarget is not started or could already be in session.

Explanation: Remote Control could not establish a session with the targetmachine. The Remote Control target could be not started or it is already in session.



E.

Tivoli

Rem

ote

Co

ntro

lM

essages

Operator Response: Retry later or try to establish a session with a different targetworkstation.


File Transfer Messages

A file transfer operation is running; if you close the application the operation will be interrupted.Do you really want to exit file transfer?

Explanation: You are closing a file transfer session while a transfer operation isrunning.

System Action: If you click OK, the file transfer session terminates and thetransfer operation is interrupted. If you click Cancel, the file transfer operationcontinues.

Operator Response: To interrupt the file transfer click OK.


A protocol error occurred. The File Transfer window will be closed.

Explanation: A protocol exception occurred.

System Action: The File Transfer application will be terminated.


¶ The TCP/IP is running.

¶ The file transfer target is running.

System Programmer Response: If you cannot resolve the problem, send theRCCTL_FT.log and the RCTGT_FT.log files to Tivoli Support.

Abend in Protocol occurred.

Explanation: A protocol abend occurred.




212 Version 3.7

Access is denied.

Explanation: You are expanding a directory or transferring a file that cannot beread.

System Action: The directory will not be expanded or the file will not be copied.

Operator Response: Check whether the Trusted File Commander is enabled.


An error occurred building FT message output buffer.

Explanation: A problem occurred while the file transfer controller read the answermessage coming from the target.

System Action: The file transfer session continues.

Operator Response: Close the file transfer session to restore the Remote Controlenvironment.


An error occurred creating directory directory name

Explanation: The directory specified cannot be created.


Operator Response: Run a refresh to check whether the directory already exists.


An error occurred deleting directory directory name

Explanation: The directory specified cannot be deleted.


Operator Response: Run a refresh to check whether the directory still exists.


An error occurred getting the file.

Explanation: The File Transfer application cannot transfer a file from the remotesystem. The file might not exist or might not have read permission.



E.

Tivoli

Rem

ote

Co

ntro

lM

essages

Operator Response: Run a refresh to check whether the file still exists.


An error occurred in directory_list. Return code is return code.

Explanation: An error occurred while Tivoli Remote Control was listing thedirectories.




An error occurred in file_list. Return code is return code.

Explanation: An error occurred while Tivoli Remote Control was listing the files.




An error occurred in opening file.

Explanation: The File Transfer application cannot transfer the file because eitherthe file does not exist or you do not have read permission.




An error occurred in removing directory.

Explanation: The directory specified cannot be deleted.


Operator Response: Run a refresh to check whether the directory exists.


214 Version 3.7

An error occurred putting the file.

Explanation: The File Transfer application cannot transfer a file to remote system.


Operator Response: Check the permission on the destination path.


An error occurred reading file.

Explanation: The File Transfer application cannot transfer a file because either thefile does not exist or you do not have read permission.




An error occurred while transacting FT message.

Explanation: A protocol problem occurred while the File Transfer application wastrying to send a message to the target and read its answer.

System Action: The file transfer session ends and control returns to the operatingsystem.

Operator Response: Check whether the TCP/IP is running. If the file transfersession is still open, close it.


An error occurred writing file. Return code is return code.

Explanation: The File Transfer application cannot transfer a file because theapplication does not have write permission.


Operator Response: Check the permission on the destination path. If the filetransfer session is still open, close it.



E.

Tivoli

Rem

ote

Co

ntro

lM

essages

An unexpected error occurred.

Explanation: A generic error occurred when you performed a file transferoperation.

System Action: The requested operation will be not executed.

Operator Response: Check the RCCTL_FT.log and the RCTGT_FT.log files.


Are you sure you want to delete directory/file name?

Explanation: You have been asked to confirm or deny the deletion of the selecteditem.

System Action: If you click Yes, the specified item is deleted. If you click Cancel,the specified item is not deleted. The file transfer session continues.

Operator Response: To delete the specified item click Yes.


Are you sure you want to delete these items items?

Explanation: You have been asked to confirm or deny the deletion of the selecteditems.

System Action: If you click Yes, the specified items are deleted. If you clickCancel, the specified items are not deleted. The file transfer session continues.

Operator Response: To delete the specified items click Yes.


DataFormat exception occurred.

Explanation: An error occurred while the file transfer target was executingrequests coming from the controller.


Operator Response: Close the file transfer session.


216 Version 3.7

Deleting directory directory name.

Explanation: Remote Control is deleting the specified directory or file.




Directory directory name has been created successfully

Explanation: The specified directory has been created successfully.




Exception in Protocol occurred.

Explanation: A protocol exception occurred.


Operator Response: Check whether the TCP/IP is running and whether the filetransfer controller or target is running.

System Programmer Response: If you cannot resolve the problem, contact TivoliSupport sending it the RCCTL_FT.log and the RCTGT_FT.log.

Executing DIR_LIST command for path name

Explanation: Remote Control is listing the contents of the specified path.




Executing IS_DRIVE_SYSTEM command...

Explanation: Remote Control is checking whether the system is intel based.





E.

Tivoli

Rem

ote

Co

ntro

lM

essages

Executing FILE_LIST command for path name

Explanation: Remote Control is listing the contents of the specified path.




Executing GET_ATTRIBS command for file name

Explanation: Remote Control is getting the attributes of the specified file.




Executing GET_DRIVE command...

Explanation: Remote Control is getting the list of the drives.




Executing MAKE_DIR command for directory name

Explanation: Remote Control is creating the specified directory.




Executing REMOVE_DIR command for directory/file name

Explanation: Remote Control is deleting the specified directories or files.




218 Version 3.7

Executing RECV_FILE command for file name

Explanation: Remote Control is transferring the specified file from the remote filesystem.




Executing SEND_FILE command for file name

Explanation: Remote Control is transferring the specified file to the remote filesystem.




File Transfer could not establish a session with the target machine. The target is not started orcould already be in session.

Explanation: The file transfer controller cannot set up the connection with thetarget machine.

System Action: The File Transfer application is terminated.

Operator Response: Try to ping the target machine and check the rc_def_portspolicy method to see whether the ports specified are already in use.


Getting file file name.

Explanation: Remote Control is transferring a file from the remote file system.




IOException after accept.

Explanation: For some reason, the file transfer target cannot accept the connectionfrom the file transfer controller.


E.

Tivoli

Rem

ote

Co

ntro

lM

essages

System Action: The file transfer session ends.

Operator Response: Check whether TCP/IP is running.


IOException after closing file.

Explanation: An error occurred while the File Transfer application was saving thetransferred file. The transferred file is not saved.

System Action: The file transfer continues.



IOException after connect.

Explanation: The file transfer controller cannot establish the connection with thefile transfer target machine.

System Action: The file transfer session ends.



IOException after hangup.

Explanation: The File Transfer application receives an error while closing theconnection.

System Action: The File Transfer application ends.



IOException from startReading.

Explanation: An error occurred while the file transfer target was setting up theProtocolListener.

System Action: The File Transfer application ends.


220 Version 3.7


IOException from TcpChannel.

Explanation: A protocol error occurred while the file transfer controller wascreating a channel for the connection.

System Action: The file transfer session does not start.


¶ TCP/IP is running.

¶ The TCP/IP port is busy.


IOException from TcpServerChannel.

Explanation: A protocol error occurred while the file transfer target was creating achannel for the connection. For example the TCP/IP port could be busy.



¶ TCP/IP is running.

¶ The TCP/IP port is busy.


IOException occurred in closing window.

Explanation: An error occurred while the File Transfer application was closing.

System Action: The File Transfer application closes.



IOException occurred in reading the message.

Explanation: An error occurred when Remote Control is reading a file transfermessage from the socket.



E.

Tivoli

Rem

ote

Co

ntro

lM

essages

Operator Response: Close the file transfer session. If the error persists, contactyour system programmer.


IOException occurred in writing the message.

Explanation: An error occurred when Remote Control was writing a file transfermessage to be sent. The file transfer message is not sent.


Operator Response: Close the file transfer session. If the error persists, contactyour system programmer.


Loading information about the target file system. Please wait...

Explanation: The system is loading the information about the drives on the remotefile system.




Making directory.

Explanation: Remote Control is creating the specified directory.




NotSerializable exception occurred.

Explanation: An error occurred while the file transfer target was getting the driveslist of the remote file system.




222 Version 3.7

Operation ’filexfer’ is not implemented on this type of system.

Explanation: You tried to start a file transfer session between two workstationsthat are not endpoints or that do not have a supported operating system.


Operator Response: Start the file transfer session between endpoints.


Putting file file name.

Explanation: Remote control is transferring a file to the remote file system


Operator Response: Click Refresh to see the updated status of the file transfer.



Explanation: The port specified for the gateway in rc_def_gw might be busy.

System Action: The system tries to start the connection using a system port. Thefile transfer session is starting.



The directory/file name has been successfully deleted

Explanation: The specified directory or file has been deleted successfully.




The directory directory name already exists.

Explanation: The specified directory cannot be created because it is alreadypresent on the file system.


Operator Response: Change the name, if you need to create a new directory.


E.

Tivoli

Rem

ote

Co

ntro

lM

essages


The file file name has not been found.

Explanation: The file to be transferred or deleted cannot be found. The requiredoperation on the specified file is not executed.




The session has been rejected due to file system access restrictions on the target workstation.

Explanation: Even if the security file has been defined in the rc_def_tfc policymethod the session has been rejected for one of the following reasons:

¶ Trusted File Commander is not installed on the target.

¶ The security file you have specified in the rc_def_tfc policy method does notexist on the target.

¶ You did not specify the full path of the security file in the rc_def_tfc policymethod.

System Action: The file transfer session does not start. Control returns to theoperating system.


¶ The path of the security file in the rc_def_tfc policy method is correct.

¶ The security file exists.

¶ Trusted File Commander is installed on the target.


The user does not have receive permission.

Explanation: You do not have the required Remote Control roles for file transferfrom the remote file system.

System Action: The receive operation will not be executed.

Operator Response: Check whether you have the remote_ft_receive role. The filetransfer session continues.

System Programmer Response: If you cannot resolve the problem, contact TivoliSupport.

224 Version 3.7

The user does not have send permission.

Explanation: The Tivoli user does not have the Remote Control roles for filetransfer to remote file systems.

System Action: The send operation is not executed. The file transfer sessioncontinues.

Operator Response: Check whether you have the remote_ft_send role.


Unable to get FT message buffer.

Explanation: A protocol problem occurred while the File Transfer application wastrying to get message buffer.





Explanation: The maximum number of connections has been reached.

System Action: The File Transfer application is terminated.

Operator Response: Close some sessions and try again or change the maximumnumber of session in rc_def_gw policy method.


Chat Messages

A protocol error occurred. The Chat application will be closed.

Explanation: The TCP/IP connection encountered an error.

System Action: The Chat session is closed.

Operator Response: Check whether TCP/IP is running



E.

Tivoli

Rem

ote

Co

ntro

lM

essages

Choose a directory where to store the log file

Explanation: You must specify the name of a directory in which to create the logfile.

System Action: The chat session continues.

Operator Response: Type the name of the directory where you want to create thelog file.


Client starting.

Explanation: The Chat controller application is starting.




Chat could not establish a session. Gateway answer error.

Explanation: The chat application encountered an error while trying to connect toa gateway.

System Action: The chat session is closed.

Operator Response: Check whether the gateway machine is running.


Chat could not establish a session. Gateway port number is missing.

Explanation: Gateway port number is missing from the chat command line.

System Action: The chat application is terminated.

Operator Response: Check the value of policy method rc_def_gw.


Chat could not establish a session with the target machine. The target is not started or couldalready be in session.

Explanation: The chat controller cannot set up the connection with the targetmachine.

System Action: The chat application is terminated.

Operator Response: Check whether the target machine is running.

226 Version 3.7


Chat server is unable to start.

Explanation: The chat server cannot start.

System Action: The chat target application is terminated.

Operator Response: Check the TCP/IP connection by pinging the target machine.


Chat session closed.

Explanation: The connected user closed the chat session.

System Action: The chat session closes.



New chat message.

Explanation: A new chat message was received while the Chat window waschanging in an icon.




Operation ’chat’ is not implemented on this type of system.

Explanation: You tried to start a chat session between two workstations that arenot endpoints.

System Action: The chat session does not start.

Operator Response: Start the chat session between endpoints.


Server didn’t get info message.

Explanation: The chat target application did not receive the information about thename of the target user.




E.

Tivoli

Rem

ote

Co

ntro

lM

essages


Server starting...

Explanation: The chat target application is starting.





Explanation: The port specified for the gateway in rc_def_gw might be busy.

System Action: The system will try to connect using a system port.



The specified directory doesn’t exist. Create?

Explanation: The specified directory does not exist. You are asked whether thisdirectory is to be created.


Operator Response: click Yes, to create the directory in which to log theconversation.


Unable to create lock file.

Explanation: The Chat application cannot create the lock file.


Operator Response: Check whether there is enough disk space or the writepermission is enabled.


Unable to create log file.

Explanation: The Chat application cannot create the log file.


228 Version 3.7

Operator Response: Check whether there is enough disk space.


Unable to format chat message.

Explanation: The chat application cannot create or send chat messages.


Operator Response: Check whether the TCP/IP connection is established.


Unable to get caller user name.

Explanation: The administrator name is not supplied to the chat command line.The IP address of the administrator is displayed.




Unable to get message type.

Explanation: The Chat application cannot read the Chat message type.




Unable to get target IP address.

Explanation: The IP address parameter is not supplied to the chat controllerapplication.

System Action: The chat controller application is terminated.



Unable to log into file.

Explanation: The Chat application cannot write into the log file



E.

Tivoli

Rem

ote

Co

ntro

lM

essages

Operator Response: Check whether there is enough disk space or whether thewrite permission is enabled.

System Programmer Response: None

Unable to receive messages from Gateway.

Explanation: The chat controller application is enable to receive messages fromGateway.


Operator Response: Check whether the gateway process is running.


Unable to read chat message.

Explanation: The Chat application cannot read or receive chat messages.




Unable to send message to Gateway.

Explanation: The Chat controller application cannot send messages to thegateway.


Operator Response: Check whether the gateway process is running.


Unable to set chat token message.

Explanation: The Chat application cannot write the chat token message. Youmight have lost a message.


Operator Response: Check whether the TCP/IP connection is up.


230 Version 3.7

Unable to set chat token message length.

Explanation: The Chat application cannot write chat token message length.




Unable to set message type.

Explanation: The Chat application cannot write the chat message type.




Unknown message type.

Explanation: The Chat application received an unknown message type.





Explanation: The maximum number of connections has been reached.

System Action: The Chat application is terminated.

Operator Response: Close some sessions and try again or change the maximumnumber of sessions in rc_def_gw.


Remote Diagnosis Messages

An unexpected error occurred: the console will be closed. The Java stack trace will saved inTSETrace.out file under directory directory.

Explanation: An unrecoverable error occurred.

System Action: Tivoli Remote Diagnosis terminates.


E.

Tivoli

Rem

ote

Co

ntro

lM

essages

Operator Response: Check the error file TSETrace.out, and restart Tivoli RemoteDiagnosis.


Are you sure you want to close the connection?

Explanation: You tried to close a session.

System Action: Waits for a response.

Operator Response: Choose Yes to close the session, or No to continue thesession.


Do you want to save the current diagnosis before opening a new one?

Explanation: You tried to load data saved from a previous session. The data fromthe current session will be lost if you do not save it first.

System Action: Wait for your response.

Operator Response: Choose Yes to save the current data, or No to discard thedata.


Mail Error

Explanation: You tied to send a mail, but it failed.


Operator Response: Check the e-mail address in the ’To:’ field, and try again.


Mail Error: please, check the fields ’Host’ and ’From’\n in the Mail Configuratoin Dialog.

Explanation: You tried to send a mail, but it failed.


Operator Response: Check the ’Host’ and ’From’ fields, and try again.


232 Version 3.7

Please, insert an e-mail address.

Explanation: You tried to mail someone without specifying an e-mail address.


Operator Response: Specify an e-mail address in the To: field.


Remote Diagnosis Console could not establish a session with the target machine. The target is notstarted or could already be in session.

Explanation: You tried to start a session, but it failed.


Operator Response: Try again. If you are not successful, check that the target isstarted. Also check that no other controller is in session with the target. If the targetis available but you are still unsuccessful, contact the system administrator.


The file specified already exists. Overwrite?

Explanation: You tried to save data to a filename that already exists. The existingdata will be overwritten by the new data unless you change the filename.

System Action: Wait for your response.

Operator Response: Choose Yes to overwrite the file, or No to specify anotherfile.


The file specified does not exist.

Explanation: You tried to open a file that does not exist.


Operator Response: Specify an existing file.


The file specified does not contain a ServiceEverywhere diagnosis.

Explanation: You tried to open a file containing data from a previous session.


Operator Response: Specify a valid diagnosis file.


E.

Tivoli

Rem

ote

Co

ntro

lM

essages


Wrong browser path. Be sure to select a valid browser path.

Explanation: You tried to launch a web browser that you selected previously butthe path is no longer valid.


Operator Response: Enter a new web browser path.



Explanation: The Remote Control Gateway is busy.


Operator Response: Try again later.


TCP/IP CodesThe TCP/IP codes are listed in the following table in numericalorder.

Codes Explanation

35 Operation requested would block because the socket is innon-blocking mode

36 Operation inquired about in progress

37 Operation requested already in progress

38 Socket operation requested but did not request socket

39 destination address required

40 Message too long

41 TCP/IP implementation does not support requestedprotocol for socket

42 Protocol not available

43 Protocol not supported

44 Socket type not supported

234 Version 3.7

Codes Explanation

45 Operation not supported on socket

46 Protocol family not supported

47 Address family not supported by protocol family

48 Local address already in use

49 Cannot assign requested local address

50 Remote network is down

51 Communication subsystem cannot find route to networkrequested

52 Network dropped connection on reset

53 Software application caused connection abort

54 Connection reset by remote workstation

55 No buffer space available

56 Socket is already connected

57 Socket is not connected

58 Cannot send after socket shutdown

59 Too many references: cannot splice data packets

60 Connection timed out

61 Connection refused

62 Too many levels of symbolic links

63 File name too long

64 Host is down

65 Host does not have router configured

66 Directory not empty


E.

Tivoli

Rem

ote

Co

ntro

lM

essages

236 Version 3.7

Glossary

A

administratorSee Tivoli administrator.

agent(1) In systems management, a user that, for a particular interaction, has assumed anagent role. (2) An entity that represents one or more managed objects by (a)emitting notifications regarding the objects and (b) handling requests from managersfor management operations to modify or query the objects. (3) A system thatassumes an agent role. (4) Software that acts on behalf of a user as it performs taskswithin an application program. An agent may run on both the client and the server.

artifactIn Tivoli Remote Control, a file that can be downloaded from a target to helpdiagnose a problem.

authorization roleIn a Tivoli environment, a role assigned to Tivoli administrators to enable them toperform their assigned systems management tasks. A role may be granted over theentire Tivoli Management Region or over a specific set of resources, such as thosecontained in a policy region. Examples of authorization roles include: super, senior,admin, and user.

C

ChatIn Tivoli Remote Control, a function that enables the Tivoli administrator toexchange written communication with the user of a target.

CIMSee Common Information Model.

clientIn a client/server system, a computer system or process that requests a service ofanother computer system or process that is typically referred to as a server. Multipleclients may share access to a common server.

client daemonAn AIX process that performs the client’s operations.


Glo

ssary

client/serverIn communications, the model of interaction in distributed data processing in whicha program at one site sends a request to a program at another site and awaits aresponse. The requesting program is called a client; the answering program is calleda server.

Common Information Model (CIM)A specification provided by the Distributed Management Task Force (DMTF). CIMis an abstract model of system information aimed at system management.

controllerIn Tivoli Remote Control, the workstation used by the Tivoli administrator toperform Remote Control, File Transfer, Chat, Reboot, and Remote Diagnosisactions.

D

daemonA program that runs unattended to perform a standard service. Some daemons aretriggered automatically to perform their task; others operate periodically.

E

endpointAny computer system running the Tivoli Management Agent (TMA).

endpoint managerIn a Tivoli environment, a service that runs on the Tivoli server, assigns endpointclients to gateways, and maintains the endpoint list.

endpoint methodIn a Tivoli environment, a method that runs on an endpoint client as the result of arequest from other managed resources in the Tivoli Management Region. Results ofthe method are forwarded first to the gateway, then to the calling managed resource.

F

File TransferIn Tivoli Remote Control, a function that enables the Tivoli administrator to transferfiles or directories between controller and a target.

238 Version 3.7

G

gatewayIn a Tivoli environment, software running on a managed node that provides allcommunication services between a group of endpoints and the rest of the Tivolienvironment. This gateway includes the multiplexed distribution (MDist) function,enabling it to act as the fanout point for distributions to many endpoints. See alsoTivoli management gateway, Tivoli Remote Control gateway.

I

install repository (IR)In Tivoli Software Installation Service (SIS), the directory containing reusableinstallation images and other data used by SIS.

Internetwork Packet Exchange (IPX)The network protocol used to connect Novell’s servers, or any workstation or routerthat implements IPX, with other workstations. Although similar to the InternetProtocol (IP), IPX uses different packet formats and terminology.

Internet Protocol (IP)In the internet suite of protocols, a connectionless protocol that routes data througha network or interconnected networks and acts as an intermediary between thehigher protocol layers and the physical network.

IPXSee Internetwork Packet Exchange.

IPX AgentA PC Agent that runs on IPX/SPX. It can only be the client of a NetWare managedsite.

M

managed nodeIn a Tivoli environment, any managed resource on which the Tivoli ManagementFramework is installed.

managed object(1) A component of a system that can be managed by a management application. (2)The systems management view of a resource that can be managed through the useof systems management protocols.

managed resourceIn a Tivoli environment, any hardware or software entity (machine, service, system,or facility) that is represented by a database object and an icon on the Tivoli


Glo

ssary

desktop. Managed resources must be a supported resource type in a policy regionand are subject to a set of rules. Managed resources include, but are not limited to,managed nodes, task libraries, monitors, profiles, and bulletin boards.

N

NetWare managed siteIn a Tivoli environment, a resource that represents (a) a Novell NetWare server onwhich the Tivoli NetWare repeater (TNWR) is installed and (b) one or more clients.A NetWare managed site enables profiles to be distributed through the NetWareserver to one or more specified client PCs using either TCP/IP or IPX.

O

object request broker (ORB)In object-oriented programming, software that serves as an intermediary bytransparently enabling objects to exchange requests and responses.

oservThe name of the object request broker used by the Tivoli environment. Oserv runson the TMR server and each TMR client.

P

PC agentIn a Tivoli environment, software installed on a client PC that enables Tivolioperations to execute on the PC. See PC managed node.

PC managed nodeIn a Tivoli environment, an object that represents a client PC. The TivoliManagement Framework can communicate with the client PC only if the PC agentis installed on the PC. Client PCs are most often referred to as PC managed nodes.

policyIn a Tivoli environment, a set of rules that are applied to managed resources. Aspecific rule in a policy is referred to as a “policy method”.

policy regionIn a Tivoli environment, a group of managed resources that share one or morecommon policies. Tivoli administrators use policy regions to model the managementand organizational structure of a network computing environment. Theadministrators can group similar resources, define access to and control theresources, and associate rules for governing the resources. The policy regioncontains resource types and the list of resources to be managed. A policy region isrepresented on the Tivoli desktop by an icon that resembles a capitol building (dome

240 Version 3.7

icon). When a Tivoli Management Region (TMR) is created, a policy region withthe same name is also created. In this case, the TMR has only one policy region.However, in most cases, a Tivoli administrator creates other policy regions andsubregions to represent the organization of the TMR. A TMR addresses the physicalconnectivity of resources whereas a policy region addresses the logical organizationof resources.

R

Remote ControlA Tivoli Remote Control function that enables the Tivoli administrator to takecontrol of a remote target workstation to which it is linked over a network.

remote distributionIn a Tivoli environment, a distribution to target machines in a connected TivoliManagement Region.

resource roleThe role an administrator has over specific resources in the local TMR or anyconnected TMR (for example, policy regions or the Administrator collection).

S

saved configurationIn Tivoli Remote Control, a file containing Windows registry keys, initialization andother configuration data. The file is used by the Remote Diagnosis function torestore damaged or missing files on a target.

Sequenced Packet Exchange (SPX)A session-oriented network protocol used in a Novell environment. It relies on theInternet Packet Exchange (IPX) protocol, provides flow control and error recovery,and guarantees the reliability of the physical network.

serverA functional unit that provides services to one or more clients over a network.Examples include a file server, a print server, and a mail server.

siouxThe name of the Remote Diagnosis target application, sioux.exe

snapshotIn Tivoli Remote Control, a record of the state of a computer system at a particularmoment.The record includes the files specified in its Tivoli Software Distributionautopack type. See also Tivoli Software Distribution.


Glo

ssary

SPXSee Sequenced Packet Exchange.

T

TACFSee Tivoli Access Control Facility.

targetIn Tivoli Remote Control, a remote workstation that the controller acts upon.

TCP/IPSee Transmission Control Protocol/Internet Protocol.

TECSee Tivoli Enterprise Console.

Tivoli Access Control Facility (TACF)In Tivoli Security Management, an object-oriented security system that runs onUNIX-based operating systems and provides security functions that are not availableon UNIX (such as an access rule database, an audit log, and administration tools).TACF is invoked immediately after the operating system has completed itsinitialization, and it places hooks in system services that should be protected,thereby enabling control to be passed to TACF before the services are performed.

Tivoli administratorIn a Tivoli environment, a system administrator who has been authorized to performsystems management tasks and manage policy regions in one or more networks.Each Tivoli administrator is represented by an icon on the Tivoli desktop.

Tivoli Application Development EnvironmentA Tivoli toolkit that contains the complete application programming interface (API)for the Tivoli Management Framework. This toolkit enables customers and TivoliPartners to develop their own applications for the Tivoli environment.

Tivoli Application Extension FacilityA Tivoli toolkit that enables customers to extend the capabilities of Tivoliapplications. For example, customers can add fields to a dialog, create customattributes and methods for application resources, or create custom icons andbitmaps.

Tivoli clientA client of a Tivoli server. See TMR client and TMR server.

242 Version 3.7

Tivoli Cross-SiteThe integrated suite of Tivoli products for managing an e-commerce environment toensure that Web resources are secure and available and to enable applications andinformation to be distributed and maintained across the extended enterprise.

Tivoli desktopIn a Tivoli environment, the desktop that system administrators use to manage theirnetwork computing environment.

Tivoli Enterprise Console (TEC)A Tivoli product that collects, processes, and automatically initiates correctiveactions for system, application, network, and database events; it is the centralcontrol point for events from all sources. The Tivoli Enterprise Console provides acentralized, global view of the network computing environment; it uses distributedevent monitors to collect information, a central event server to process information,and distributed event consoles to present information to system administrators.

Tivoli environmentThe Tivoli applications, based upon the Tivoli Management Framework, that areinstalled at a specific customer location and that address network computingmanagement issues across many platforms. In a Tivoli environment, a systemadministrator can distribute software, manage user configurations, change accessprivileges, automate operations, monitor resources, and schedule jobs.

Tivoli install imageIn a Tivoli environment, a file that resides on a CD or in a file system and containsa Tivoli product to be installed. A Tivoli install image can be used to install theTivoli Management Framework or to install an application onto the Framework forthe first time. A single CD often includes both a Tivoli install image and a Tivoliupgrade image, and it may include Tivoli install images for more than oneapplication.

Tivoli Management Agent (TMA)In the Tivoli environment, an agent that securely performs administrative operations.

Tivoli Management FrameworkThe base software that is required to run the applications in the Tivoli product suite.This software infrastructure enables the integration of systems managementapplications from Tivoli Systems Inc. and the Tivoli Partners. The TivoliManagement Framework includes the following:

¶ Object request broker (oserv)

¶ Distributed object database

¶ Basic administration functions

¶ Basic application services


Glo

ssary

¶ Basic desktop services such as the graphical user interface

In a Tivoli environment, the Tivoli Management Framework is installed on everyclient and server; however, the TMR server is the only server that holds the fullobject database.

Tivoli management gatewayIn the Tivoli environment, a system that enables bidirectional communication withTivoli Management Agents.

Tivoli Management Region (TMR)In a Tivoli environment, a Tivoli server and the set of clients that it serves. Anorganization can have more than one TMR. A TMR addresses the physicalconnectivity of resources whereas a policy region addresses the logical organizationof resources.

Tivoli management softwareThe overall descriptor for software from Tivoli Systems Inc., which includes TivoliEnterprise software (for systems management in a large organization), Tivoli ITDirector (for systems management in a small or medium organization), and TivoliCross-Site (for the management of e-commerce systems). Tivoli managementsoftware enables organizations to centrally manage their computing resources(including the critical applications that drive business performance and profits) in asimple and straightforward manner.

Tivoli ManagerTivoli management software that manages specific vendor systems, networks,applications, or databases.

Tivoli NetWare repeater (TNWR)In a Tivoli environment, a server application that is installed on a Novell NetWareserver and that maintains a list of available clients for the server. The TivoliNetWare repeater works with the NetWare managed site to perform profiledistribution.

Tivoli Remote ControlA Tivoli product that enables a Tivoli administrator to control mouse and keyboardoperations on a Windows NT managed node, an endpoint, or a PC managed node. Italso provides File Transfer, Chat, Reboot, and Remote Diagnosis actions.

Tivoli Remote Control gatewayAn optional function that is available with the Tivoli Remote Control server tohandle communication between controllers and targets.

244 Version 3.7

Tivoli Remote Execution ServiceA service that enables a Tivoli environment to perform remote operations onmachines. These operations include: remotely installing clients, connecting TivoliManagement Regions (TMRs), and starting oserv from a remote machine.

Tivoli Security ManagementTivoli Enterprise software that enables the consistent definition, implementation, andenforcement of security policy in a network computing environment.

Tivoli serverThe server that holds or references the complete set of Tivoli software, including thefull object database.

Tivoli Software DistributionA Tivoli product that automates software distribution to clients and servers in anetwork computing environment. An organization can use this product to install andupdate applications and software in a coordinated, consistent manner across anetwork. Tivoli Software Distribution creates file packages and distributes them topredefined subscribers.

Tivoli upgrade imageIn a Tivoli environment, a file that resides on a CD or in a file system and containsupdates for a Tivoli product. A Tivoli upgrade image contains only the files thathave changed since the previous product release, with the scripts and commandsthat are needed for installing the new files and configuring the database.

Tivoli User AdministrationA Tivoli product that provides a graphical user interface (GUI) for centralizedmanagement of user and group accounts. It offers efficient, automated managementof user and system configuration parameters, secure delegation of administrativetasks, and centralized control of all user and group accounts in a network computingenvironment.

Tivoli UserLinkA Tivoli product that provides IP address synchronization between a PC agent andits associated PcManagedNode using the Dynamic Host Configuration Protocol(DHCP). Tivoli UserLink also enables a PC user to pull a file package to aWindows, Windows 95, or Windows NT workstation.

TMASee Tivoli Management Agent.

TMRSee Tivoli Management Region.


Glo

ssary

TMR clientIn a Tivoli environment, any computer—except the TMR server—on which theTivoli Management Framework is installed. The oserv daemon runs on the TMRclient, and the TMR client maintains a local object database.

TMR roleThe role an administrator has in the local TMR and any connected TMR. It providesthe assigned authorization level to all resources in the TMR. For example, if aTivoli administrator has a senior role in the TMR, this administrator has the seniorrole over every resource in that TMR.

TMR serverA Tivoli Server for a specific Tivoli Management Region (TMR).

Transmission Control Protocol/Internet Protocol (TCP/IP)(1) The Transmission Control Protocol and the Internet Protocol, which togetherprovide reliable end-to-end connections between applications over interconnectednetworks of different types. (2) The suite of transport and application protocols thatrun over the Internet Protocol.

V

vital objectsIn Tivoli Remote Control, the critical files and directories, registry entries and othersettings that ensure an application functions correctly.

246 Version 3.7

Index

AActive state 89agents 134Alt+Esc 92Alt+Tab 92

Cchanges

registry 140chat

activate 98recording conversation 98start session 95suspend 98using with remote control 99

Chat window 96command line syntax 143commands

odstat 136wcreaterc 51, 144wgetpolm 76winstall 16wln 54wmv 54, 133wputpolm 76wrc 145wrcinstep 150wrcmdpcr 152wregister 137

components 13CONFIG.SYS file 140, 142controller

logging events 160setting OS/2 traces 158setting Windows traces 156uninstalling 24

controller (continued)using 87

createrc command 144creating a managed resource 50Ctrl+Alt+Del 92Ctrl+Esc 92Ctrl+Shift+Esc 92

Ddefault policy

list of methods 60setting 55

diagnosiscollect artifacts 115protect/restore vital objects 114restore target configurations 113save target configurations 112start session 106suspend/activate session 113, 119

dialogsTivoli Remote Control 88

Eendpoint

Remote Control deinstallation 27Remote Control installation 17

error messageshost not managed node 136host not PC managed node 136resource not found 136start_controller 134start_target 134Unable to monitor remote host 137


Ind

ex

FFAQs 131File menu 89file transfer

log 104, 161start session 101

File Transfer window 102, 107files

CONFIG.SYS 140, 142OS2.INI 142SYSTEM.INI 140, 142WIN.INI 139, 140

frequently asked questions 131

Ggateway

closing 134definition 2uninstalling 24using 77

Hhardware requirements 8Help menu 89

IIME hot key 92improving performance 163installation 12

directories 13installing

with SIS 14with Tivoli Desktop 14with winstall 16

installing on endpoints 17interoperability 21

Kkeyboard modes 91Keystrokes menu 89

Llogging events on controller 160

Mmemory requirements 8menus

File 89Help 89Keystrokes 89State 89View 89

methods for the Default Policy 60migrating from version 3.6 (3.6B) or 3.6.1 22mixed keyboard support 93Monitor state 89

Oodstat command 136OS/2 file changes 140, 142OS2.INI file 142

PPacks

uninstalling 25pcgateway 134performance

improving 163Plugins

uninstalling 25

248 Version 3.7

policy method rc_def_rd_config 72policy methods

rc_def_alt_t 61rc_def_backgrnd 61rc_def_checkinterp 62rc_def_color 62rc_def_command 63rc_def_comp 63rc_def_define 64rc_def_filter_mode 65rc_def_ftmode 65rc_def_grace_time 66rc_def_gw 66rc_def_inactivity 67rc_def_initstate 68rc_def_polfilter_mode 68rc_def_ports 69rc_def_rate 71rc_def_rcmode 71rc_def_targets 73rc_def_tfc 73rc_def_timeout_op 74rc_def_uncheckedlist 74

Rrc_def_alt_t policy method 61rc_def_backgrnd policy method 61rc_def_checkinterp policy method 62rc_def_cmmand policy method 63rc_def_color policy method 62rc_def_comp policy method 63rc_def_define policy method 64rc_def_filter_mode policy method 65rc_def_ftmode policy method 65rc_def_grace_timer policy method 66rc_def_gw policy method 66rc_def_inactivity policy method 67rc_def_initstate policy method 68rc_def_polfilter_mode policy method 68rc_def_ports policy method 69rc_def_rate policy method 71rc_def_rcmode policy method 71rc_def_rd_config policy method 72

rc_def_targets policy method 73rc_def_tfc policy method 73rc_def_timeout_op policy method 74rc_def_uncheckedlist policy method 74reboot after abnormal termination 106registry changes 139, 140, 141Remote Control controller

using 87Remote Control target

using 90requirements

hardware 8software 9

Sscroll pointer 134sending

Alt+Esc 92Alt+Tab 92Ctrl+Alt+Del 92Ctrl+Esc 92Ctrl+Shift+Esc 92IME hot key 92

serverdefinition 2uninstalling 24

settingdefault policy 55traces

on OS/2 controller 158on OS/2 target 158on Windows controller 156on Windows target 156

sioux, two instances on targetRemote Diagnosis 106

software requirements 9starting Tivoli Remote Control application from

Command Line 85starting Tivoli Remote Control feature 77State menu 89states

Active 89Monitor 89


Ind

ex

states (continued)Suspend 90

Suspend state 90switching between keyboard modes 91SYSTEM.INI file 140, 142

Ttarget

leaving connection open 133setting OS/2 traces 158setting Windows traces 156uninstalling 24using 90

TEC 19timeout setting 133Tivoli Remote Control

interoperability 21starting from Command Line 85uninstalling 24

Tivoli Remote Control dialog 88Tivoli Remote Control feature

starting 77Tools

uninstalling 25troubleshooting

timeout setting 133

Uuninstalling

gateway 24packs 25Plugins 25server 24Tools 25

uninstalling chat 36, 40, 44uninstalling diagnosis packs 45uninstalling file remote diagnosis 42uninstalling file transfer 39uninstalling on endpoints 27

uninstalling tools 46using

controller 87gateway 77target 90

Vvariables

WD_DISPLAY 136View menu 89vital objects

protect/restore 114

Wwcreaterc command 51WD_DISPLAY variable 136wgetpolm command 76WIN.INI file 139, 140Windows

file changes 139, 140registry changes 139, 141

Windows 95 and Windows 98registry 140

winstall command 16wln command 54wmv command 54, 133wputpolm command 76wrc command 145wrcinstep command 150wrcmdpcr command 152wregister command 137

250 Version 3.7

Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.

GC31-8437-06