Patch 2: version 8.5.00.002
This topic contains information about fixes and updates in Patch 2 (product version 8.5.00.002), and provides instructions for downloading and installing the patch.
For information about issues corrected in this patch, see Known and corrected issues.
There are no updates in Patch 2 for version 8.5.00.
EPD version number
|Patch 2 for version 8.5||8.5.00.469||8.5.00.002||May 6, 2014|
Downloading the patch
Patch 2 for version 8.5.00 includes full installers for all components. You can download the files for version 8.5.00.002 from the BMC Electronic Product Distribution (EPD) website. For download instructions, see Downloading the installation files. For a list of installation programs by OS, see Installation programs for BMC Server Automation.
Installing the patch as a fresh product installation
If you are installing this patch as a fresh product installation, download the Service Pack files and then follow the instructions in Performing the installation.
Upgrading to the service pack and patch
To upgrade to the service pack and patch, follow the instructions in Upgrading.
The installation programs for BMC Vendor Patch Management and BMC BladeLogic Advanced Repeater were not upgraded for service packs. If you have installed version 8.5.00 for any of these programs, you do not need to upgrade these programs when upgrading to the service pack level.
Note the following special tasks that you must perform during an upgrade to a service pack, after upgrading the Application Server and Console:
|Special condition or scenario||Task description|
|If upgrading from 8.3.x or earlier||Run the Data Migration Manager using the version 8.5 external files to upgrade your Oracle or SQL Server database to version 8.5.|
|If upgrading from a version earlier than 8.0||Run the postmigration file to migrate pre-8.x compliance rules and discovery signatures.|
|If smart group conditions were defined in any earlier version||Run the postmigration file to migrate and update smart group conditions.|
Considerations in patch implementation for patch management on Windows
If you are using Microsoft Windows, review the following considerations for patch management.
Resolving a potential RSCD Agent installation problem
If the target system is in a pending reboot state (for example, from a previous patch or other software installation), you can use the PENDINGREBOOTFORCE flag to allow the MSI installer to ignore the pending reboot state and allow the installation to proceed. After you confirm that the pending reboot state on the target is not a result of a previous RSCD installation, you can set
PENDINGREBOOTFORCE=1. Following is a command-line sample for the MSI installation program:
msiexec /I RSCD85-P2.WIN32.msi /qn REBOOT=ReallySuppress PENDINGREBOOTFORCE=1