Installing a preconfigured controller component

You can apply custom configuration settings when you install the controller component.

About this task

Preconfiguring the controller is useful for unattended installations. You can set your configuration file values in the configuration file and copy the file to the computers that you want to install the controller on. Your configuration settings are installed together with the controller. The configuration values are set in the trc_controller.cfg file. You can create the file and add your custom values or you can edit a default configuration file. If you do not apply any preconfiguration, the default configuration file is installed when you install the controller component.

The property values in the trc_controller.cfg are global and are the same for all users who run the controller. However, a user can create a local configuration. The values in the users' local configuration are used when they run the controller and override the global values. To enforce the global property value, you can set a property to mandatory so that a user cannot edit the property in the Configuration Window in the controller UI. The mandatory global property overrides the local property.

To set a mandatory property, complete the following steps:
  1. Open the trc_controller.cfg file.
  2. Copy the property name and add .mandatory = true to the end.

    For example, to make the Enable Address History property mandatory so that it cannot be edited in the Configuration Window.


    enable.address.history=false
    enable.address.history.mandatory=true

  3. Save the file.

After you save the trc_controller.cfg file, install the controller.

Preconfigure the controller for a Windows™ operating system installation
  1. Copy the trc_controller.cfg file to the same directory as the trc_controller_setup.exe or trc_controller.msi file.
  2. Run the controller installation file.
The controller is installed with your configured settings.
Note: Preconfiguring the controller is not supported for installation on a Linux™ operating system. If necessary, you can modify and rebuild the controller .rpm file from the source .rpm file.

Example

Use the content of the default configuration file to create your custom configuration file and set your own values.



fips.compliance=false

sp800131a.compliance=false

enable.address.history=true

enable.user.history=false

enable.domain.history=true

history.max.items=20

tool01.ToolName = Control Panel
tool01.ToolCommand = [SystemFolder]\\control.exe
tool01.ToolParameters =
tool01.ToolUser =

tool02.ToolName = Command Prompt
tool02.ToolCommand = [SystemFolder]\\cmd.exe
tool02.ToolParameters =
tool02.ToolUser =

tool03.ToolName = Administrator Command Prompt
tool03.ToolCommand = [SystemFolder]\\cmd.exe
tool03.ToolParameters =
tool03.ToolUser = admin

tool04.ToolName = Task Manager
tool04.ToolCommand = [SystemFolder]\\taskmgr.exe
tool04.ToolParameters =
tool04.ToolUser =

tool05.ToolName = Windows™ Explorer
tool05.ToolCommand = [WindowsFolder]\\explorer.exe
tool05.ToolParameters =
tool05.ToolUser =

tool06.ToolName=Terminal
tool06.ToolCommand=/usr/bin/gnome-terminal
tool06.ToolParameters =
tool06.ToolUser =

tool07.ToolName=Control Panel
tool07.ToolCommand=/usr/bin/gnome-control-center
tool07.ToolParameters =
tool07.ToolUser =

tool08.ToolName=
tool08.ToolCommand=
tool08.ToolParameters =
tool08.ToolUser =

tool09.ToolName=
tool09.ToolCommand=
tool09.ToolParameters =
tool09.ToolUser =

tool10.ToolName=
tool10.ToolCommand=
tool10.ToolParameters =
tool10.ToolUser =

# Custom keys

# example.KeySequenceName = Inject F1
# example.KeySequenceValue = [F1]
#
# For a list of supported key codes, please refer to the User's Guide

key01.KeySequenceName =
key01.KeySequenceValue =

key02.KeySequenceName =
key02.KeySequenceValue =

key03.KeySequenceName =
key03.KeySequenceValue =