Welcome
Remote Control
BigFix Remote Control application helps to communicate between different components, clients, and endpoints within BigFix environment.
BigFix Remote Control Controller Users Guide
Use remote control commands from the command line
You can install tools that you can use to start a remote control session from the command line. You can also use the tools to run a command on a target and see the output of the command on your computer.
Running commands on the target from the command line
Use the wrcmdpcr command to connect to a target and run a non-interactive command-line command.

BigFix Documentation Homepage
BigFix 11 Lifecycle Documentation
Welcome to the BigFix Lifecycle documentation, where you can find information about how to install, maintain, and use BigFix Lifecycle.
BigFix Platform
BigFix Query
Lifecycle overview
BigFix Lifecycle is single-agent, single-console technology that provides near real-time visibility into the state of endpoints.
Lifecycle guides in PDF format
Following is a list of links to the BigFix Lifecycle guides in PDF format:
Software Distribution
Use the BigFix Software Distribution applications to deploy software to endpoints across your network from a single location. Maintain control and visibility into software delivery and installation. Device owners can use the Self Service Application to manage software and other BigFix actions that are deployed to them as offers.
OS Deployment
BigFix OS Deployment, which is part of the BigFix Lifecycle Management suite, provides a consolidated, comprehensive solution to quickly deploy new workstations and servers throughout a network from a single, centralized location. This solution saves time and money, enforces a standardized and approved image, and reduces risks associated with non-compliant or insecure configurations.
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
  - The BigFix Remote Control server interface
  - Remote control sessions
    Use remote control sessions to establish a connection to a computer in your environment to observe or actively control the computer remotely. In the session the controller user's keyboard and mouse become the primary keyboard and mouse for the remote system. Functions such as chat, guidance, reboot, and file transfer are some of the options available for use in a remote control session.
  - Using the controller interface as a controller user
  - Use remote control commands from the command line
    You can install tools that you can use to start a remote control session from the command line. You can also use the tools to run a command on a target and see the output of the command on your computer.
    - Starting a remote control session from the command line
      You can start a session with a target by running the wrc command.
    - Running commands on the target from the command line
      Use the wrcmdpcr command to connect to a target and run a non-interactive command-line command.
      - Examples of usage
    - Error messages for the wrc and wrcmdpcr commands
  - Configuring global controller properties
    Edit the trc_controller.cfg file to create and configure global controller properties. The properties are used by the Remote Control controller component during a peer to peer remote control session. The property values are the same for every user who runs the controller.
  - Auditing
    Remote control session events are saved for auditing purposes if the AuditToSystem policy is enabled for the session.
  - Ensuring that current data is reported
  - Error messages
    In most of cases, connectivity problems that are experienced in Remote Control are related to the surrounding network infrastructure. Error messages in Remote Control help to pin point these problems.
  - Session resilience for sessions that are connected by using a broker
    During a remote control session that is connected by using a broker, when connection failure is detected, reconnection to the session is attempted automatically. The controller user and target user are informed of what is happening with the session connection through various message windows.
  - Smart card status messages
    The following status messages can be displayed on the controller during a remote control session in which smart card authentication is enabled. A Hide button is displayed on some of the message windows. Click Hide to minimize the message window and continue in the session.
  - Keyboard shortcuts for the BigFix® Remote Control Target for macOS
    During a remote control session with a BigFix® Remote Control Target for macOS, you can inject the following keyboard shortcuts. The shortcuts are displayed in the Perform Action in Target menu in the controller UI.
  - Override proxy
    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
- 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.
- Remote Control V10 Readme
Power Management
Use Power Management to control, monitor, and manage conservation policies in your deployment.
Server Automation
Server Automation provides powerful automation. You can use it to sequence automation actions in steps across multiple endpoints.
Profile Management
Profile Management is a WebUI-based feature of BigFix Lifecycle. It provides Security Administrators the capability to define and deploy security policies to Windows 10 and macOS devices.
CVE Search dashboard
BigFix CVE Search dashboard and Web Report are available as part of the CyberFOCUS site.
BigFix Remediate
BigFix MCM

Running commands on the target from the command line

Use the wrcmdpcr command to connect to a target and run a non-interactive command-line command.

About this task

You can specify the command that you want to run on the target, and the output from that command is displayed on the computer that the command is started from. This command can be useful for debugging a target when you do not have access to the BigFix® Remote Control Server user interface.

To start a command on a target, complete the following steps:

Procedure

At a command prompt, go to the directory where you installed the command-line tools.
Type in the following command
```
wrcmdpcr user:password Rctarget command [argument ...]
```
user:password

Use to specify a valid user ID and password that you would use to log on to the BigFix® Remote Control Server.

Rctarget

Use to specify the computer name or the IP address of the target that you want to connect to and run a command on. It has the following syntax:
@Endpoint:<computername or ipaddress>

command
Use to specify a command that runs from the command line. For commands that are built into the operating system's shell and do not have a binary executable file. For example, dir or tree in a Windows™ operating system. In a Linux™ operating system, cd or echo. You must also add the command shell command.

Windows™ systems

You must type cmd /c before the command. For more information, seeExamples of usage.
For example, cmd /c dir

Linux™ systems

You must type sh -c before the command. For more information, see Examples of usage.
Note:

The command that you run must be specific to the operating system that is running on the target. If you are entering the command from a Windows™ computer to a target that has a Linux™ operating system installed, you must specify the Linux™ command.

If you are entering the command from a Linux™ computer to a target that has a Windows™ operating system installed and you are using path names in the argument, you must use a double backslash in the argument. For example, \\windows.

The command that you want to run must be in the PATH statement of the target, otherwise the full path to the command must be used.
argument

Use to provide arguments for the command that you want to run on the target.