Configuring global controller properties

Edit the trc_controller.cfg and controller.properties files file to create and configure global controller properties. The properties are used by the Remote Control controller component during a peer to peer remote control session. The property values are the same for every user who runs the controller.

About this task

When the controller component is installed, a properties file, trc_controller.cfg, is also installed when you are using the peer to peer controller. For the controller that is used for sessions that are started from the server, the controller.properties file is available. Use these files to create and configure various properties to provide more function during a remote control session. This section provides the steps for configuring the properties for the peer to peer controller. For more information about configuring the controller properties for managed remote control sessions, see the section on editing property files in the BigFix® Remote Control Administrator's Guide.
Note:
You must have administrator authority on the system that the controller component is installed on to be allowed to edit the properties file.
For more information about configuring global controller properties for managed remote control sessions, see the section on editing property files in the BigFix® Remote Control Administrator's GuideEditing the properties files.

A user can also configure a set of properties locally, by using the Configure Controller feature in the controller UI. The local property values override the global property values. For more information about configuring local properties, see Creating a local configuration for the controller.

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 configure the controller properties, complete the following steps:

Procedure

  1. Edit the trc_controller.cfg file.
    Note:
    To edit the file, you must have administrator authority on the system that the controller component is installed on.
    Windows® systems
    [controller install dir]\trc_controller.cfg

    Where [controller install dir] is the directory that the controller is installed in.

    Linux® systems
    opt/bigfix/trc/controller/trc_controller.cfg
  2. Add or configure the relevant property.
    To set a property as mandatory, 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.
  4. Stop and start the controller component.

Results

The new property values are in effect for any new peer-to-peer sessions that the controller starts with a target.