Starting version 8.9.03, BMC Server Automation is renamed to TrueSight Server Automation. This space contains information about BMC Server Automation 8.9.02 and previous versions. For TrueSight Server Automation 8.9.03 and later releases, see TrueSight Server Automation 8.9.

BSA 8.9.02 Rolling Update 1 (RU1)

This topic contains instructions for downloading and installing Rolling Update 1 on BMC Server Automation (BSA) 8.9 SP2. A Rolling Update provides product fixes by updating specific files in existing BSA components, thus delivering the latest product fixes without having to upgrade the entire product. Rolling Updates are installed on top of a service pack without affecting the product version or build number.


The Rolling Updates discussed in this page can only be installed on BMC Server Automation 8.9 SP2. Do not install the updates on any other release of BMC Server Automation.

Rolling Updates available for 8.9 SP2

The following table lists the Rolling Updates provided for BMC Server Automation 8.9 SP1 along with their release dates.

Base ReleaseBuild numberRolling UpdateRelease date

Service Pack 2 for BMC Server Automation 8.9

Rolling Update (RU) 1March 16, 2018

Preparing for installation

Before you begin installing the Rolling Update, check the following prerequisite:

  • BMC recommends that you to go through the list of product fixes mentioned here.

Download the latest available Rolling Update

You can access and download the installation files for RU 1 from the following FTP location:


You must be logged on to this page to view the FTP URL.

Verify the downloaded content by using the following check sums:

Linux Application Server files

File Name


Windows Application Server files

File Path and Name


Download and extract the required zip packages on your Application Servers as described below:

  • Downloading the files on your Application Servers
    1. Depending on the type of operating system running on your Application Servers, download either of the following zip packages from the FTP location.





    2. Copy and extract the zip package to temporary folder (for example /tmp on Linux or C:\temp on Windows) on your Application Servers.

Step 1: Installing on all Application Servers in your environment

Perform the following steps on all Application Servers in your BMC Server Automation environment:

  1. Log on to your Application Server with a user having root or Administrator privileges.

  2. Navigate to the temporary location where you have extracted the installation files, as described in this step.
  3. Execute the rollingUpdateInstaller.nsh script using the following command in cmd or shell terminal:
    nsh rollingUpdateInstaller.nsh


    The Application Server will restart twice for the installation to complete successfully.

  4. The following message is displayed:
    #### Rolling Updatation Completed Successfully ####
    Repeat the above steps on all other Application Servers in your environment.


    Wait for the installation process to complete successfully on one Application Server, before beginning the installation process on another Application Server. Running installations on different Application Servers simultaneously will result in errors during installation.

  5. Verify whether all Application Servers have been updated successfully by using both the following options: 

    1. By checking the Rolling Update version in the RU_Version file at the following application server location:

      Microsoft WindowsC:\Program Files\BMC Software\BladeLogic\RU_Version
    2. By running the following SQL query in your database:

      ID RU_VERSION      STATUS  APPSERVER_NAME                              EXECUTION_TIME
      ---------- ---------------- -----------------------------------------------------------------
      1    success bsaappserverhost01                    09-MAR-18 PM

Product fixes

BSA Rolling Updates are cumulative type of updates. When you install a particular Rolling Update, product fixes from earlier updates are also added to the product. For example, when you install RU 3, all product fixes added in RU 1 and RU 2 will also be installed along with RU 3 product fixes. See the below table for a list of product fixes and the Rolling Update that they were corrected in.

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

Defect IDCategoryDescriptionCorrected in
DRBLG-111754Application Server

When you run multiple Update Server Property jobs with same set of targets in parallel, this leads to database deadlock.

DRBLG-112540Application Server

When you use json as input parameter in POST method, you receive the following error message:

Could not parse operation arguments, the json input does not match the schema Unexpected token (END_OBJECT), expected FIELD_NAME: missing property '@class' that is to contain type id 

QM002360590Application Server

For Agent Installer Jobs, you got connection timeout error message instead of connection lost message because of hard coded list.

QM002362321Application Server

If there is a heavy load on the application server, NSH script job stops responding and still shows in running state even after JOB_TIMEOUT is reached.

QM002369864Application ServerThe License Utility BLCLI command does not provide full data.RU1
QM002371390Application ServerBLCLI server does not handle inputs that contains Microsoft windows EOL characters.RU1
QM002371490Application Server

The I/O releated error messages in the BLCLI server are confusing.

QM002373636Application Server

When you open a Solaris patch, Is Reboot Required field is not set as expected.

QM002381667Application Server

In SUSE, zypper-based analysis is not populating the count of installed rpms (rpm -qa) in BL_PATCH_RES_DEVICE_CNT table as expected.

QM002383835Application Server

When patching multiple servers simultaneously, you receive the following error message on BMC Server Automation servers:

A depot object of the same type with the name 'X' already exists in this folder.

QM002385556Application Server

In BMC Server Automation 8.9.00, Compliance Run Result from RCP export is significantly slower than BLCLI export.

QM002385582Application Server

When you try to create an empty NSH script for the second time, you receive the following error message: No such file or directory



Was this page helpful? Yes No Submitting... Thank you


  1. Barry Mcquillan

    This should not be located here! This information should be listed under planning and installing sections.

    This functionality should be "mentioned" in the enhancements and updates section. But they MUST be listed under the following section: Installing->Download files Installing->Using the Unified Installer (or in a separate section like: Installing->Post Unified Installer steps.

    These are required steps for for completing a successful installation.

    May 17, 2018 06:50
    1. Ranu Ganguly

      Hi Barry,

      Let me check and revert.

      Thanks and regards,


      May 21, 2018 12:17