Service Pack 3: version 8.3.03
This topic contains information about fixes and updates in BMC Server Automation 8.3 Service Pack 3 (product version 8.3.03), and provides instructions for downloading and installing the service pack.
Tip
For information about issues corrected in this service pack, see Known and corrected issues.
Enhancements
The following topics describe the updates and enhancements included in this service pack.
- Agent and NSH updates for SP3
- BLCLI updates for SP3
- Compliance Content updates for SP3
- Console management updates for SP3
- Database updates for SP3
- Installation updates for SP3
- Patch management updates for SP3
Tip
Click here to create a PDF containing only content related to Service Pack 3.
Downloading the service pack
Service Pack 3 for BMC Server Automation 8.3.00 includes full installers for all components. You can download the files for version 8.3.03 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 service pack as a fresh product installation
If you are installing this service pack as a fresh product installation, download the Service Pack files and then follow the instructions in Performing the installation.
After configuring the database, run the scripts found in the 83SP3-SQL_Update_Scripts.zip file. This file is available in the BMC Server Automation 8.3.03 section of the EPD. Run these scripts as the BMC Server Automation database owner (as provided to blasadmin). For more detailed instructions, see Running the SQL update scripts.
Upgrading to the service pack
To upgrade to the service pack, follow the instructions in Upgrading.
Note
The installation programs for BMC Vendor Patch Management were not upgraded for service packs. If you have installed version 8.3.00 for this program, you do not need to upgrade these programs when upgrading to the service pack level.
Supported upgrade paths
The following table lists information for the most recent BMC Server Automation version 8.3 builds.
Release | Build number | EPD version number | Release date |
|---|---|---|---|
| Service Pack 3 | 8.3.03.082 | 8.3.03 | February 21, 2014 |
| Service Pack 2 Patch 1 | 8.3.02.407 | 8.3.02.001 | December 18, 2013 |
| Service Pack 2 | 8.3.02.332 | 8.3.02 | August 30, 2013 |
| Service Pack 1 | 8.3.01.160 | 8.3.01 | May 15, 2013 |
Base version 8.3 | 8.3.00.114 | 8.3.00 | January 14, 2013 |
The following list identifies the supported upgrade paths:
- Version 8.3.00 to any later 8.3 service pack or patch
- Version 8.2 direct to version 8.3.x
- Version 8.1 direct to version 8.3.x
8.0 to SP6 to version 8.3.x
To upgrade from an 8.0 version earlier than 8.0 SP6, first apply SP6.
Special upgrade scenarios
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.2.x or earlier | Run the Data Migration Manager using the version 8.3 external files to upgrade your Oracle or SQL Server database to version 8.3. |
| Any upgrade | Run the SQL Update scripts found in the 83SP3-SQL_Update_Scripts.zip file. This file is available in the BMC Server Automation 8.3.03 section of the EPD. Run these scripts as the BMC Server Automation database owner (as provided to blasadmin). |
| 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 service pack 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. A command-line sample for the MSI installation program follows:
msiexec /I RSCD83-SP1.WIN32.msi /qn REBOOT=ReallySuppress PENDINGREBOOTFORCE=1
Comments
We have found that since we have upgraded from SP2 to SP3, users need the authorization BLPackage.Create in order to run deploy jobs that deploy custom software. The hidden BLPackage Builder Job sees to requires this to create the BLPackage needed to deploy the custom software. Without this auth, users get the following error before the Dryrun can even begin:
Example: Access Denied CREATE on CM-Monitoring_BPPM_KM_for_Remedy_AR_Windows-240730.2-0.18997430574236918
This authorization was not required before SP3 in order to run the same job. An issue is being opened for this with Premier Support: ISS04300968
Added as a prerequisite in the 8.3 and 8.5 documentation. Also as a known issue. See the following pages.
For 8.3:
Known and corrected issues in Deploy Jobs
Creating a Deploy Job
For 8.5:
Known and corrected issues
Creating a Deploy Job
Added as a corrected issue in the 8.6 documentation: Known and corrected issues
Log in or register to comment.