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.
Overview of the Remote Controlsystem
Remote Control operating requirements
Server environment guidelines

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 Controlsystem
    - How to use the guide
    - Remote Control operating requirements
      - A Basic installation
        The most basic installation requires the Remote Control target and controller components. Use the two components to start a peer to peer remote control session, for which the policies are defined only at target level.
      - Installation with support for firewall and NAT traversal
        In some environments, it is not possible to open a port in a firewall to enable controller to target, or target to server communication for all endpoints. It is more appropriate to enable traffic from, or traffic to a single computer that acts as a gateway to traverse the firewall.
      - Installation with support for remote control sessions over the internet
        Sometimes the target that requires support is out of network sight in an internet location. For example, in a hotel or an airport lounge.
      - Server requirements
        The hardware that is required by the server component depends on the number of computers that are administered and the frequency that is defined for their status updates.
      - Server environment guidelines
        Small environment guidelines
        Medium environment guidelines
        Large environment guidelines
      - Controller requirements
        The Controller is a Java™ based application that can run on the following operating systems with the listed prerequisites.
      - Target requirements
      - Gateway requirements
      - Broker requirements
  - 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.
  - 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 TLSv1.3
  - Federal information processing standard (FIPS 140-2) 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

Server environment guidelines

In addition to system requirements, you must also determine which type of server installation to use in your environment. Use the following information as a guide.

Table 1. Remote Control server installation types
Server installation type	Components installed	Install by using the BigFix® console	Install by using the installation files
1	Embedded Liberty profile. Embedded Derby database.	Yes	Yes
2	Embedded Liberty profile, that uses an already installed DB2®, MS SQL, or Oracle database	Yes	Yes
3	Stand-alone Remote Control server that accesses WebSphere Application Server, by using an already installed DB2®, MS SQL, or Oracle database	No	Yes

Note: Server installation types 1 and 2 are available only when you use Windows® or Linux® operating systems.

Note: Server installation type 1 must be used only in Proof of Concept or test deployments.

The following sections provide guidance and recommendations based on environment size.