Share This:

Upgrading the BMC Client management Master server and database is a pretty simple job. All you need to consider is the upgrade path based on the current version you have, the hardware and software requirements for the target BCM Master server version, steps required to be done before proceeding for an upgrade. This has been explained in detail in following sections.

 

 

 

BCM Upgrade Path:

BCM supports upgrade up to the latest versions from legacy versions. However not always its possible to upgrade to the latest environment from the version you have as the database schema has been changed on specific version. This section explains the upgrade patch based on the version you currently have.

 

From Version 11.x or 12.0 to 12.9:

If you are currently on 11.x or 12.0 version you will need to upgrade first to 12.1. Once the master and client agents are upgraded to 12.1 you can then upgrade to 12.6, 12.7, 12.8 and 12.9 versions.

1.png

From Version 12.1 to 12.9:

If you are on 12.1 or higher version you can directly upgrade to any of the 12.6, 12.7, 12.8 and 12.9 versions.

2nd.png

From Version 12.5 or earlier to 20.08:

If you are on 12.5 or earlier versions and want to upgrade to 20.08, you will need to upgrade first to any of the 12.6, 12.7, 12.8 and 12.9 version. You can then upgrade to 20.08 version.

3rd.png

 

From Version 12.6,12.7,12.8 and 12.9 to 20.08:

If you are on any of the version 12.6, 12.7, 12.8 and 12.9, you can directly upgrade to 20.08.

4th.png

System Requirements:

Depending on the architecture, the hardware and software requirements must be met before on-premises and cloud installation of BMC Client Management components.

 

Database prerequisites: The BMC Client Management setup offers the possibility to install MS SQL Server Express on the master server for Windows platforms that have no database engine already installed on their network. MS SQL Server Express is installed during master server installation. If you have a version of MS SQL Server, Oracle, or PostgreSQL already installed, you must ensure that the following prerequisites are fulfilled before starting the Client Management setup process:

 

BCM 12.8 & Higher version Agent Prerequisites:

To rollout or upgrade BCM 12.8 and higher version Agents on devices on supported operating systems, administrator must install the Microsoft Universal C Runtime (UCRT) first. The recent operating systems might include the new runtime but the administrator must install the patch on the older operating systems by using the KB2999226. For more information, see https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows.

 

Following document explains this.
12.8 enhancements - Documentation for BMC Client Management 12.8 - Update Microsoft Universal C Runtime (UCRT) before rolling out agents

 

Preparation for upgrade for all the version and Database preparation if you are on the version 11.7 or earlier:

Before actually proceeding for an upgrade based on the version you are on its best to make the preparations beforehand.

  • If you are updating from BMC Client Management 12.0 or earlier using the automatic upgrade procedure for your agents and you are using the operating system deployment (OSD) functionality of BMC Client Management, you should first refer to Considerations when upgrading OSD to version 12.1 and later before you start the upgrade. The OSD functionality has undergone major changes in BMC Client Management 12.1 release that might impact your way of working, and you might consider not to automatically upgrade your OSD Manager devices to the new version, or execute some specific actions on these before proceeding with the upgrade.
  • If you have an BMC Helix Client Management installation and your system is properly set up, all BMC Helix Client Management components should be automatically upgraded.
  • Make sure you have a valid license for your upgrade to the current version. Your current license continues to work for 30 days after the upgrade. You can download your new license from your support profile on our website, or by contacting Technical Support.
  • If you are currently using Microsoft Internet Explorer 8 to access the agent interface, you can no longer display the graphics of these pages. You must upgrade to a newer browser. For more information, see System requirements.
  • The SCAP validation package that was present in earlier versions is removed from BMC Client Management version 12.9. Therefore, verifying an imported SCAP package is currently not possible.

 

The following document covers all such requirements. It also explains specific database script executions if you are on version 11.x or earlier.
Preparing for upgrade - Documentation for BMC Client Management 12.9

Preparing for upgrade - Documentation for BMC Client Management 20.08

 

Preparation for the upgrade from the BCM console:

It's better to clean packages and operational rules from previous upgrade(s) first before you upgrade to a newer major version. Sometimes the import will fail or will be partial if you don't. Normally the mechanism is supposed to manage this but it fails sometimes, especially if you've been using BCM product from several versions. In this case you might have packages and operational rules in various directories instead of one: "Asset Management Platform Upgrade" "Footprints Asset Core Upgrade" or "Client Management Upgrade". It could be a mess and packages would be replicated in these folders or not.

 

This should not take too much time to perform and it's always a good thing to do some regular cleanup. For details steps on the cleanup please refer following document:

Prepare your BCM console upgrade to a new major version of BMC Client Management

 

Performing the Upgrade:

The new version of BMC Client Management requires new tablespaces. For more information, see Preparing for upgrade. If you have an SQL database, the tablespace upgrade is included in the master upgrade process. However, in specific situations, you still must upgrade the tablespaces manually. For example, if you renamed the tablespaces from their default values. For more information on updating tablespaces, see Preparing for upgrade.

The update processes of the master and the database are closely linked together and consist of the operations described in the following procedure. It involves the actual steps for an upgrade. Please refer the following documents for the detailed steps:

Performing the upgrade - Documentation for BMC Client Management 12.9

Performing the upgrade - Documentation for BMC Client Management 20.08


Upgrading the Relay & Client Agent post upgrade:

The upgrading the Relay and client agents is equally important. Please note that the BCM agent version on an older version will communicate to the upgraded master however the Defects fixed on the newer version will only be applicable on relays and clients when its upgraded to the same version as Master. Please note that you upgrade the relay Agent versions before clients.

You can select an option to automatically upgrade the client agents post the master server upgrade. This saves manual efforts to individually configure and assign device groups later to upgrade operational rules. You can use Transfer Windows to limit the network usage during the automated agent upgrade process.

Upgrading client agents individually - Documentation for BMC Client Management 12.9

Upgrading client agent on all platforms automatically - Documentation for BMC Client Management 12.9

Upgrading client agents individually - Documentation for BMC Client Management 20.08

Upgrading client agent on all platforms automatically - Documentation for BMC Client Management 20.08