Walkthrough: Upgrading to version 8.7 for Microsoft Windows
Prior to upgrading your production environment, it is best practice to test the upgrade in a duplicated environment.
If you are running BMC Server Automation 8.5.x or later, and are running 64-bit Microsoft Windows platforms, you can use the unified product installer to upgrade to version 8.7.
The topic includes the following sections:
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:
As 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.
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.5.xx and 8.6.xx. If you need to upgrade from BMC Server Automation version 8.3.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.5 service pack, (as discussed in the Upgrading section of the BMC Server Automation 8.5 online documentation)
Afterwards, you can upgrade from version 8.5.xx or 8.6.xx to 8.7.x.
The following figures illustrate the supported upgrade paths to BMC Server Automation 8.7.x.
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.
If your id.pem certificate was created with a key size of 1024 bits (or less), you will need to regenerate it with a higher key size (2048 or higher). This is due to a change in the FIPS requirement for minimum key length (now 2048 bits).
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.
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 BBSA87-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 BBSA87-RSCDAgent.zip file from the package and copy the rscd folder to ../BBSA87-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
The unified product installer automatically upgrades the database, file server, Application Server, agents, PXE server and TFTP server, and console in your environment, with certain exceptions. The checklist below walks you through the process of upgrading the Windows environment using the unified product installer.
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\PXE87-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.
|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, and console in your environment, with certain exceptions (see .
To run the unified product installer the Application Server
About the Discovered BladeLogic Server Automation Infrastructure screen
If any of the remote servers do not have an RSCD Agent installed, the wizard first displays a list of those servers, and you must decide whether to manually install RSCD Agents on these servers or to provide connection details for enabling the unified product installer to perform the installation of an RSCD Agent on each of the servers.
If you are running one or more PXE servers, the installer detects and lists them as part of your infrastructure. The unified product installer upgrades the 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 below.
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.
Related topic: Upgrading on Windows using the unified product installer
|Upgrade the console.|
To upgrade the console
After completing the upgrade using the unified product installer, you can attend to the upgrade of the console, according to the following scenarios:
Related topic: Upgrading the BMC Server Automation Console
|Upgrade components that were not upgraded|
After the unified product installer completes the upgrade, you must manually upgrade any components that meet the following criteria. You can perform this step anytime after the upgrade.
|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.
|Upgrade Compliance Content.|
Perform an over-the-top installation 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