Home
Remote Control
BigFix Remote Control application helps to communicate between different components, clients, and endpoints within BigFix environment.
Remote Control Installation Guide
By using Remote Control you can remotely support and control thousands of PCs and servers, on an enterprise scale, from a central location or directly, in peer to peer mode.
Install the Remote Control components
The Remote Control components can be installed in two ways. If you have access to the BigFix® console, use a deployment fixlet to install the components.
Install the controller
Installing the Linux™ controller

Remote Control
BigFix Remote Control application helps to communicate between different components, clients, and endpoints within BigFix environment.
- Release notes
  A summary of changed or new features and enhancements included in BigFix Remote Control.
- Remote Control Installation Guide
  By using Remote Control you can remotely support and control thousands of PCs and servers, on an enterprise scale, from a central location or directly, in peer to peer mode.
  - Audience
  - Versions
  - Terms used in this guide
  - Overview of the Remote Control system
  - Get started
    Now that you understand the terms and components available in Remote Control, you can identify which components you need to install:
  - Install the Remote Control components
    The Remote Control components can be installed in two ways. If you have access to the BigFix® console, use a deployment fixlet to install the components.
    - Obtain the installation files
      The installation files for installing the Remote Control components can be obtained in various ways.
    - Install the server
      Remote Control server supports the following installation types:
    - Install the target
    - Install the controller
      - Installing the controller on a Windows™ system
        The trc_controller_setup.exe file is required to install the controller component on a Windows™ system.
      - Installing the Linux™ controller
      - Install the BigFix® Remote Control Controller for macOS
        The BigFix® Remote Control Controller for macOS can be installed in multiple ways. You can use the trc_controller.pkg file to install the application. You can also install the controller by using a Fixlet® in the BigFix console.
      - Installing the controller in other supported operating systems
      - Installing a preconfigured controller component
        You can apply custom configuration settings when you install the controller component.
    - Install the command-line tools
    - Install gateway support
      For targets, controllers, and server on different networks that cannot directly contact each other you can install and configure gateway support.
    - Install broker support
      Broker support must be installed on the computers that connect the controller to the target computer when the target computer is not directly accessible by the controller and the connection is made across the internet.
  - Utility for extracting the component installation files
    Remote Control provides a utility that you can use to extract the installation files that are required for each component.
  - Enable secure target registration
    To prevent unauthorized targets from registering with the Remote Control server, you can enable the secure registration feature and use tokens to authenticate the target.
  - Install the driver for smart card authentication
    The BigFix® Remote Control Target provides an installation option to install a virtual smart card reader driver. You can also install the driver by running a fixlet in the BigFix console.
  - Manage the component services
    After you install the Remote Control components, if you change their configuration, you can stop, start, or restart the component services.
  - Enabling email
  - Configure LDAP
  - Configure Microsoft Entra ID
  - Configure TLSv1.3
  - Federal information processing standard (FIPS) compliance in Remote Control
    The US Federal information processing standard 140-2 (FIPS 140-2) is a cryptographic function validation program that defines security standards for cryptographic modules that are used in IT software.
  - NIST SP800-131A compliance in Remote Control
    Remote Control version 10.0.0 components can be configured for NIST SP800-131A compliance.
  - Verifying the server installation
  - Recover from installation errors
  - Uninstall the components
  - Upgrade from previous versions
  - Maintaining the target installation
  - Properties that can be set in the target configuration
    You can configure target properties either during or after installation. The operating system on the target system determines which properties can be configured. The target properties determine the actions that can be carried out during a peer-to-peer session. If you set a server URL and set the Managed property to Yes, the actions are determined by the policies that are set on the Remote Control server.
- Remote Control Administrators Guide
  This guide is for users who want to administer Remote Control.
- Remote Control Console User Guide
- BigFix Remote Control Controller Users Guide
- Remote Control Target Users Guide
- Remote Control On-demand Target Guide
  Use Remote Control to start remote control sessions over the internet with targets that do not have the target software installed.
- Remote Control V10 Readme

Installing the Linux™ controller

Before you begin

Use the trc-controller-10.x.x.noarch.rpm and trc-controller-jre-10.x.x.<arch>.rpm files to install the controller component in Linux™. Where 10.x.x is relevant to the version that you want to install. For more information about how to obtain the Linux™ component installation files, see Install the Remote Control components. Choose the appropriate method for obtaining the file.

About this task

You can install the controller in two modes in Linux™, a FIPS-compliant controller or a standard controller.

Procedure

Type the relevant command for installing the controller. Where 10.x.x is relevant to the version that you want to install. .

For the standard controller type
#<install_command> trc-controller-10.x.x.noarch.rpm

For a FIPS-compliant controller, install the standard controller and the FIPS-compliant JRE by running both commands.
#<install_command> trc-controller-10.x.x.noarch.rpm
#<install_command> trc-controller-jre-10.x.x.<arch>.rpm

Results

To install the trc-<component>-10.x.x.<arch>.rpm package of the component, run the dnf, yum, or zypper command by providing the install -y option and the RPM package file path. Otherwise. if you want to manually resolve the dependencies, use the rpm -ivh <package>.rpm command. You can also get the complete dependency list by running the rpm -qpR <package>.rpm command.

Note: Standard controller installations work with the trc-controller-10.x.x.noarch.rpm file, with an alternative JRE installed on the system. If the controller is to be FIPS-compliant or if you don’t have a compatible JRE installed on the system, the trc-controller-jre-10.x.x.<arch>.rpm file must also be installed.

You can start the controller from your applications list when it is installed.

To add feedback about this topic, select the following checkbox:

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners Four, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site. Personal data should not be shared in this comment box. See our Privacy Statement to understand how personal data is used.