Default language.

Unsupported content This version of the product is in limited support. However, the documentation is available for your convenience. You will not be able to leave comments.

Known and corrected issues in patches for version 12.6

The BMC Client Management patches are cumulative, so the latest patch includes all the issues fixed in the previous patches. Irrespective of the last patch you applied to your BMC Client Management environment, you can directly apply the latest patch.

Note

Before you apply a patch, do the following:

  • Backup database and the master installation folder in order to be able to revert if the patch update fails.
  • After upgrading, first update the patch knowledge base before using the patch management module. Until the patch knowledge base is updated, only the Configuration node is populated under the Patch Management node.

Patches for BMC Cloud hosted BMC Helix Client Management

For BMC Cloud hosted BMC Helix Client Management, patching is undertaken by BMC. The table below, shows information on the scheduling of such patches.

Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.

Patch 8 for version 12.6 (200428l)

The following issues were addressed in Patch 8 for BMC Client Management version 12.6.

Patch 7 for version 12.6 (191104u)

The following issues were addressed in Patch 7 for BMC Client Management version 12.6.

Patch 6 for version 12.6 (190507j)

The following issues were addressed in Patch 6 for BMC Client Management version 12.6.


Patch 5 for version 12.6 (190124l)

Patch 5 for BMC Client Management version 12.6 introduces a replacement for Java Web Start.

Oracle recently announced a major change to their licensing policy and release cadence for Java SE (Standard Edition including both JDK and JRE). BMC Client Management earlier included Oracle Java (JRE) for some server processes and the Administration Console. To minimize impact of the new Oracle licensing change for users, BMC Client Management now provides support for open JDK through the web start installer. The web start installer is a replacement for Java Web Start, and provides the following advantages:

  • Provides an easier way to install the BMC Client Management Console, with fewer installation steps.
  • Ensures that the console is always up-to-date. 

Note

BMC Client Management supports OpenJDK only on 64 bit environments. BCM Java console cannot be launched on 32 bit platforms because they are no longer supported.

If you use BMC Remedyforce or BMC FootPrints with BMC Client Management, you must wait until the release of BMC Remedyforce Winter 19 or BMC FootPrints version 20.19.01 before upgrading to BMC Client Management 12.6 patch 5 in order to launch the BCM console from BMC Remedyforce and BMC FootPrints. The current releases of BMC Footprints and BMC Remedyforce are not compatible with BMC Client Management 12.6 patch 5, due to the introduction of the new BMC Client Management web start installer.

For more information, see Downloading-and-installing-the-BMC-Helix-Client-Management-console.

The following issues were addressed in Patch 5 for BMC Client Management version 12.6.

Patch 4 for version 12.6 (180813m)

The following issues were addressed in Patch 4 for BMC Client Management version 12.6. Issues requiring more details include a hyperlink to the Knowledge Base article.

Some security related defects were also fixed.

Patch 3 for version 12.6 (180214o)

New software catalog

The software catalog in BMC Client Management 12.6 has been replaced in patch 3 with the Flexera Application Recognition library. Flexera provides a normalized software catalog with standard naming conventions used to identify software publishers and titles. The Flexera software catalog supports Windows, Mac OS, and Linux applications.

Upgrade considerations

The following notices relate to the replacement of the ExpressMetrix software catalog with the Flexera software catalog in patch 3 of BMC Client Management 12.6:

  • ExpressMetrix applications cannot be mapped with Flexera applications. After the master server is upgraded the Software Catalog inventory is purged to the BCM database.
  • If you are using the BMC Atrium CMDB integration:
    • During the first import in the CMDB after master server is upgraded, all applications are regarded as new.
    • Customers need to launch the  Delete Software job to delete the old entries, then the Reconciliation & Merge job and finally the Purge job.
  • After an upgrade the existing application lists with Catalog objects are automatically updated with the new Custom Applications. 
    You must manually update the Licensed Software linked to Software Catalog.
  • With the new software catalog, applications lists are now restricted only to Client Management objects. Catalog objects are no longer supported.
  • The suites have been removed from software catalog. It is possible to replace them with another item: application or license via a tool that can be launched from console dashboard or from Software catalog node.

The following issues were addressed in Patch 3 for BMC Client Management version 12.6. Issues requiring more details include a hyperlink to the Knowledge Base article.

Patch 2 for version 12.6 (171219w)

The following issues were addressed in Patch 2 for BMC Client Management version 12.6. Issues requiring more details include a hyperlink to the Knowledge Base article.

Patch 1 for version 12.6 (170915o)

The following issues were addressed in Patch 1 for BMC Client Management version 12.6. Issues requiring more details include a hyperlink to the Knowledge Base article.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*