Welcome
Server Automation
Server Automation provides powerful automation. You can use it to sequence automation actions in steps across multiple endpoints.
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.
Sample plan: Server patching
This sample Automation Plan completes a scenario for server patching. All sample plans are read-only. To use a sample plan, you must copy it, re-name it, and then update the placeholder Fixlets with Fixlets, Tasks, or Baselines as per your requirements.

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.
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.
- 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.
  - Sample plan: Server Patching (Client-Server sample)
    BigFix Lifecycle Server Automation provides a sample content Automation Plan. This sample Automation Plan contains Tasks to stop services on client and server endpoints, apply a patch to the server endpoint, and then restart the client and server services. All sample plans are read-only. To use a sample plan, you must copy it, re-name it, and then update the placeholder Fixlets with Fixlets, Tasks, or Baselines as per your requirements.
  - Sample plan: Physical Server Build
    This sample Automation Plan completes a simple end-to-end physical server build. You must have BigFix Bare Metal Server set up and integrated with BigFix to run this Automation Plan. The first step in the plan deploys an operating system to one or more computers. The second step creates a baseline patches the operating system on the virtual machine created in the first step. The third step installs Microsoft SQL Server 2008 Enterprise Server Edition on the computer or computers that you created in the first step. The final step patches Microsoft SQL Server 2008 Enterprise Server Edition that is installed in step 3. All sample plans are read-only. To use a sample plan, you must copy it, re-name it, and then update the placeholder Fixlets with Fixlets, Tasks, or Baselines as per your requirements.
  - Sample plan: Faster Virtual Server Build (with baseline)
    This sample Automation Plan completes a simple end-to-end virtual server build. This sample plan performs exactly the same actions as that of Lifecycle/ServerAutomation/SAUsersGuide/Server_Automation_sample_plans/sa_ootbvirtualserverbuild_baseline.html. However, in this sample automation plan, a baseline is used as a (regular) step instead of multi-step fixlets. This helps you to execute the plan in a relatively shorter time compared to the plan with multi-step fixlets. Under the take-action and Default dialog box, the baseline step and its component fixlets are represented in parent-child structure to provide parameter support for each component. This feature only works when baseline is added as a regular step and not as a failure-step.
  - Sample plan: Server patching
    This sample Automation Plan completes a scenario for server patching. All sample plans are read-only. To use a sample plan, you must copy it, re-name it, and then update the placeholder Fixlets with Fixlets, Tasks, or Baselines as per your requirements.
  - Sample plan: Microsoft® Windows® 2008 Release 2 to Microsoft® Windows® 2012 Release 2 Cluster - OS patching (Non-Baseline from Site Sample)
    This sample Automation Plan provides you with a template to automate patching of clusters with Microsoft® Windows® Servers 2008 Release 2 and later operating systems. There are two phases in this plan, in the first phase, which runs from steps 1 to 4, you patch the first node or group of nodes in the cluster. For each of the steps in this phase, you target the first node or group of nodes. While these nodes are being patched, the second nodes remain operational. The second phase of the plan is a repeat of the first phase, except that you are targeting the second node or group of nodes in the cluster. The cluster remains operational throughout the patching process. All sample plans are read-only. To use a sample plan, you must copy it, re-name it, and then update the placeholder Fixlets with Fixlets, Tasks, or Baselines as per your requirements.
  - Sample plan: Microsoft® Windows® 2008 Release 2 to Microsoft® Windows® 2012 Release 2 Cluster - OS patching
    This sample automation plan provides a template for you to automate cluster patching for Microsoft® Windows® 2008-2012 operating systems. You can use this sample plan as a template to patch the nodes in a Microsoft Windows cluster. This plan is designed for use where you configure the Pending Restart setting in the Server Automation user interface to automatically restart the endpoints. See the Settings tab of the plan in Server Automation and set the Pending Restart option to Continue to next step. All sample plans are read-only. To use a sample plan, you must copy it, re-name it, and then update the placeholder Fixlets with Fixlets, Tasks, or Baselines as per your requirements.
  - Sample plan: Microsoft Exchange 2007 Cluster - OS patching
    This sample plan shows how you can patch Microsoft Exchange 2007 SP1 on a Microsoft Windows cluster. Use this plan as a template for patching Exchange 2007 SP1 on Windows clusters. This plan patches the operating systems by running Baselines from a site. Before running the plan, add the Baselines that you want to use to patch the operating systems to a custom site. When you are running the plan, you then select that site to patch the Exchange mailbox server. All sample plans are read-only. To use a sample plan, you must copy it, re-name it.
  - Install Oracle Database 11g on Linux
    This sample automation plan provides a template for you to automate the deployment of Oracle Database 11g Enterprise Edition on Linux. You can use this sample plan as a template by copying it and then making changes to the copy as required. All sample plans are read-only. To use a sample plan, you must copy it, re-name it, and then update the placeholder Fixlets with Fixlets, Tasks, or Baselines as per your requirements.
  - Sample plan: Microsoft Hyper-V Servers Cluster - OS patching
    This sample automation plan provides a template for you to automate cluster patching of Hyper-V operating systems on Windows 2008-2012 and contains a Fixlet to automatically reboot the targets endpoints. You can use this sample plan as a template if the patch Fixlet that you are including to patch the nodes in the cluster requires the endpoints to be restarted. The sample plan uses the Baselines from a site feature to patch the operating systems. All sample plans are read-only. To use a sample plan, you must copy it, re-name it.
  - Sample plan: Microsoft Exchange 2010/2013 Cluster - OS patching
    This sample automation plan provides a template for you to automate patching of operating systems in Microsoft Exchange 2010 and 2013 clusters. This sample plan uses the Baselines from a site feature to patch the operating systems. All sample plans are read-only. To use a sample plan, you must copy it, re-name it, and then update the placeholder Fixlets with Fixlets, Tasks, or Baselines as per your requirements.
  - Sample plan for Exchange 2010 and 2013 and Windows Server 2008
    This sample automation plan provides a template for you to automate patching of the operating systems for a Microsoft Exchange 2010 and 2013 and Windows Server 2008 Release 2 cluster. It is a parallel plan, where the patching of the clustered Exchange 2010 and 2013 servers are patched concurrently with the Windows Server 2008 cluster. This sample plan uses the Baselines from a site feature to complete the patching. All sample plans are read-only. To use a sample plan, you must copy it, re-name it, and then update the placeholder Fixlets with Fixlets, Tasks, or Baselines as per your requirements.
  - Sample plan: Dynamically Run All Baselines from a Site and Restart the Endpoints
    This sample Automation Plan runs all of the Baselines contained in a site against a set of endpoints that you target. After that step has completed, the second step in the automation plan restarts all of the endpoints targeted in the first step. Add the Baselines that you want to execute to a custom site before running this plan. All sample plans are read-only. To use a sample plan, you must copy, re-name, and save it and then use the copy.
  - Sample plan: Microsoft® Windows® 2008 Cluster - OS patching
    This sample Automation Plan automates Microsoft® Windows® cluster patching. As well as managing the cluster as it is patched, the automation flow runs all of the Baselines contained is a site against the nodes in the cluster. Add the Baselines to a custom site before running this plan. All sample plans are read-only. To use a sample plan, you must copy it, re-name it, and then update the placeholder Fixlets with Fixlets, Tasks, or Baselines as per your requirements.
  - Sample plan: Microsoft® SQL Server 2008 Release 2 Cluster - Middleware patching
    This sample plan automates patching of Microsoft® SQL Server 2008 Release 2 in a cluster. The plan is designed to automate Microsoft SQL Server 2008 Release 2 patching for a two node cluster. The first step and last step in the plan are common to each of the nodes in the cluster. For these steps, you must target both nodes in the cluster. For steps 2 to 8, target the first node in the cluster, replacing the placeholder patching Fixlet with a Fixlet,Task, or Baseline to patch Microsoft SQL Server. For steps 9 to 15, target the second node in the cluster, replacing the placeholder Fixlet with a patching Fixlet, Task or Baseline to patch the Microsoft SQL Server. All sample plans are read-only. To use a sample plan, you must copy it, re-name it, and then update the placeholder Fixlets with Fixlets, Tasks, or Baselines as per your requirements.
  - Sample Plan: Microsoft® SQL Server 2012 and later Cluster - Middleware patching
    This sample plan automates patching of Microsoft® SQL Server 2012 and Microsoft SQL Server 2014 clusters. The plan is designed to automate Microsoft SQL Server 2012 or Microsoft SQL Server 2014 patching for a two node cluster. The automation is executed in two phases, one for each node in the cluster. For steps 1 to 7, the first node in the cluster is patched. These steps are then replicated in steps 8 to 14 on the second node in the cluster. At all times during the patching process the cluster remains operational and available. For each phase in the automation, replace the placeholder steps, replacing them with a Fixlet, Task or Baseline to patch Microsoft SQL Server. All sample plans are read-only. To use a sample plan, you must copy it, re-name it, and then update the placeholder Fixlets with Fixlets, Tasks, or Baselines as per your requirements.
  - Sample Plan: IBM® WebSphere® Application Server Cluster - OS patching
    This sample plan automates operating system patching for WebSphere® Application Server 8.0, 8.5, or 8.5.5 nodes in a Microsoft Windows cluster. The plan is designed to automate operating system patching for three WebSphere Application Server nodes in a cluster. The automation is executed in three phases, one for each node. The first step sets the parameters for all other steps in the plan. For steps 2 to 5, the first node is patched. These steps are then replicated in steps 6 to 9 on the second node and in steps 10 to 13 for the third node. For each phase in the automation, replace the placeholder steps, replacing them with a Fixlet, Task or Baseline to patch the operating system. All sample plans are read-only. To use a sample plan, you must copy it, re-name it, and then update the placeholder Fixlets with Fixlets, Tasks, or Baselines as per your requirements.
  - Sample Plan: IBM® WebSphere® Application Server Cluster - Middleware patching
    This sample plan automates middleware patching for WebSphere® Application Server 8.0, 8.5, or 8.5.5 nodes in a Microsoft Windows cluster. The plan is designed to automate middleware patching WebSphere Application Server in a three node cluster. The automation is executed in three phases, one for each node. The first step in the plan sets the parameters for all other steps in the plan. For steps 2 to 5, the first node is patched. These steps are then replicated in steps 6 to 9 on the second node and in steps 10 to 13 for the third node. For each phase in the automation, replace the placeholder steps, replacing them with a Fixlet, Task or Baseline to patch the operating system. All sample plans are read-only. To use a sample plan, you must copy it, re-name it, and then update the placeholder Fixlets with Fixlets, Tasks, or Baselines as per your requirements.
  - Sample Plan: Microsoft Exchange 2007 Mailbox Cluster - Middleware Patching
    This sample plan automates patching of Microsoft Exchange 2007 middleware in a mailbox cluster. The plan is designed to automate Microsoft Exchange 2007 patching in a two node cluster. The automation is executed in two phases, one for each node in the cluster. For steps 1 to 7, the first node in the cluster is patched. These steps are then replicated in steps 8 to 14 on the second node in the cluster. At all times during the patching process the cluster remains operational and available. For each phase in the automation, replace the placeholder steps, replacing them with a Fixlet, Task or Baseline to patch Microsoft Exchange. All sample plans are read-only. To use a sample plan, you must copy it, re-name it, and then update the placeholder Fixlets with Fixlets, Tasks, or Baselines as per your requirements.
  - Sample Plan: Microsoft Exchange 2010 or 2013 DAG Cluster - Middleware Patching
    This sample plan automates patching of Microsoft Exchange 2010 or 2013 middleware in a cluster. The plan is designed to automate Microsoft Exchange patching in a two node cluster. The automation is executed in two phases, one for each node in the cluster. For steps 1 to 5, the first node in the cluster is patched. These steps are then replicated in steps 6 to 10 on the second node. Optionally, if you have a File Share Witness configured, you can add Task 134 Check File Share Witness status on a Microsoft Windows cluster to check the status of the File Share Witness. For each phase in the automation, replace the placeholder steps, replacing them with a Fixlet, Task or Baseline to patch Microsoft Exchange. All sample plans are read-only. To use a sample plan, you must copy it, re-name it, and then update the placeholder Fixlets with Fixlets, Tasks, or Baselines for your patching requirements.
  - Sample Plan: IBM® WebSphere® Application Server Standalone - OS patching
    This sample plan automates operating system patching for stand-alone WebSphere® Application Server 8.0, 8.5, or 8.5.5. nodes. The plan is designed to automate operating system patching for two stand-alone WebSphere Application Server nodes. The automation is executed in two phases, one for each node. For steps 1 to 4, the first node is patched. These steps are then replicated in steps 5 to 8 on the second node. For each phase in the automation, replace the placeholder steps, replacing them with a Fixlet, Task or Baseline to patch the operating system. All sample plans are read-only. To use a sample plan, you must copy it, re-name it, and then update the placeholder Fixlets with Fixlets, Tasks, or Baselines as per your requirements.
  - Sample Plan: IBM® WebSphere® Application Server standalone - Middleware patching
    This sample plan automates patching of WebSphere® Application Server v8.0, 8.5, or 8.5.5 for two stand-alone nodes. The automation is executed in two phases, one for each node. For steps 1 to 4, the first node is patched. These steps are then replicated in steps 5 to 8 on the second node. For each phase in the automation, replace the placeholder steps, replacing them with a Fixlet, Task or Baseline to patch WebSphere Application Server. All sample plans are read-only. To use a sample plan, you must copy it, re-name it, and then update the placeholder Fixlets with Fixlets, Tasks, or Baselines for your patching requirements.
  - Sample Plan: Patching a VMware Windows Template
    This sample plan automates patching of VMware templates on Microsoft® Windows® platforms. The automation process works by first creating a virtual machine from the template that you want to patch, then patching the newly created virtual machine, removing the BigFix client identity data, and then converting the virtual machine back to a VMware template. All sample plans are read-only. To use a sample plan, you must copy it, rename it, and then update the placeholder Fixlets with Fixlets, Tasks, or Baselines as per your requirements.
  - Sample Plan: Patching a VMware Linux® Template
    This sample plan automates patching of a VMware template on Linux® systems. The automation process works by first creating a virtual machine from the template that you want to patch, then patching the newly created virtual machine, removing the BigFix client identity data, and then converting the virtual machine to a VMware template. All sample plans are read-only. To use a sample plan, you must copy it, re-name it, and then update the placeholder Fixlet with Fixlets, Task, or Baselines as per your requirements.
- Server Automation content
  Server Automation provides content that you can use to automate processes and software deployment.
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

Sample plan: Server patching

This sample Automation Plan completes a scenario for server patching. All sample plans are read-only. To use a sample plan, you must copy it, re-name it, and then update the placeholder Fixlets with Fixlets, Tasks, or Baselines as per your requirements.

About this task

This Automation Plan uses some sample Fixlets that will not suit the requirements for your particular server patching scenario. Replace these Fixlets with relevant Fixlets that you want to run on your endpoints to complete server patching in your environment.

Complete the following steps to run the sample Automation Plan.

Procedure

Open theServer Automation domain.
From the navigation tree in the Domain Panel, click Automation Plans.
In the Automation Plans dashboard, enter 103 and press Enter. This is the ID of the sample Automation Plan.
Select the Automation Plan from the list of Automation Plans.
Click Copy to copy the Automation Plan, enter a name and then save the copy that you have just created.

To run the copied Automation Plan, click Take Action. The following table shows the parameters and targets that you need to input for each step in the sample Automation Plan.

Table 1. Plan steps and parameters and targets
Step	Description	Parameters and targets
Step 1 Stop Service (222)	This step stops the service. For example, the DB2® client service on the clients.	Parameter: Client service name, for example, `db2_client`. Targets: Client endpoints.
Step 2 Stop Service (222)	This step stops the server service. For example, the DB2® server service on the DB2® server.	Parameter: Server service name, for example, `db2_server`. Targets: DB2® server.
Step 3 Placeholder for OS or Application Patches - (REPLACE ME)	Remove this Fixlet and include an operating system patch that suits your patching requirements. Depending on the Fixlet that you include for this step, you might or might not need to restart the endpoints targeted in this step in step 4.	Parameter: Any parameters required by the OS patch Fixlet that you include. Targets: DB2® server.
Step 4 Restart Endpoint (94)	This step restarts the server endpoint.	Parameter: No parameter required. Targets: DB2® server.
Step 5 Start Service (221)	This step starts the client server, for example, the DB2® client server on the clients.	Parameter: Client service name, for example, `db2_client`. Targets: Client endpoints.

Click OK to run the Automation Plan.