Walkthrough: Upgrading to version 8.9 for Microsoft Windows
If you are running BMC Server Automation version 8.6 or later, and are running 64-bit Windows platforms, you can use the unified product installer to upgrade to version 8.9.
The topic includes the following sections:
The video at right provides helpful tips on how to upgrade your BladeLogic Application Server running on Windows.
Review the supported upgrade paths information, available in the Supported upgrade paths section below.
If your BMC Server Automation environment includes BMC BladeLogic Decision Support for Server Automation, upgrade BMC BladeLogic Decision Support for Server Automation before upgrading BMC Server Automation. For more information, see the following topic in the Decision Support for Server Automation online technical documentation:UpgradingAs of BMC Server Automation 8.6 SP1, the task of running SQL Update scripts, which was necessary in the past for any upgrade to a BMC Server Automation patch or service pack, is no longer required during an upgrade. The database upgrade is now handled internally by the unified product installer, which was introduced in version 8.6.
Upgrading using the unified product installer
If you are not an experienced user, see the related topics listed in the table to review the required planning information for upgrading the product.
The unified product installer automatically upgrades the database, file server, Application Server, agents, PXE server and the TFTP server in your environment. If you manually enabled the BMC Server Automation Console Upgrade Service, the console is also automatically upgraded; otherwise, you must manually upgrade it. The checklist below walks you through the process of upgrading Windows and Linux environments using the unified product installer.
As of version 8.9 of BMC Server Automation, you can choose not to upgrade certain consoles. Specifically, version 8.9 of the BMC Server Automation Application Server supports communication with BMC Server Automation Consoles of version 8.8. To enable this backward support for any specific Application Server, you must use the blasadmin command To enable communication with clients of an earlier version of BMC Server Automation.to turn off the version compatibility check that occurs whenever you access a Console. For more information, see
Prior to upgrading your production environment, it is best practice to test the upgrade in a duplicated environment.
Step 1: Review requirements and limitations
The first step is to review the following requirements and limitations when using the unified product installer for product upgrade.
Supported upgrade paths
BMC Server Automation supports direct upgrade from versions 8.6, 8.7, and 8.8. If you need to upgrade from BMC Server Automation version 8.5.x or earlier, you must first upgrade to one of the following:
- The latest 8.6 service pack, (as discussed in the Upgrading section of the BMC Server Automation 8.6 online documentation)
The latest 8.7 service pack, (as discussed in the Upgrading section of the BMC Server Automation 8.7 online documentation)
- The latest 8.8 service pack, (as discussed in the Upgrading section of the BMC Server Automation 8.8 online documentation)
Afterwards, you can upgrade from version 8.6.xx, 8.7.xx or 8.8.xx to 8.9.x.
The following figures illustrate the supported upgrade paths to BMC Server Automation 8.9.x.
If you are running BMC Server Automation 8.7 Patch 5 or 8.8 Patch 2, you cannot upgrade to version 8.9.01. However, you will be able to upgrade to version 8.9.02 after it is released. To receive proactive notifications for new releases, subscribe to BMC Server Automation's Subscription List on the BMC Support site.
If you are running BMC Server Automation 8.7 Patch 5 or 8.8 Patch 2, you cannot upgrade to version 8.9.00. However, you will be able to upgrade to version 8.9.02 after it is released. To receive proactive notifications for new releases, subscribe to BMC Server Automation's Subscription List on the BMC Support site.
In the above diagrams, abbreviations are defined as follows:
- BSA stands for BMC Server Automation
- SP stands for Service Pack
- P stands for Patch
If your BMC Server Automation environment includes BMC BladeLogic Decision Support for Server Automation, upgrade BMC BladeLogic Decision Support for Server Automation before upgrading BMC Server Automation. For more information, see the following topic in the Decision Support for Server Automation online technical documentation:Upgrading
If your BMC Server Automation environment includes BMC Cloud Lifecycle Management, you need to ensure that you maintain compatibility with BMC Cloud Lifecycle Management. For more information, see the following topic in the BMC Cloud Lifecycle Management online technical documentation: Component BMC product service pack and patch levels
Review the following key requirements.
Click here to review.
The unified installer supports Windows 64-bit and Linux 64-bit operating systems. For a complete list of platforms supported by the unified installer, see:
|PXE servers||To improve performance during the upgrade, create a new folder on your remote PXE server (by default, %SystemDrive%/BBSAInstallerDumpDir, for example, C:/BBSAInstallerDumpDir) and then manually copy the PXE installer binary (..\installers\pxe_64\PXE<version>-WIN32) into the %SystemDrive%/BBSAInstallerDumpDir folder prior to upgrading. The unified product installer validates the existence of the PXE installer binary under the expected location, and upgrades the PXE server during the upgrade process.|
If you are using Microsoft Windows 2003 or 2008, you must upgrade in Install mode instead of Execute mode, see Using Install mode instead of Execute mode.
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. Therefore, as part of the upgrade process, you must distribute the latest versions of the custom configuration objects that are not included as part of an RSCD agent.
The product installation is automatically upgraded to the appropriate version when you upgrade the agent. However, you must upgrade any custom configuration objects that are not included with the agent by running a Distribute Configuration Objects Job. Configure this job to target servers to which custom configuration objects need to be distributed. For a list of those objects that are included as part of an agent installation and those that are not included with the agent and require distribution, see Custom configuration objects.
To upgrade custom configuration objects
Click here to see the steps for upgrading custom configuration objects.
To upgrade virtualization configuration objects
Click here to see the steps for upgrading virtualization configuration objects.
The Upgrade Model Object Job is not supported for upgrading virtualization configuration objects.
To upgrade configuration objects that you distributed in prior versions, complete the following steps:
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. Therefore, as part of the upgrade process, you must distribute the latest versions of custom configuration objects for the custom configuration objects that are not included as part of an agent. The installation are automatically upgraded to the appropriate version when you upgrade the agent. (See Custom configuration objects for a list of those objects.) You should upgrade any custom configuration objects not included with the agent by running a Distribute Configuration Objects Job. The job should target servers to which custom configuration objects should be distributed.
Click here to review a list of potential issues you can encounter during an upgrade.
Limitations when using the unified product installer
|Category||Description of support or limitation|
|Multiple Application Server (MAS) environments||The unified product installer only supports upgrade of an homogeneous MAS environment, that is, either all Application Servers run on Linux 64-bit operating systems or all run on Windows 64-bit operating systems.|
|"Mixed" Application Server/database environments||The unified product installer supports upgrade of "mixed" Application Server/database environments (for example, Linux Application Server + Microsoft SQL Server database). The UPI does not require the database or the file server operating system to match the operating system of the Application Servers.|
For PXE servers to be upgraded by the unified product installer, they must be:
If your environment includes hybrid PXE servers (that is, PXE servers not running Windows or Linux), you must perform a workaround for the upgrade
Click here to see the workaround.
The unified product installer does not support the following upgrade scenarios:
Step 2: Prepare the environment for upgrade
Perform these tasks in order. Many steps are prerequisites for other steps that occur later in the process.
- Back up the BMC Server Automation database. The data upgrade occurs in place. If, for any reason, it should become impossible to complete the upgrade, the only way to restore the database to its pre-upgrade state is from the backups.
- Ensure that your connection to Microsoft SQL database is not encrypted. BMC Server Automation does not support using an encrypted Microsoft SQL database connection at the time of upgrade. However, after the product is upgraded successfully, BMC Server Automation can use an encrypted connection to communicate with the Microsoft SQL database. For steps on enabling and disabling an encrypted connection to your SQL database server, see Encrypting your database connection.
- Verify that the following components are up and running for the upgrade to be successful:
- All Application Servers
- PXE Server
- RSCD agents on Application Servers, PXE servers, and file servers.
Back up the installation directories for all Application Servers and PXE servers. The default installation locations are:
- Application Server: C:\Program Files\BMC Software\BladeLogic\NSH
- PXE Server: C:\Program Files\BMC Software\BladeLogic\PXE
If you are upgrading the PXE server, follow the upgrade instructions for Windows or UNIX, to prevent loss of configuration settings.
Ensure that all files and folders in the installation directory and its sub-directories do not have the read-only attribute enabled. The upgrade might fail, if the read-only attribute is enabled on any file.
Note that the user who installed the earlier version of the product might have changed the installation directory from the default location, so ensure that you have the right location. If your current installation is already an upgrade from a previous version, the paths might be different, due to differences in these locations in earlier versions of BMC Server Automation. If you do not know the installation location for BMC Server Automation components view the contents of the %WINDIR%\rsc\HOME file.
- Back up the BMC Server Automation file server storage location. For example, copy the entire contents of the storage location to a directory other than the current storage location.
Ensure that there is an RSCD agent installed on each Application Server to avoid potential errors in the upgrade process.
Ensure that there is an RSCD agent and NSH are installed on the PXE server.
- Make sure that you have 4 GB on disk with temp space and 4 GB on disk with installation directory.
Ensure that you have disabled the NSH proxy on all Application Servers in the environment to avoid failure during upgrade. To disable the NSH proxy, run the following command on the NSH client:
secadmin -m default -p 5 -appserver_protocol clear -T encryption_only -e tls
Note: After the upgrade completes, remember to add this entry back into the secure file. You can use the following command:
secadmin -m default -p 5 -appserver_protocol ssoproxy -T encryption_only -e tls
10. Ensure that Microsoft Visual C++ 2015 Redistributable Update 3 is installed on the server. For more information, see Installing an RSCD agent (Windows).
As a prerequisite to install Microsoft Visual C++ 2015 Redistributable Update 3 on Windows 2012 R2, you must have the following patches installed on your server:
- KB2919442 - This patch is required for KB2919355.
- KB2919355 - This patch requires several other patches (clearcompressionflag.exe, KB2919355, KB2932046, KB2959977, KB2937592, KB2938439, and KB2934018). These are available on download KB2919355 page.
For more information about the prerequisites for Microsoft Visual C++ 2015 Redistributable Update 3, refer to the Microsoft documentation here.
11. To preserve the Live Reporting dashboard environment, back up the cacerts file (for example,C:\Program Files\BMC Software\BladeLogic\appserver\NSH\jre\lib\security\cacerts for Windows) to a separate safe location on the BladeLogic server. You must do this because the BladeLogic upgrade overwrites the existing cacerts.
Related topic: (See these topics for additional upgrade considerations and supported upgrade paths)
Step 3: Download the files
Download and extract the installation files to a temporary location.
- Download the BBSA89-WIN64.zip file (which contains the unified product installation program files) to the host computer of the Application Server that was set up as a configuration server.
- Extract the BBSA89-RSCDAgent.zip file from the package and copy the rscd folder to ../BBSA89-WIN64/Disk1/files/installers/ before running the unified product installer. The unified product installer uses the RSCD installers while installing or upgrading BMC Server Automation in your environment.
Step 4: Run the unified product installer on the Application Server
When you run the unified product installer on the Application Server, the unified product installer automatically upgrades the database, file server, Application Server, agents, PXE server, and TFTP server in your environment, with certain exceptions. Before running the upgrade, back up your database and inform your users that BMC Server Automation will be unavailable during the upgrade.
Tip for upgrading PXE servers
If you have one or more PXE servers that are remote (on a different LAN/WAN than the Application Server), do the following to improve performance during the upgrade:
Create a new folder on your remote PXE server (by default, %SystemDrive%/BBSAInstallerDumpDir, for example, C:/BBSAInstallerDumpDir) and then manually copy the PXE installer binary (..\installers\pxe_64\PXE89-WIN32) into the %SystemDrive%/BBSAInstallerDumpDir folder prior to upgrading.
The unified product installer validates the existence of the PXE installer binary under the expected location, and upgrades the PXE server during the upgrade process.
This process is strongly recommended if your PXE servers are on a different LAN/WAN.
- Navigate to the temporary directory that contains the installation files.
- Run the installation program (setup.exe for Windows)
Note: For Windows 2008 or higher, right-click the installer file and select Run as administrator.
- Select the language in which you want to run the installer and click OK.
Note: If problems arise during the upgrade, the on-screen error messages contain instructions and guidance to help you troubleshoot the problems, and further information is available in the log files. For a list of log files written during the upgrade process, see the Troubleshooting section.
- Read through the basic information about the unified product installer and the types of nodes that are installed in the environment.
- Click Next.
Read the End User License Agreement (EULA) and select I agree to the terms of the license agreement, and then click Next.
Read the copyright statement and select I agree to the terms of the license agreement, and then click Next.
Enter your Authentication profile credentials to proceed with the upgrade procedure.
The profile that you specify must be associated with the same Application Server where you are performing the upgrade. Note that only secure remote password (SRP), LDAP, or Domain Authentication type profiles can be used with the unified product installer.
Review the BMC BladeLogic Server Automation infrastructure discovered in your environment.
This includes the different types of servers that are present in the BMC Server Automation environment, their count, and their status. If your environment includes PXE servers, the installer upgrades the PXE server automatically, if it is up and running during the infrastructure discovery phase.
If you are running one or more remote PXE servers (that is, on a different subnet than the Application Server), the installer detects and lists them as part of your infrastructure. The unified product installer upgrades the remote PXE servers as part of the upgrade process. The checkbox for the Remote Site field controls how the PXE server installer files are copied to the PXE server, as described in the table below.
PXE upgrade option Explanation Remote Site field selected (default) Selecting the checkbox assumes that you have previously manually copied the PXE installer binary (..\installers\pxe_64\PXE89-WIN32) to the %SystemDrive%/BBSAInstallerDumpDir on the PXE server prior to upgrading. The unified product installer validates the existence of the PXE installer binary under the expected location, and upgrades the PXE server during the upgrade process. For performance reasons, this option is strongly recommended for PXE servers that are on a different LAN/WAN than the Application Server. Remote Site field cleared (not selected) Clearing the checkbox assumes that you want the installer to copy ..\installers\pxe_64\PXE89-WIN32 file to the remote host, to the %systemDrive%\BBSAInstallerDumpDir folder. De-select the Remote Site option if the PXE server is on the same LAN/WAN as the Application Server. However, note that clearing the checkbox is typically much slower if thePXE server is on a different LAN/WAN than the Application Server.
- Click Next.
- Preview the upgrade.
- Select the I acknowledge that the installer will bring down the BladeLogic Server Automation (BSA) environment for upgrade check box.
- Click Install.
- If you encounter a failure, fix the underlying cause and re-run the installer. When you see the re-attempt panel, review the information and then click Install.
- When the upgrade is finished, review the summary and the upgrade log, and then click Done.
Step 5: Uninstall the old console on the Application Server system
You cannot use a version of the BladeLogic Console that is incompatible with the connecting Application Server, as shown in the following screenshot. Therefore, uninstall the existing version of the BSA Console before you upgrade the Application Server and the other components unless you absolutely need to create a ready-to-use test environment.
As of version 8.9 of BMC Server Automation, you can choose not to upgrade certain consoles, and you can turn off the compatibility check shown above. For more information, see To enable communication with clients of an earlier version of BMC Server Automation.
Before you uninstall the console,note the following:
Before uninstalling components, back up C:\WINDOWS\rsc. This directory holds several important files, including the exports, users, and secure files. These files define communication and security settings for an RSCD agent.
If multiple versions of the BMC Server Automation console are installed, the directory holding these files is C:\Program Files\BMC Software\BladeLogicx, where x represents the BMC Server Automation installation number.
To uninstall the existing console:
- Back up the rsc directory (for example, C:\Windows\rsc). The rsc directory holds several important files, includes exports, users, and secure.
- Install the latest 64-bit JRE. Otherwise, the Windows uninstaller cannot find the JVM necessary to uninstall the console.
- Open the Windows Control Panel.
- Select Uninstall a Program.
- Select BMC BladeLogic Server Automation Console.
- Click Uninstall/Change.
- Close the uninstall wizard when you finish.
- Clean up any remaining files in the installation directory.
For more information, see Upgrading the BMC Server Automation Console.
Step 6: Install the new console on a separate system
Because the unified product installer does not upgrade the console, you must manually upgrade the console to match the Application Server version so that the console functions correctly.
BMC recommends that you do not install or upgrade the console on the same system as the Application Server. Copy the console installation files located on the Application Server (for example, ...\BBSA88-WIN64\Disk1\files\installers\rcp) to a separate system and install the console there.
Navigate to the directory containing the installation files that you copied from the Application Server and run the installation program for the console (for example, ..\BBSA89-WIN64\Disk1\files\installers\rcp). Different installers are provided for 32-bit and 64-bit Windows.
In this example, we are running the BBSACONSOLE89-WIN64 file on the Windows machine on which you plan to install the console.
Select a language to use for the installation and click OK.
The installer extracts the installation files, and the Introduction window opens.
Ensure that you have closed all applications before you proceed.
The Review License Agreement window opens.
Read the End User License Agreement (EULA) and select I agree to the terms of the license agreement if you wish to proceed.
The Directory Selection window opens.
The default installation location for the console is C:\Program Files\BMC Software\BladeLogic. Click Next to use the default location.
Alternatively, you can click Browse to change the installation location.
A window opens in which you can select components to install. By default, all components are selected.
The Network Shell is automatically installed when you install the console.
Note: If you clear the BMC Server Automation Console Upgrade Service check box, the BMC Server Automation Console Upgrade Service is not installed. This service is required for automatically upgrading the BMC Server Automation Console when you upgrade the Application Server.
The window displays your selections.
The installer pre-analyzes your environment:
The window displays installation progress, then displays a message when installation is complete.
The console and Network Shell are installed on your machine.
If all operations are completed successfully, click Done to exit the wizard.
If you encountered any errors while installing, you can click View Log to view a detailed report of the installation.
Tip: BMC recommends that you save a copy of the log, before you contact technical support for further assistance. You can also find more information about resolving common issues in Troubleshooting the unified product installer.
Start the console.
To configure the console so that it connects to the default Application Server, click Options.
Click the Authentication Profiles tab and click Add.
BSA clients use authentication profiles to facilitate single sign-on feature. You must create an Authentication profile before you start using the Console. For more information about why we use Authentication Profiles, see System capabilities related to security.
Enter the following information.
You can now log on the the Console using the BLAdmin user that is created while installing the default Application Server node, see step 10.
The quick start page is the first page that is displayed once you log on the the BSA Console. It introduces you to the main use cases of BMC Server Automation and allows you to execute them from a centralized UI immediately after installing the BSA set up. For information about using the quick start page, see Quick start page.
For general information about the UI of the BSA Console, see Navigating the interface.
Step 7: Manually upgrade additional components
After the unified product installer completes the upgrade, manually upgrade any components that meet the following criteria. Perform this step anytime after the upgrade.
- NSH clients on non-Application Server host computers - Use the instructions in Upgrading the Network Shell on Windows.
PXE and TFTP servers that reside on separate host computers - When you upgrade a PXE server on a different subnet than the target server, you need to copy the installation files to the remote machine and upgrade the remaining servers manually, as described in Upgrading a PXE server on Windows or Upgrading a PXE server on Linux or UNIX.
If the TFTP service is not started automatically after the upgrade, manually start it, as described in Starting and stopping a TFTP server.
- Upgrade any agents that you may have that fall into the following categories.
- Agent on an online or offline patch repository
- Agent on a basic/standard repeater
- Agent on a VMware vCenter server. You must upgrade the agent on the vCenter server before you try to use the vCenter integration or the updated VMware configuration object push. For more information, see Setting up a VMware vSphere environment and Distributing configuration objects.
Step 8: Perform additional post-upgrade tasks
At any time after the upgrade, complete the following tasks, if they apply to your environment:
|Run the Update Model Objects Job|
For custom configuration objects to work reliably, the version of the custom object should match the version of the agent. You can perform this step anytime after the upgrade.
|If you are running patch management in offline mode|
If you employ patch management in offline mode, you must:
|Upgrade Compliance Content add-ons|
Perform an over-the-top upgrade of the new Compliance Content add-ons. You can perform this step anytime after the upgrade.
Related topic: Installing and configuring Compliance Content add-ons