Home
Remote Control
BigFix Remote Control application helps to communicate between different components, clients, and endpoints within BigFix environment.
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.
Troubleshooting
When the on-demand target is installed, a log file is created in the target user's home directory. This file can be used for debugging purposes to examine any errors during the installation of the target or during a remote control session.
Errors when you are using the Java applet method of installation

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.
- 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.
  - Configuring the landing page URL
    Remote Control provides a default web page that a target user can access to temporarily install the target software. The URL for the web page is http://trcserver/trc/ondemand/index.jsp. The variable trcserver is the host name or IP address of your Remote Control server. The default web page is provided when you have the Remote Control server installed. You can also configure server properties to provide a URL that the target user can access. The defined URL is displayed to the controller user when they start a broker remote control session.
  - Configuring custom fields
    You can add extra input fields to the default web page that is used during the process of downloading and temporarily installing the target software.
  - Creating a custom landing page
    You can customize the web page that is used to start the process to download and temporarily install the target software. The web page can be integrated into your own company website.
  - On-demand target portal access for internet users
    A reverse proxy, in a DMZ, can be configured to provide access for Internet users to the on-demand portal that is on the Remote Control server in the intranet. The reverse proxy must not allow access to other sections of the Remote Control server, but only to the on-demand portal.
  - Setting session permissions
    A target that participates in a broker session receives session policies from the server. These policies are resolved from the user and target group permission links that the user and target in the session are associated with. An on-demand target participates in broker remote control sessions. However, it is not registered with the server and does not belong to regular target groups. An unregistered target can also be a computer that you install the target software on, configure it with correct broker settings, and the target property Managed set to no. You can define session permissions for unregistered targets by using the Set Permissions for Unregistered Targets function.
  - Session policies for unregistered targets
    The set of session policies available for unregistered targets is divided into two sections. The core policies cater for remote support actions during a session. The extended policies cater for the session administration actions during a session. The core policies are always visible on the Set Permissions for Unregistered Targets screen. Click Show in the More permissions section to set values for the extended policies.
  - Defining the temporary recording directory for a broker
    You can define the directory where session recordings are temporarily stored on the broker, by configuring broker properties.
  - On-demand target installation methods
    The on-demand target installation method is determined by properties in the ondemand.properties files and the browser that is used by the target user .
  - Starting a session with an on-demand target
    You can start a remote control session through the internet with a target that does not have the target software already installed.
  - Session limitations
    Some limitations might be in effect during a remote control session with an on-demand target.
  - Saving a session recording on the on-demand target
    As the user on an on-demand target you can save a recording of a remote control session on your computer. You can select to save the recording when you accept the session or start to record and save during the session.
  - Handing over a broker collaboration session
    If you are the master controller of a collaboration session, that involves a broker, you can pass full control of the session to another participant.
  - Ending a session
    When you end a session with an Remote Control on-demand target, all related files and directories are deleted.
  - Ending a collaboration session when you disconnect
    When you end a session in which collaboration is started, you can choose to stay in the session or disconnect from the session.
  - Saving the session log file
    You can save the trace log file that is created during a session with an Remote Control on-demand target.
  - Session history for unregistered targets
    After you participate in remote control sessions with on-demand targets, you can view the session history. Sessions that involved unregistered targets are listed in the All Session History report and My Session History report together with the registered target sessions. You can also view a list of the sessions that only involved unregistered targets.
  - Database table definitions
    Description and definition of the database tables that hold data for remote control sessions with on-demand targets. The SESSIONS_DATA table hold the data that is submitted from the default web page that is used by the target user. The SESSIONS table holds session data.
  - OnDemand properties file
    Edit the ondemand.properties file to create and configure properties for remote control sessions with on-demand targets.
  - Determine the installation method for the on-demand target
    The configuration of the on-demand installation method properties determines which installation method is used for the on-demand target.
  - Lite Web Portal
    Lite Web Portal enables you to start a Remote Control session with an On Demand Target without using a VPN, even when the controller and the target are over the Internet.
  - Troubleshooting
    When the on-demand target is installed, a log file is created in the target user's home directory. This file can be used for debugging purposes to examine any errors during the installation of the target or during a remote control session.
    - Errors when you are using the Java applet method of installation
    - Errors when you are using the ActiveX method of installation
    - On-demand target installation and loading status icons
      Status icons are displayed during the installation and loading of the on-demand target to indicate success or failure.
    - Error when you start On-demand Target on macOS
      After downloading the On-demand Target package, if you try to start the application, you might see the error “The application "BigFixRC-xxx" can't be opened”.
  - Frequently asked questions
- Remote Control V10 Readme

Errors when you are using the Java™ applet method of installation

When the on-demand target is installed by using the Java™ applet method, the following errors might be reported. The errors are displayed in the status window and are written also to the log file. The status window is displayed until the target user closes it. For more information about the Java™ applet installation, see Downloading the on-demand target by using the Java Applet.

Bad URL:{0}: When a malformed URL is entered by the target user. For example, Bad URL: htp://example.com/#123456.
Bad server response for {0}: Response code {1}: When an invalid URL is provided. For example, Bad server response for http://example.com/index.jsp?conncode=0000000:Response code: 404.
Unable to determine host architecture: The Java™ Applet is unable to determine whether the architecture of the target computer is 32-bit or 64-bit.
Error running {0} -c={1} -l={2}: When the Java™ Applet fails to start the on-demand launcher. For example, Error running /tmp/trc_odt-abc-123.exe -c=http://configurl -l=C:\Users\tgtuser\trc_odt_trace_20130510_131023.log
IO Error downloading from {0}: When a read or write error occurs while the ODL, or the configuration package is downloaded from the server. For example, IO Error downloading from http://configurl.
Unable to open the log file for writing: When the Java™ Applet is unable to create its debug log file.

Note: The Java™ Applet is built with Java™ version 1.5. Therefore, the target user must have a browser Java™ plug-in of version 1.5 or later for the Java™ applet to run correctly.