Unsupported content


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.



BMC Software is alerting customers who use BMC Server Automation for Windows Patching that action must be taken before December, 2018 to ensure continued functioning of Windows Patching within the BMC Server Automation product beyond that date. This action includes a requirement to upgrade the RSCD Agent on all Windows servers which are targets for BMC Server Automation windows patch analysis.

This topic provides information related to upgrading BMC Server Automation. It includes the following sections:

Latest update

The latest upgrade version is Patch 5 for Service Pack 1 of BMC Server Automation version 8.5.00. The fixes included in this patch are listed in Known and corrected issues. For detailed upgrade instructions, see the following:

Build information

The following table lists information for the most recent BMC Server Automation version 8.5 build.


Build number

EPD version number

Release date

Patch 5 for Service Pack 23, 2015
Patch 4 for Service Pack 5, 2015
Patch 3 for Service Pack 10, 2014
Patch 2 for Service Pack 15, 2014
Patch 1 for Service Pack 2, 2014
Service Pack 7, 2014
Patch 2 for version 6, 2014
Patch 1 for version 11, 2014

Base version 8.5


February 25, 2014

Upgrade reference information

The following topics in this section provide information about upgrading the individual components of the BMC Server Automation system.

Preparing for upgrade 

Review the supported upgrade paths and upgrade considerations and perform the preliminary upgrade steps, such as shutting down the BMC Server Automation environment and backing up the installation directories for all Application Servers and PXE servers.

Upgrading the Application Server on Windows

Upgrading product components on Linux and UNIX

Do not restart the Application Server until you complete the database migration. Additional upgrades that occur at this point depend on where the Application Server resides:

  • On a Microsoft Windows computer, an upgrade of the Application Server also upgrades the Network Shell. 
  • On a Linux or UNIX computer, an upgrade of the Application Server also upgrades all components that were installed as part of the earlier installation of the Application Server. These components can include the Network Shell, the RSCD agent, and the PXE server.
Migrating core BMC Server Automation data

Run the Data Migration Manager using the version 8.5 external files to upgrade your Oracle or SQL Server database to version 8.5. 

Note: This step is not necessary for an upgrade from 8.5.00 to a later 8.5 service pack or patch level.

Running the SQL update scripts.If upgrading to an 8.5.x service pack or patch (later than 8.5.00), run a set of SQL Update scripts to upgrade the BMC Server Automation database to the service pack level or patch level compatible with the Application Server.
Performing post-migration updates to rules and policies 

Run the postmigration (.exe or .sh) file to update BLPackages that refer to old Group Policy Object (GPO) assets or to migrate rules.

Upgrading the BMC Server Automation ConsoleUpgrade at least one BMC Server Automation Console.

Upgrading the provisioning system

Upgrading a PXE server on Windows

Upgrading a PXE server on Linux or UNIX

If you have upgraded the provisioning server (the Application Server enabled for provisioning), upgrade the components that BMC Server Automation uses in provisioning operating systems to bare metal machines.

Upgrading the Network Shell

Upgrading RSCD agents

Upgrading the file server 

Upgrade the other BMC Server Automation Application Servers, consoles, RSCD agents, and other components in your enterprise (including on any file servers or virtual servers). 

Note: If the BMC Server Automation file server resides on a different computer from the Application Server, upgrade the RSCD agent on the computer on which file server resides. The file server and the database must be at the same version before you run BMC Server Automation.

Upgrading custom configuration objects

Upgrade any custom configuration objects that you have created and distributed. You can perform this step at any time after the upgrade.

Upgrading to a new release can potentially create mismatches between the version of a custom configuration object, an agent, and any model objects that reference custom configuration objects. For more information, see Upgrading custom configuration objects.
Installing Compliance Content add-onsIf you are using Compliance Content, perform an over-the-top installation of the new Compliance Content add-ons. You can perform this step at any time after the upgrade.

Related Knowledge Articles

AMIGO Upgrade Program Introduction for BMC Server Automation environments (Knowledge Article ID: 000011572)

The AMIGO Upgrade Program is designed to assist you with the upgrade of BMC Server Automation environments. The process begins when you open an AMIGO Starter Issue and are provided with this document which contains a brief description of the process, a checklist of environmental information to capture and consider when planning your upgrade and links to other documents and manuals which will be helpful in performing your upgrade. The end result is for you to create a written Upgrade Plan which has been reviewed by BMC Support in advance of your upgrade.

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