Upgrading product components on Microsoft Windows
BDSSA upgrade requirement
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:
The following topics provide information about upgrading the individual components of the BMC Server Automation system on Microsoft Windows, using the component installers.
| Step | Description |
|---|---|
| Preparing to upgrade individual components on Microsoft Windows | 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. You must also download the installers (see Downloading the installation files). |
Do not restart the Application Server until you complete the database migration. Note that an upgrade of the Application Server also upgrades the Network Shell. | |
| Migrating the database and persisting configuration data to the database | Run the configurator utility on all Application Servers and PXE Servers to migrate configuration data. |
| Performing post-migration updates | 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 Console | Upgrade at least one BMC Server Automation Console. |
| 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 on Windows | 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. |
Comments