Home
Remote Control V9.1.4
BigFix® Remote Control V9.1.4 Administrators Guide
This guide is for users who want to administer BigFix® Remote Control.
Set a secure environment
Set a secure environment when you are using BigFix® Remote Control
Protocol configuration after a server upgrade
When you upgrade by using the server installer program and select to keep existing properties, you must configure properties after installation if you change your protocol selection.

Remote Control V9.1.4
- Release Notes V9.1.4 Fixpack 1
- BigFix® Remote Control V9.1.4 Installation Guide
  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.
- BigFix® Remote Control V9.1.4 Administrators Guide
  This guide is for users who want to administer BigFix® Remote Control.
  - Set a secure environment
    Set a secure environment when you are using BigFix® Remote Control
    - Configure the server URL
      Configure properties to allow the target to use a secure URL to communicate with the BigFix® Remote Control Server.
    - Protocol configuration after a server upgrade
      When you upgrade by using the server installer program and select to keep existing properties, you must configure properties after installation if you change your protocol selection.
    - Signed certificate management
      By default, BigFix® Remote Control creates a self-signed certificate for the website.
    - Setting password rules
    - Lock user accounts
    - Automatic passphrase encryption
      For security purposes, plain text passwords that are contained in the broker, gateway, target, and CLI component configuration, are now automatically encrypted. Use the DisableAutomaticPassphraseEncryption property to determine whether the passwords are automatically encrypted or not.
    - Enforcing strict HTTPS validation of certificates
      You can configure BigFix® Remote Control to enforce strict HTTPS validation of certificates. All HTTPS connections from the target, broker, CLI, and controller are verified and the connection fails if the certificate is not trusted.
  - Secure target registration
    To prevent unauthorized targets from registering with the BigFix® Remote Control server, you can use tokens to authenticate the target.
  - Configure SAML 2.0 authentication on the server
    BigFix® Remote Control V9.1.3 introduced support for SAML 2.0 authentication on the BigFix Remote Control server.
  - Access the server web interface.
  - Unlocking user accounts
    When a user account is locked, you can unlock the account by using the Unlock locked userid feature.
  - Manage targets and target groups
  - Manage users and user groups
  - Server session policies
  - How session policies are determined
  - Starting a managed session by using an installed controller
    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.
  - Manage permission sets for temporary access to targets
  - Requests for temporary access to targets
  - Generate custom reports
  - Manage the home page for a user or group
  - Adding tables and columns to queries
  - Configuration and troubleshooting options in the Admin menu
  - Ensure targets are registered correctly
  - Record the session on the target
  - Set up for exporting recordings
  - Audit log distribution
  - Access targets on different networks
  - Editing the properties files
    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.
  - Reduce the volume of target connections to the server
  - Broker configuration
    When you install broker support you can use the installed trc_broker.properties file to configure your environment for using the broker function.
  - Managing brokers
    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.
  - Certificate management
    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.
  - Migrating to a new certificate
    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.
  - Configuring the session connection code
    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.
  - Target registration before a remote control session
    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.
  - Configure target properties
  - Importing data from other sources
  - Database table and column descriptions
  - Troubleshooting and Help
  - Gateway sample scenarios
  - Properties for configuring logging activity
    Use properties to determine what type of information and how much is written to the broker, gateway, and target component log files.
- BigFix® Remote Control V9.1.4 Console Users Guide
- BigFix® Remote Control V9.1.4 Controller Users Guide
- BigFix® Remote Control V9.1.4 Target Users Guide
- BigFix® Remote Control V9.1.4 On-demand Target Guide
  Use BigFix® Remote Control to start remote control sessions over the internet with targets that do not have the target software installed.
- Remote Control V9.1.4 Readme file

Protocol configuration after a server upgrade

When you upgrade by using the server installer program and select to keep existing properties, you must configure properties after installation if you change your protocol selection.

Note: From V9.1.3, HTTPS is enabled by default. If you do not keep existing properties during the upgrade and you clear the Force targets to use HTTPS option, you must configure properties after installation. For more information, see Enabling HTTP access.

Changing from HTTPS to HTTP

Your previous server installation is configured to use HTTPS and you clear Force targets to use HTTPS during the upgrade. To access and log on to the server UI by using HTTP, you must also complete the following steps after the upgrade.

Edit the trc.properties file and set enforce.secure.alllogon to false.
Edit the following file, where [INSTALLDIR] is the BigFix® Remote Control server installation directory.

Windows™ systems

[INSTALLDIR]\wlp\usr\server\trcserver\cookie.xml

Linux™ systems

[INSTALLDIR]/wlp/usr/server/trcserver/cookie.xml
Set <httpSession cookieSecure="false"/> and save the file.
Restart the server service.

Changing from HTTP to HTTPS

Your previous server installation is configured to use HTTP and you select the Force targets to use HTTPS option during the upgrade. To access and log on to the server UI by using HTTPS, you must also complete the following steps after the upgrade.

Edit the trc.properties file and set enforce.secure.web.access, enforce.secure.weblogon, and enforce.secure.alllogon to true.
Edit the following file, where [INSTALLDIR] is the BigFix® Remote Control server installation directory.

Windows™ systems

[INSTALLDIR]\wlp\usr\server\trcserver\cookie.xml

Linux™ systems

[INSTALLDIR]/wlp/usr/server/trcserver/cookie.xml
Set <httpSession cookieSecure="true"/> and save the file.
Restart the server service.