This guide is for users who want to administer BigFix® Remote Control.
By using BigFix® 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 BigFix® Remote Control
To prevent unauthorized targets from registering with the BigFix® Remote Control server, you can use tokens to authenticate the target.
BigFix® Remote Control V9.1.3 introduced support for SAML 2.0 authentication on the BigFix Remote Control server.
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. Note that the Java Web Start plugin method is deprecated in Remote Control starting from Version 10.0.0 Update 8 (Build Number 0802). 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 BigFix® 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 BigFix® 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.
When using BigFix® Remote Control to facilitate remote control sessions across the internet, you can use certificates to address the authentication and verification required for ensuring secure connections between brokers and endpoints.
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 BigFix® 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.
Use BigFix® Remote Control to start remote control sessions over the internet with targets that do not have the target software installed.