BigFix Remote Control application helps to communicate between different components, clients, and endpoints within BigFix environment.
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.
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.
A summary of changed or new features and enhancements included in BigFix Remote Control.
Now that you understand the terms and components available in Remote Control, you can identify which components you need to install:
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.
Remote Control provides a utility that you can use to extract the installation files that are required for each component.
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.
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.
After you install the Remote Control components, if you change their configuration, you can stop, start, or restart the component services.
The Remote Control controller is a Java™ application that requires a FIPS certified cryptographic provider when FIPS compliance is enabled. In FIPS-compliant mode the Remote Control controller supports the BC-FJA (Bouncy Castle FIPS Java API) with the IBM Semeru Runtime Open Edition JRE on Windows, Linux and MacOS.
You can enable FIPS compliance on the gateway component by editing the gateway configuration file that is created when you install gateway support.
You can enable FIPS compliance on the broker component by editing the broker configuration file that is created when you install broker support.
Remote Control version 10.0.0 components can be configured for NIST SP800-131A compliance.
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.
This guide is for users who want to administer Remote Control.
Use Remote Control to start remote control sessions over the internet with targets that do not have the target software installed.