Using remote control commands from the command line

There are two commands that you can run from the command line to start a remote control session with a target or run commands on a target system without target user interaction. These commands can be useful if you want to connect to a target without using the usual IBM® Endpoint Manager for Remote Control Server interface or for using as part of a script to run multiple commands in an automated fashion. See the IBM Endpoint Manager for Remote Control Installation Guide for details of how to install the command line tools.

There are two command line tools available

• wrc - to start a remote control session.
• wrcmdpcr - to run a command on a target and see the output from the command on the machine that you issued the command from.

Before using the command line tools the following configuration actions should be carried out.

• The server URL defined in the trc.properties file on the server should be the same URL defined in the ServerURL property in the target properties.
• The remote control port defined during the installation of the command line tools should be the same on both the machine that the commands are being issued from and in the target settings.
• If FIPS compliance is required the machine that is issuing the command and the target both require FIPS compliance enabled. See the IBM Endpoint Manager for Remote Control Installation Guide for details of enabling FIPS compliance.
  Note: The machine that will be starting the controller software requires a registry key entry named JavaHome which contains the path to the FIPS compliant IBM JRE that is installed with the controller software. If you are starting the controller on a remote machine you must create a registry key entry on the remote machine too.

  Windows systems

  C:\Program Files\IBM\tivoli\Remote Control\Controller\jre

  Linux systems

  Edit the ibmtrct.conf file and update the value of the JavaHome property.

• If logging needs to be enabled when running the wrcmdpcr command ensure that the DebugTrace property is set to yes, in the target settings. A text file, cli_trace.txt, will be created in the same location as the target log files.