Running tools on the target during a remote control session

Configuration settings to add custom menu items to the controller UI. The menu items are added to the Perform Action in Target menu and can be used to run commands on the target during a remote control session.

Note: If too many items are added to the Perform Action in Target menu, the last items in the menu might extend beyond the bottom of the screen. In particular on a smaller screen size, with no support for scrolling menus.

By default, you can configure seven preconfigured tools in the server UI. Three blank tools are also available by default. To add more tools, manually edit the controller.properties file.

Refer to Editing the properties files topic to change the values from the server web interface.

If you need to add additional tools but there is no more room in the controller.properties configuration, you need to manually edit this file on the Remote Control server. Stop the Remote Control server service before editing the file:

<server_install_folder>\wlp\usr\servers\trcserver\apps\TRCAPP.ear\trc.war\WEB-INF\classes\controller.properties

You can create empty tool sections with progressive numbering, then after the Remote Control server service restarts you can proceed with the normal editing from the web interface as usual.

Note: After you manually edit the file, restart the server service or click Admin > Reset Application in the server UI.

prefix.ToolName =


Modifiable field	prefix.ToolName
Field Description	Display name that is used in the Perform Action in target menu. Each defined tool name must have a different prefix.
Possible Values	User Defined. For example, `tool01.ToolName=Command Prompt` The text, Command Prompt, is displayed in the Perform Action in target menu.
Value Definition

prefix.ToolName.$lang$=


Modifiable field	prefix.ToolName.$lang$
Field Description	Display name that is used in the Perform Action in target menu. Translation of display name. $lang$ is the ISO language code.
Possible Values	User Defined.
Value Definition

prefix.ToolCommand=


Modifiable Field	prefix.ToolCommand
Field Description	Command to run the tool, without parameters.
Possible Values	User Defined. For example, tool01.ToolCommand=[SystemFolder]\\control.exe The tool command can be a fully qualified path or just the file name. The file must be on the PATH environment variable of the logged in user. You can specify executable files but also files that are associated with an executable file. Do not use quotation marks, even with a path or file name that contain spaces. For example, tool01.ToolCommand=cmd.exe and tool01.ToolCommand=[SystemFolder]\\cmd.exe are equivalent. Note: When you use a backslash in the path, you must enter two backslashes. You can use the following folder properties when you define Windows™ tools parameters. The target substitutes the values with the actual path on the target system. [WindowsFolder] The target uses the following path to run the tool. `[WindowsVolume]\Windows` [SystemFolder] The target uses the following path to run the tool. `[WindowsFolder]\System32` Folder properties are not relevant for Linux™ targets. `lnxcontrol.ToolCommand = /usr/bin/gnome-control-center`
Value Definition

prefix.ToolParameters =


Modifiable field	prefix.ToolParameters
Field Description	Optional parameters for the command to run.
Possible Values	User defined
Value Definition

prefix.ToolUser =


Modifiable Field	prefix.ToolUser
Field Description	Determines which privileges or credentials the command is run with.
Possible Values	<blank> or admin
Value Definition	<blank> Run the tool as the logged on user. Note: Might trigger UAC prompts depending on the version of Windows™. This value is the default value. admin Run the tool with UAC prompt to elevate privileges. prompt Start a process as a different user (other than the current logged on user) and provide a way to elevate that user instead of the current logged on user (the elevation may be restricted to this user). A credential panel will appears on the Target machine and the credentials specified there will be used to start the tool process. Note: This feature is currently supported only on Windows OS with an installed Target or on On-demand Target. On the latter only if elevation is not performed. If you want the process to be run as a different user and also you want this process to gain the Elevated privileges you can use a configuration like this: toolXX.ToolName=My Program with Prompt toolXX.ToolCommand=[SystemFolder]\cmd.exe toolXX.ToolParameters=/c powershell start-process myprogram.exe -verb runas toolXX.ToolUser=prompt Make sure that myprogram.exe can be run from a normal cmd.