Skip navigation
1 2 3 4 Previous Next

Client Management

56 posts
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.


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.


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.



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.


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


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


Share This:

Check out their story here:


West Midlands Ambulance Service implemented BMC Helix Client Management with the goal of consolidating its mix of homegrown, manual, and vendor tools to more effectively manage and track its assets. BMC Helix Client Management deploys the proper software specific to the device and the user, ensures organizational and industry policy compliance, and keeps patches up to date until the device is retired.

As the COVID-19 pandemic took workers offsite and then returned them to the office, the solution has allowed WMAS the flexibility to accommodate both onsite and home-based workers, with critical security patching extended easily to remote locations when needed, accomplished in just one weekend.

BMC Helix Client Management’s comprehensive automation capabilities help ensure that both part-time workers and full-time employees can effectively manage the Trust’s growing number of technology assets without troublesome or time-consuming hand-offs. Importantly, the Trust has also been able to reduce its compliance risk by automating policy compliance and remediation for endpoint access.

West Midlands - BMC Software

Share This:

We designed 20.08 for you, with you

With 20.08 being released, we want to give back to all the Community Members who helped shape an exciting release.

whats new customer ideas 2008.JPG

Thanks to everyone who created and voted on these Ideas!

Be sure to visit top+recent ideas and vote or comment. Is your idea not listed? Add it!

Many thanks again to our beta participants (especially Dominik Kress, Steve Gibbs and Joerg Schellenberger) and the whole team who helps to bring more value to BMC Helix Client Management.


Release Overview & Key Enhancements

You can do a lot more with 20.08, especially in Web Console and Patch Management:

20.08 release overview video



whats new web 2008.JPGKey Web Console enhancements



whats new patch 2008.JPGExciting Patch Management enhancements


Anything you'd like to know more about? Make a comment below.

To see full description of each feature, check out the new product docs.

Share This:

Hi Everyone,


Welcome to our new BMC Client Management (BCM) Blog for the month of August 2020. In this blog, we will provide detailed information about Patch Management. Below are the topics which we are going to cover:


  • What is Patch Management and what we can do with it?
  • Prerequisites of Patch Management
  • How the patch management works
  • Viewing the progress using the Reports


What is Patch Management and what we can do with it:


Patch Management is one of the most favorite modules of BMC Client Management for every BCM Customer. WIth Patch management, it provides an easy way to manage, update, and download all of the patches for Microsoft operating systems, and selected third-party applications, such as Firefox, 7Zip, and others which can be installed across the network for staying up-to-date.

In BCM Patch Management, Target/Client never requests for the patches. The BCM Administrator will have full control to deploy which patches and when to deploy them.

Patch Management allows you to:

  • Identify which target devices need to be patched or contains a vulnerability
  • Create a remote deployment of patches automatically or manually when required or at scheduled times
  • Monitoring the deployment process and viewing the results using reports.

Prerequisites of Patch Management which need to be followed:

A) A valid BCM Patch Management License

  • To be able to keep your patch knowledge base up to date and able to download the newer patches




B) A device (Patch Manager) which has internet access

        This device should be able to download the patches from the internet and should have:

     I) at least 20GB disk space or dedicated place for storing the patches
     ii) one of the following operating systems:

    • Windows 8 32 and 64 bit
    • Windows 8.1 32 and 64 bit
    • Windows 10
    • Windows Server 2008 R2 64-bit
    • Windows Server 2012 64-bit
    • Windows Server 2012 R2 64-bit
    • Windows Server 2016 64-bit
    • Windows Server 2019 64-Bit (BCM 12.9 and above)

     iii) patch manager should not use only an IPv6 address.
     iv)  the root certificate of the devices should be up to date. Bulletins MSRC-001 or MSRC-002 should be installed on the Patch Manager.
     v) able to reach: for downloading Patch Kb and should have access to download the patches from the internet
C) BCM version should be 12.8 patch 3 or above for supporting newer Ivanti SDK.


How does the Patch Management work:


Patch Management consists of 3 steps:


1) Patch Knowledge Base update:


Patch Manager checks-in for a new knowledge base (KB) once a day. Once a new patch KB obtained from the SDK vendor Ivanti/Shavlik, it will update the patch manager KB and send the new patch KB to the Master, Where it is stored for the distribution to BCM (BMC Client Management) clients.


  • BCM Master will start notifying all the clients about the New Patch KB and will send them the new update upon the client request through the filestore module.
    When the Patch KB Download is completed on the client, the patch Kb will evaluate and generate a new patch Inventory.





2) Patch Inventory Evaluation


Based on the default mechanism of Patch Management module each client devices scan itself for missing or installed patch inventory and upload the result to the master server. This patch inventory is generated against its operating system, installed applications, and third-party applications for assessing the result in missing patches or missing service packs. The Client sent the inventory via the Upstream module of each Client's parent Relay for processing on Master to integrate the inventory for this client into the BCM database, then this integration triggers an evaluation of the existing patch assignment.


How to view the Patch Inventory:

- Go to the device from BCM Console
- Expand it from the left-hand side Click on Inventory then from Patch.
- Click on Missing patches for Missing the patches to this device or click to view the missing service packs or installed patches or installed service packs




3) Patch Deployment Process


BCM Patch Management supports two methods of deployment of patches on clients.


a) Patch Group and

b) Patch Job


a) Patch Group also is known as Patch deployment on BCM Patch Management console. Patch groups are the manual patch selection method in which the administrator has to decide when to deploy and which specific patches or service packs need to be deployed.




How to create a patch group for deploying only specific patches like VC_Redist new update:




creating Patch group.png

To use the Patch deployment feature. You would need to go the

Expand the Patch Deployment (Aka Patch group)

  • Right-click on Patch Deployment and choose to Create Patch/Service Pack Distribution Wizard.
creating Patch group1.png

Click on Automatic Configuration to create an auto-configured patch group (which will have predefined settings for creating a patch group)


Add a meaning full name to it and click on Next button


creating Patch group2.png

This option will allow you to add the specific patch for the deployment by searching using this Misc pane or using Severity and filtered using the patch type and product name.


The Option called Affected device will only show the patches which are missing on devices (from all managed devices) with these filtered data.


Patches can be filtered using the contains table (if you're looking for a specific patch like VC_Redist or any other with the Start date in conjunction)

creating Patch group3.png

Once you're able to find the specific patch for deployment, You can select from Patch name as I did, I selected a patch name called " VC_Redist_14.27.29016.0_x64.exe then click on Plus sign to add the patch for deployment.


Click on the Finish button as soon as the patch is added.

creating Patch group4.1.png

This confirmation screen will pop-up.


This is asking us if we want to continue with the default schedule or want to schedule the deployment whenever we want.


- Using Yes, will immediately deploy the patch to the affected devices.

- Using No, it will allow you to when to schedule this deployment or on-demand.


I am going with Yes because I want to schedule these now.

also select the Go to Patch group which will take us to this newly created Patch group.


On the Patch group, it will download the patch and deploy it to the devices.



b) Patch Jobs is dynamic in nature and it adds the patches and deploy them automatically as per the patch job scheduler. The patch job is created based on patch criteria and types.

Once the patches are installed using Patch jobs or groups the clients will be sending the resulting patch inventory files using an upstream module of Clients parent relay to the Master server for inventory integration and reevaluation for the result.


We are going to see these deployments in the next Blog



Viewing the progress using the Reports:


BCM does have out of the box reports for the Patching. To view these reports from the BCM Console go to the Report node and out of the box folder.

From Patches folder


Here are some best practices for Patch management:


Patching devices in a disconnected environment:


Thank you for reading this Blog

Share This:

Following the lead of the BMC Community, I want to send a special thanks to our top participants in the Client Management community for showing us the love every day!

Thank you for sharing your expertise and participating in our community.  Steve Gibbs Julien Devienne Dominik Kress Philipp Ernicke Fabien Carmagnolle Akash Vekhande Marvin Schumacher Alex Vargas Sameehan Joshi

BMCheart.JPG bcmtopparticipants.JPG

Share This:

We are very excited to announce the release of version 12.9 with new features and enhancements to existing features!


Some highlights of the release include:

  • The ability to record remote control sessions
  • The addition of inventory and direct actions to the web console
  • Enhancements to patch management, operational rules, and security settings


Check out the new documentation for all the details and videos on the new features.

Release notes and notices - Documentation for BMC Client Management 12.9 - BMC Documentation


Visit the epd site to download the latest version on your site or submit a support request to upgrade your BMC SaaS environment.

Share This:

Important notice for BMC Client Management customers using patch management

If you are using patch management, you will need to upgrade to BCM version 12.8, patch 3 in order to continue to receive new patches as of March 31, 2020.

Versions of BMC Client Management earlier than 12.8 patch 3 use the Ivanti Patch SDK 9.2 . The 9.2 version of Ivanti Patch SDK is not supported after 31 March 2020.

To ensure that the BMC Client Management patch management module continues to receive new patches, you must upgrade to BMC Client Management version 12.8, patch 3 or higher before 31 March 2020.

Versions of BMC Client Management earlier than 12.8, patch 3 will not receive new patches for the patch management module after 31 March 2020.…

Share This:

Want to provide input on new developments before we release them?

We are looking for partners and customers to be a part of our BMC Helix Client Management 12.9 beta.


Some areas that we plan to include in the beta program are:

Recording remote control sessions, enhancements to the web console, patch management, and operational rules.


We are looking for participants who can attend beta review calls, test new features, be active in our Communities group (ask questions, provide input, post issues), and complete the beta survey.


Ready to apply?  Get details here:

Share This:

IMPORTANT NOTE: The current releases of BMC Footprints and BMC Remedyforce are not compatible with BMC Client Management 12.8 patch 2, due to the introduction of the new BMC Client Management web start installer.

If you are using BMC Remedyforce with BMC Client Management on premises, you will want to wait to apply this patch until you have upgraded to Remedyforce Winter19, otherwise you will not be able to launch the BCM console from Remedyforce.

If you use BMC FootPrints with BMC Client Management, you must wait until the release of BMC FootPrints version 20.19.01 before upgrading to BMC Client Management 12.8 patch 2 in order to launch the BCM console from BMC FootPrints.



A new patch for BMC Client Management versions 12.8, 12.7, and 12.6 is available. The patch introduces a replacement for Java Web Start. Download the latest patch release from the Products tab of BMC EPD on the BMC Support Central website.


For more information, please refer to the release notes:

BCM version 12.8:

BCM version 12.7:

BCM version 12.6:

Share This:

Background: Oracle has recently announced changes to the licensing policy and release cadence of Java software. How do these licensing changes affect the BMC products that use Java Standard Edition (SE)?  


For more information about the announcements related to Oracle Java licensing policy and release cadence, see the following articles:



Oracle Java Licensing Changes

Oracle recently announced a major change to their licensing policy and release cadence for Java SE (Standard Edition including both JDK and JRE).

Traditionally Oracle Java SE technologies (commonly referred as Java 6, Java 7, Java 8 etc) were available for production deployments without need for any licensing or support arrangements with Oracle (BCL licensing). Also, public updates to Java ensured that periodically Customers would be able to upgrade Java to a secured and updated version.

Oracle has moved Java SE to a Long-Term-Support (LTS) release model beginning with Java 11 ("18.9 LTS"). This Oracle JDK 11 (and higher versions in future) will be available to Oracle Customers under commercial support contracts (Long-Term-Support) for production deployments. Enterprises that prefer stability, so that they can run multiple large applications on a single shared Java release, can use the current long-term support release. Commercial support (Long-Term-Support) will be available for 5 years (+ 3 years extended support) after an LTS release and include periodic updates which may include security and performance fixes. Also, Enterprises can plan ahead to migrate from one long-term support release to the next, every three years.

Oracle has stated that customers can remain on the non-LTS release that is publicly available for 6 months; however, after 6 months the customers must upgrade to the latest release. Oracle will no longer provide public updates or security vulnerability updates for earlier releases. Customers who require more stability and cannot align to an upgrade cadence after every 6 months, can use the Commercial Premier Support that provides security vulnerability upgrades for earlier releases. Commercial Premier Support will be available for 5 years after an LTS release.

Use of Java within BMC Client Management

BMC Client Management currently includes Oracle Java (JRE) for some server processes and the Administration Console.

To minimize impact of this Oracle licensing change to Client Management Customers, the application now includes support for open-source builds of the Java Development Kit, an implementation of the Java SE Platform under the GNU General Public License – commonly referred as Open JDK builds.

This support for Open JDK in BMC Client Management is effective with patches and versions provided from the January 2019 releases.

Open JDK is open source and production ready alternative (11.0.1 onwards) for Oracle JDK. Similar to getting Oracle Java SE binaries for free in the past, Customers can simply continue doing so with OpenJDK builds available at

This open source distribution OpenJDK has releases scheduled every 6 months. Customers must upgrade Open JDK to the latest release every 6 months since Open JDK will no longer provide public updates for prior Open JDK releases (including security vulnerability updates).

BMC Client Management will ensure compatibility with latest Java versions by providing hotfixes. BMC will develop and deliver a replacement for Java Web Start, which will provide the same user experience for customers.

SaaS environments like Helix Client Management and Remedyforce Client Management will be updated by BMC Cloud Operations through planned maintenance updates. BMC will provide an update on how these changes will impact BMC products as soon as the update is available.


Important: Because OpenJDK is not supported on a 32-bit operating system, BCM Client Management can no longer be supported on a 32-bit master server.

Frequently Asked Questions

Question: Traditionally Open JDK lacked some features present in Oracle JDK. Will lack of these features/capability impact my BMC Client Management application?

Answer: Along with change in licensing and releases, Oracle also committed to make Open JDK and Oracle JDK ‘Functionally identical and interchangeable’ starting Java 11 (Reference - Same reference page also list small number of differences in these JDK builds that are continued even with Java 11.

Based on this assurance from Oracle and our lab test results, we have not seen any functional or performance impact when using Open JDK 11 for BMC Client Management deployment.


Question: There is no reference to support for Java 9 or Java 10 here? Can you clarify if these are supported for BMC Client Management deployments?

Answer: Java 9 or Java 10 are not supported for any version of BMC Client Management. These versions followed 6 month release cadence and are now superseded by Java 11.


Question: Can I continue to use Java 8 when using BMC Client Management? Why should I upgrade to a new Java version?

Answer: BMC Client Management will allow backward compatibility for applications running on Java 8. However also note that Oracle has announced end of public updates for Java SE 8 beginning January 2019 for Commercial Users. Only customers with Premier Support from Oracle will get updates to Java SE 8 from Oracle. For others, continued use of Java 8 beyond January 2019 may leave your system open for security vulnerabilities or performance issues among other things. More details here -


KnowledgeArticle - BMC

Share This:

Happy Holidays! Here is a little gift for you.

We have released BMC Client Management version 12.8 with all kinds of new and enhanced goodies inside.



Before upgrading, be sure to check the value of the parameter RemoveOldPackages located in data/Vision64Databse.ini file to ensure it is set to false in order to retain your existing custom packages.


Highlights of the release include:

  • New remote control on request capability to provide remote control for users without the BCM agent installed.
  • New Security checklist to help customers ensure they have enabled the security levels they want
  • Enhancements to operational rules, patch management, centralized credentials
  • FIPS-140-2 support for Federal government customers
  • and more!

Get all the details here 12.8 enhancements - Documentation for BMC Client Management 12.8 - BMC Documentation

Share This:

We have released new patches for BMC Client Management versions 12.7, 12.6, and 12.5, which introduce Enhanced Security, a new secure mode for reinforcing the security of communications between BCM agents. The patches also provide a number of fixes for known defects.

See the following pages for more information:

Share This:

Hello BMC Client Management community!


I wanted to make you aware that we have replaced this package posted in the Patches tab because it was the full installer instead of just the patch file.

BMC Client Management Windows (x64) Master Patch ( .


Thank you for your patience as we uploaded the correct file.

Share This:

We are changing some support dates for certain versions that will be an exception to the general BMC support policy.


Due to the obsolescence of some 3rd party components included in these versions, we are making the following changes:

  • BCM v12.5 will enter Limited Support status on December 31, 2018, because after this date, BMC is not able to provide patch management content updates for this version
  • BCM v12.1 and v12.5 end of version support will be aligned to v12.0. Limited support for these versions will therefore end on September 23, 2019


Please visit the Supported Versions of BMC Client Management page for details on BMC Client Management version support dates.


What is Limited Support?When a Product release enters Limited Support:

  • New enhancements will not be made to the version or release.
  • Customer Support will direct customers to existing fixes, patches, or workarounds applicable to the reported case.
  • BMC Software will develop new hot fixes for problems of high technical impact or business exposure for customers. With customer input, BMC Software will determine the degree of impact and exposure and the consequent activities.
  • Customer Support will direct customers to upgrade to a more current version, release, or service pack of the product.
  • The Patch Knowledge Base will not be updated anymore
  • The Software Catalog will not be updated anymore
  • The Security Product Knowledge Base will not be updated anymore


Upgrading BMC Client Management

We strongly recommend that you upgrade if you are on any previous versions of BMC Client Management 11.x, 12.0, 12.1, or 12.5. For details about the upgrade procedure, see the Upgrading BMC Client Management page.


Getting assistance

If you have any questions about the support update, please visit BMC Support Central, contact BMC Software Customer Support at  800 537 1813 (United States or Canada) or call your local support center.

Share This:

Important Notice for Client Management customers using software catalog feature of the compliance module


A new software catalog from Flexera has been implemented in the BMC Client Management 12.7 release. The Flexera Application Recognition library replaces the previous catalog. The Flexera Application Recognition library provides a normalized software catalog with standard naming conventions used to identify software publishers and titles. This new software catalog knowledgebase includes software content for Windows, Mac OS, and Linux applications.


Call to action for customers

To continue to receive updates to the software catalog knowledgebase, customers need to upgrade to version 12.7 or apply a hotfix for versions 12.1, 12.5 and 12.6. All files are available at


BMC encourages customers relying on Client Management’s software catalog capabilities to upgrade or apply the cumulative hotfix at their earliest convenience.


Reason for the change

The last software catalog update was released on January 2, 2018 and will be available until March 31, 2018. While the existing software catalog detection will continue to function, it will do so without access to new software catalog titles released after January 2, 2018. 


If the hotfix or upgrade is not applied, customers will no longer receive updates to the software catalog knowledge.

Filter Blog

By date:
By tag: