Home
Server Automation
Server Automation provides powerful automation. You can use it to sequence automation actions in steps across multiple endpoints.
Server Automation content
Server Automation provides content that you can use to automate processes and software deployment.
Server Automation Remote Connector
BigFix Remote Connector module replaces the existing RXA module. When the Remote Connector is installed on a machine, the machine can act as an intermediary to execute BigFix functionality such as executing commands on or transferring files to a remote target machine, even if BigFix agent is not installed in that target machine. For example, Linux embedded targets. You can use Server Automation content to install Remote Connector on a system on which the BigFix agent is installed.
Installing Remote Connector
BigFix Remote Connector module replaces the existing RXA module. You can install Remote Connector on BigFix version 9.5 onwards.

Server Automation
Server Automation provides powerful automation. You can use it to sequence automation actions in steps across multiple endpoints.
- Overview
  BigFix Lifecycle Server Automation provides you with the capability to automate provisioning workflows. You can automate a sequence of Fixlets, Tasks, and Baselines across different endpoints, such as servers or computers. Server Automation exploits the agility and scalability of BigFix to deliver powerful functionality in a lean and efficient manner, with minimal impact on your network.
- Automation
  BigFix Lifecycle Server Automation provides you with technology to sequence actions, such as the deployment of Fixlets, across multiple endpoints. To sequence automation, you create an Automation Plan. Your Automation Plan contains all of the actions for your end-to-end automation sequence.
- Virtualization
  Virtualization is a software technology that allows multiple operating systems to run on the same host computer at the same time. Additional uses of virtualization include the quick creation of new systems for testing, training, and demonstration. Using virtualized computers saves the cost of hardware, management, and administration of the server infrastructure.
- Configuring your system
  This section describes how the BigFix architecture is relevant for Server Automation. It also describes how Server Automation can affect BigFix performance.
- Sample Automation Plans
  Server Automation is shipped with a number of sample Automation Plans that you can run out of the box. To run these Automation Plans out of the box, ensure that the Fixlets contained in them are available. Typically, you would substitute some of the Fixlets contained in these samples with particular Fixlets that you want to run. Use the information in each of the following sections to find out more about each of the sample plans.
- Server Automation content
  Server Automation provides content that you can use to automate processes and software deployment.
  - Advanced patching
    You can use Server Automation to complaete several advanced patching scenarios, for example to automate patching of virtual machine templates.
  - Patching Microsoft Windows® clusters
    You can use Server Automation to automate patching of Microsoft Windows® clusters. Server Automation contains preconfigured Fixlets that allow you to patch Microsoft Windows clusters.
  - Server Automation middleware content
    You can use the BigFix Lifecycle Server Automation middleware Tasks to automate the deployment of middleware applications. You can include these Tasks as steps in your Automation Plans.
  - OSD content
    BigFix Lifecycle Server Automation provides a number of Fixlets that allow you to deploy operating systems from within BigFix. These Fixlets connect to the BigFix Bare Metal Server server, which carries out the actual provisioning. You can include these Fixlets in your Automation Plans.
  - Server Automation Chef-Solo content
    You can use BigFix Lifecycle Server Automation Chef-Solo Tasks to automate the installation of Chef-Solo and download and run Chef-Solo cookbooks and recipes. The Chef-Solo installation and Chef-Solo cookbooks are downloaded from the Opscode Community web site.
  - Server Automation Remote Connector
    BigFix Remote Connector module replaces the existing RXA module. When the Remote Connector is installed on a machine, the machine can act as an intermediary to execute BigFix functionality such as executing commands on or transferring files to a remote target machine, even if BigFix agent is not installed in that target machine. For example, Linux embedded targets. You can use Server Automation content to install Remote Connector on a system on which the BigFix agent is installed.
    - Installing Remote Connector
      BigFix Remote Connector module replaces the existing RXA module. You can install Remote Connector on BigFix version 9.5 onwards.

Installing Remote Connector

BigFix Remote Connector module replaces the existing RXA module. You can install Remote Connector on BigFix version 9.5 onwards.

Before you begin

Ensure BigFix client is installed in the Windows machine in which you want to install Remote Connector.
Ensure SSH is installed and running in both client and remote target machines to install Remote Connector.
Do not modify the default SSH port.
Ensure that the remote targets that you are planning to run Remote Connector actions are capable of receiving Remote Connector commands.
Ensure that these remote targets are not secured so that no communication can be established. For example, the sshd daemon in the case of a Unix systems must be running and accessible.
For the current release, you must install Remote Connector on a Windows system.

About this task

Complete the following steps to install Remote Connector on a Microsoft® Windows® system:

Procedure

Open the BigFix console.
Search for Fixlet 168 Install BigFix Remote Connector Tool for SA v9.5.
Target the Microsoft® Windows® system on which you want to install Remote Connector.
Click OK to run the installation.

Results

Remote Connector is installed. After the installation is completed, the RC application folder is created, and you can review the contents of the installation in the BES Client\Applications\RC folder.

What to do next

Refer to Fixlet 167 Remote Connector Example for further information on how to use the Remote Connector APIs to establish connection with the remote target machine and execute commands.

Uninstalling Remote Connector

About this task

To uninstall Remote Connector, run the Fixlet 169 Uninstall Remote Connector Tool for SA v9.5.