BigFix Remote Control application helps to communicate between different components, clients, and endpoints within BigFix environment.
This guide is for users who want to administer Remote Control.
A summary of changed or new features and enhancements included in BigFix Remote Control.
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.
Set a secure environment when you are using Remote Control.
To prevent unauthorized targets from registering with the Remote Control server, you can use tokens to authenticate the target.
Remote Control V9.1.3 introduced support for SAML 2.0 authentication on the Remote Control server.
After you install the BigFix® Remote Control Server software and the BigFix Remote Control Target software, you can log on to the server application. For more information about installing and configuring the server and target software, see the Remote Control Installation Guide
The Deployment Status Dashboard provides a quick view of the system and brokers health status.
The Unattended Target Support feature allows you to take remote control sessions of targets that are connected through a broker, without the need to provide a connection code. In strict remote control terminology, an unattended target is a managed target that performs Call Home through a broker.
When a user account is locked, you can unlock the account by using the Unlock locked userid feature.
When you start a managed session, you can configure the server to use an installed controller rather than using the Java™ Web Start method. This feature makes starting a session faster and it removes any warning message windows that are displayed while the session is starting.
You can use the properties files in Remote Control to customize your environment, configure LDAP, set debug options, and set controller and on-demand target properties. The files can be edited in the BigFix® Remote Control Server UI.
When you install broker support you can use the installed trc_broker.properties file to configure your environment for using the broker function.
After installing broker support you can register the broker machines in the Remote Control server. When they have been registered you can view the list of brokers, edit the broker details and delete brokers that are no longer required.
Remote Control uses certificates in the Server and in the Broker to address the authentication and verification required for ensuring secure connections between the different product components.
If your existing certificates are due to expire, you can create new certificates. Distribute the new certificates to the relevant endpoints so that they can continue to successfully establish remote control sessions through the broker.
You can define the number of characters required and the timeout value, for the connection code used when starting a remote control session through a broker.
When you have targets that are on the internet or third-party networks and cannot register directly with the Remote Control server you can configure server properties to allow the target to register with the server. When the target registers, you can start a remote control session with the target, by using a broker.
Use properties to determine what type of information and how much is written to the broker, gateway, and target component log files.
The controller uses the proxy defined at system level by default. In some conditions, this may not be desirable. Creating a file named “override.proxy” in the controller install folder changes the default behavior and the system proxy is ignored
Use Remote Control to start remote control sessions over the internet with targets that do not have the target software installed.
You can set standard reports or custom report to the default page.