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 server
Remote Control server supports the following installation types:
Set up the database
Setting up MSSQL
Creating the database

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:
      - Set up the database
        Setting up DB2®
        Setting up Oracle
        Setting up MSSQL
        Creating the database
      - Installing by using the server installer
        The Remote Control server installer can be used on Windows™ operating systems, Red Hat Linux™ operating systems, and SUSE Linux operating systems. A fully functional self-contained server with either of the following component setup is installed.
      - Installing on WebSphere Application Server version 8.5.5: deploying the war file
      - Installing from the BigFix console
    - Install the target
    - 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.
  - 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

Creating the database

About this task

Use the MS SQL management studio to complete the following steps:

Procedure

Click Connect.
Right-click the server tree and click properties.
Select security.
Ensure that SQL server and authentication mode is selected.
Expand the server tree.
Right-click databases.
Select Create New Database.
Enter a name for the database. For example, TRCDB. Click OK.

Results

The default owner of the database is user sa, the system administrator. Create a new user, to be the owner of the database being used with Remote Control.

Database permissions

The default system administrator is the owner of the database and therefore has the required permissions for using the database. If you have created a new user, they also have the required permissions if they have been assigned as the owner of the database.