Welcome
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 target
Run a target custom installation
Installing and configuring the target using the RPM file
Installing the Source RPM package

BigFix Documentation Homepage
BigFix 10 Lifecycle Documentation
Welcome to the BigFix Lifecycle documentation, where you can find information about how to install, maintain, and use BigFix Lifecycle.
BigFix Platform
BigFix Query
Lifecycle overview
BigFix Lifecycle is single-agent, single-console technology that provides near real-time visibility into the state of endpoints.
Lifecycle guides in PDF format
Following is a list of links to the BigFix Lifecycle guides in PDF format:
Software Distribution
Use the BigFix Software Distribution applications to deploy software to endpoints across your network from a single location. Maintain control and visibility into software delivery and installation. Device owners can use the Self Service Application to manage software and other BigFix actions that are deployed to them as offers.
OS Deployment
BigFix OS Deployment, which is part of the BigFix Lifecycle Management suite, provides a consolidated, comprehensive solution to quickly deploy new workstations and servers throughout a network from a single, centralized location. This solution saves time and money, enforces a standardized and approved image, and reduces risks associated with non-compliant or insecure configurations.
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
    The Remote Control system enables remote control via Target, Controller, and Server components that support peer-to-peer and managed operation. Managed mode adds centralized policy, user authentication, and auditing/recording, and can use CLI tools, Gateways, and Brokers to reach targets across restricted networks and the internet.
  - 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
      - Installing Windows Target
        The trc_target_setup.exe file is required to install the Remote Control target component on a Windows™ system.
      - Installing the Linux™ target
        You can install the target component on a Linux™ computer by using the RPM file that is provided in the Remote Control installation files.
      - Install the BigFix® Remote Control Target for macOS
        You can install the BigFix® Remote Control Target for macOS in numerous ways. Use the trc_target.pkg file to install the application in attended or unattended mode. You can also install the target by using a Fixlet® in the BigFix console.
      - Run a target custom installation
        Running a target custom installation on a Windows® system
        To install the target software on a Windows® operating system, use the trc_target_setup.exe file.
        Installing and configuring the target using the RPM file
        Configuring the RPM build tree
        Obtaining the target source RPM file
        Installing the Source RPM package
        Customizing the SPEC file
        Customising the default configuration file
        Building your customized target RPM package
        Installing the target by using the SPB file
        You can install the Remote Control target components on a Windows® system and a Linux® system by using the Software Package Block (SPB) installation method.
    - Install the controller
    - 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.
    - Install Web Session Manager support
      The Web Session Manager is automatically included with the broker support installation; no standalone package is needed and is compatible with both Windows and Linux environments.
  - 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.
  - AV Exclusions on Windows, Linux and MAC
    This topic provides guidance on configuring anti-virus (AV) and intrusion detection system (IDS) exclusions for BigFix Remote Control on Windows, Linux, and Mac platforms. It details the specific directories and processes that should be excluded to prevent interruptions or failures during remote control sessions. Proper configuration helps ensure reliable operation and avoids common errors related to AV or IDS interference.
  - Support
    For more information about this product, see the following resources:
  - Notices
- 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
Power Management
Use Power Management to control, monitor, and manage conservation policies in your deployment.
Application Control
BigFix Application Control provides a robust framework for managing application usage within an organization. It allows administrators to define policies that dictate which applications can or cannot be run on endpoints, thereby enhancing security and compliance.
Server Automation
Server Automation provides powerful automation. You can use it to sequence automation actions in steps across multiple endpoints.
Virtual Endpoint Manager
HCL BigFix Virtual Endpoint Manager (VEM) enhances BigFix with centralized, unified endpoint management for hybrid cloud and data center environments, spanning virtual machines and physical endpoints. VEM delivers real-time endpoint visibility, policy-driven automation for configuration and compliance remediation, and consistent security controls to streamline IT operations, reduce risk, and strengthen regulatory compliance.
Profile Management
Profile Management is a WebUI-based feature of BigFix Lifecycle. It provides Security Administrators the capability to define and deploy security policies to Windows 10 and macOS devices.
BigFix Remediate
BigFix MCM

Installing the Source RPM package

About this task

Installing a source RPM package installs the files that are needed to build or rebuild the package into the RPM build tree.

Use the following command to install the package for the Target:

$ rpm -ivh ~/BigFix/Tivoli_Remote_Control/RCTarget/trc-target-10.x.x.src.rpm

Where 10.x.x is relevant to the version that you want to install. For example, 10.x.0.

Note:

This command might generate warnings about users and groups that do not exist. These warnings are because your system does not have the user and groups that were used to build the original package. You can ignore these warnings.

Examples of the warning messages:-

Warning: user user name does not exist - using root

Warning: group build does not exist - using root

Warning: group trc_build does not exist - using root

To verify that this step was successful, check the SPECS and the SOURCES directories and make sure that the following files are there:

$ ls SPECS/ SOURCES/

SOURCES/:trc-target.tar

SPECS/: trc-target.spec