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.
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.
The following table provides information on the January 2020 patch deployment for BMC Cloud hosted BMC Helix Client Management.
|Region||Date for patch deployment on |
Date for patch deployment on
|EMEA||10 January 2020||18 January 2020|
|USA||10 January 2020||18 January 2020|
200428l)Patch 8 for version 12.6 (
The following issues were addressed in Patch 8 for BMC Client Management version 12.6.
|Update OpenSSL to version 1.0.2u.|
Update OpenJDK to version 14.
|Change the version numbering to detect the minimum version for the console.|
Patch 7 for version 12.6 (191104u)
The following issues were addressed in Patch 7 for BMC Client Management version 12.6.
|Update OpenJDK to version 13.|
|Java Web Start console fails to launch with an error.|
|DRZKZ-4203||Remove the SCAP validation tool.|
)Patch 6 for version 12.6 (190507j
The following issues were addressed in Patch 6 for BMC Client Management version 12.6.
|A Patch Job does not start at the scheduled time because the client devices have not received the latest master list.|
|DRZKZ-2837||The Java Web Start console does not work on Mac OS since the implementation of OpenJDK.|
A patch installation might run three hours after the patch window has been terminated. This can happen if the patch installation is cancelled while the patch window was ongoing.
Update OpenJDK to version 12.
|DRZKZ-2842||Logging into 12.6 190124l web console is not possible.|
|DRZKZ-2494||Patch scan fails on Windows Device with SQL server 2008 R2.|
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.
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.
If you do not update a Windows 7 device before installing the driver for Remote Control module on it, the installation fails reporting an unknown encryption error in the driver's signature certificate.
If a files that is packed in an archive file cannot be extracted, the remaining files too remain in the File Store folder.
In general preferences for patch Group Wizard, the Reboot after Deployment setting is overlooked.
Cannot use Gmail as the mail server for the organization.
Cannot enroll mobile devices through Mobile Device Manager (MDM) server.
Mobile Device Management (MDM) server fails to enroll the mobile devices, and displays the error message enrollment failed or authentication failed.
|DRZKZ-2385||The logged in user's details are missing on Linux operating system.|
Cannot use environment variables in configuration fields for MSI package.
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.
Tunnel between Master and MDM Manager is not recreated after it is closed.
|DRZKZ-2148||Asset discovery might occasionally fail to parse Nmap result file and return all targets as "Unreachable".|
|DRZKZ-2213||Although the agent is started and synchronized with its relay, sometimes, the Direct Access fails.|
|DRZKZ-2070||Remote Control frequent disconnections|
|Occasionally the BCM master services crash.|
|DRZKZ-2246||After you rename the MSI package, you cannot modify the MSI package installation options.|
|DRZKZ-2033||For some object types, SendTime is not reset when changing status to "Unassign Waiting".|
|DRZKZ-1719||If the value for Patches is set as = in the vision64database.ini file, the status of the Patch Group on the Patches tab is not updated.|
|DRZKZ-2313||The OpenSSL version used in BMC Client Management has been upgraded to OpenSSL 1.0.2o.|
|DRZKZ-2069||License status randomly changes to "Invalid".|
|DRZKZ-2316||Unable to collect the IsVirtual information because the opswatproxy parameter is not available.|
|DRZKZ-2134||In a query preview, the date format does not reflect user preferences. The Year part is displayed with 1 or 2 digits.|
|DRZKZ-2239||Windows 10 devices shows Type as "Server".|
|DRZKZ-2140||The Windows Update Status remains empty even after the Security Settings Inventory and Security Product Inventory are updated.|
|DRZKZ-2049||The "Force Reboot if Session is locked" parameter has no effect.|
|DRZKZ-2045||In some cases, the Patch Group installation options displayed on the BCM Console may not be the values used by assigned devices.|
|DRZKZ-584||Service Packs and Patches installed by using a Patch Management have an incorrect installation date.|
|DRZKZ-1768||BCM 12.6 Patch deployment Jobs and Groups do not populate the installation date column in Installed Patch Inventory records.|
|DRZKZ-2057||Sub report data is processed by waves of 1000 items (internal hard coded value).|
|DRZKZ-2346||The Patch inventory node displays two different values for missing patch count.|
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.
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.
Dashboard messages should accurately reflect the type of license and display warnings accordingly.
After installing Patch 2 for 12.6 the JNLP console fails to open. The error message is
Clicking a device FAM node in the Console right panel has no effect. The previous panel remains.
Server devices are shown as laptops in some cases.
The Package Wizard fails with the following error:
Random crash on several clients.
A mtxopswatproxy process takes 100% of CPU on macOS devices.
Status updates for a large number of Device IDs can cause a fault in the MS SQL Query planner in some cases.
Rollout changes the status to Configuration Failure when the rollout file has active handle because the file BCM_Agent_Install.exe cannot be deleted.
Some Operational Rule Steps use non-standard default values which, in some cases, can cause performance degradation.
Random error is logged while extracting opswat archives.
The Application Monitor does not always detect applications start and stop actions.
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.
|Issue Number||Issue Description|
|DRZKZ-1637||Network Discovery scans evaluating SNMP OIDs may consume large amounts of memory in some cases.|
|DRZKZ-1557||Clients will not switch to backup relay even if the relay list is not reachable.|
|DRZKZ-1585||User Management Step does not account for Windows Passwords that contain 14 or more characters|
|DRZKZ-1636||BMC Client Management 12.6 Master stops responding when 2-way integration is creating a ticket in Footprints.|
|DRZKZ-730||OSD synchronization process does not always complete as expected|
The scan wizard automatic mode encodes the password twice. As a result the scan cannot be assigned to the asset discovery scanner.
|DRZKZ-1282||MacOS High Sierra 10.13 is detected as Mac OS X.|
The BCM SCAP tool did not load the Version field. The Fix Text field is loaded but is not populated.
Patch pre-installation messages are displayed every minute when package creation fails.
|DRZKZ-1064||The Restart Agent step does not restart the service if it is locked.|
When multiple Transforms are provided, the MSI package fails because the second Transform fails to get the complete path to the transforms file.
|DRZKZ-1788||BMC Client Management service does not restart during the hotfix process.|
Update INI file step modify target file encoding.
When Rollout identifiers for similar packages are not synchronized correctly between the Master and the Rollout servers, the Rollout package is not deployed.
Screen monitor Reports having multiple space in .csv format/serial number of different monitors are same.
Monitor names with multiple spaces in the .csv file or serial numbers are displayed as the same in the Screen monitor reports.
|DRZKZ-1626||Patch files are not deleted from the target devices when running the Patch Groups.|
|DRZKZ-1571||The language label 041 (Croatian) is not provided in the BCM Patch management wizard.|
|DRZKZ-1211||Mismanagement of OS Deployment Repository Cache Deltas in some cases results in additional storage consumption.|
Chipset deployment drivers cannot be selected as needed in some OS Deployment use cases.
|DRZKZ-975||The Application Synchronization Op Rule Step causes database errors.|
|DRZKZ-1727||Some service packs are missing in the patch management knowledge base.|
|DRZKZ-123||Java 8 no longer creates shortcuts JNLP|
|DRZKZ-1882||Service Packs are deleted from PatchLanguages and PatchGroupAssignedPatches when Master needs to send a MasterList.|
|DRZKZ-1873||A java exception is encountered when displaying free query result with PatchReleaseDate field.|
|DRZKZ-1852||Reports cannot be opened in Firefox.|
|DRZKZ-1742||BMC Client Management Blue Shield icon is not displayed in the notification tray.|
BMC Client Management service can be started multiple times on a Linux system.
Add a log message on bulk errors (ODBC driver)
Need more details here.
Patch job template based reports are not displayed in the report portal.
|DRZKZ-1971||When you delete an existing administrator, the object and access rights are not transferred to any other selected administrator.|
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.
|Issue Number||Issue Description|
|DRZKZ-1572||After upgrading to 12.6 Patch Management Database update fails on Patch Manager with Bulk Products Error|
|DRZKZ-1579||Mtxagent.exe crashes because ORA-01000 : maximum open cursors exceeded, during 12.6 upgrade|
|DRZKZ-1564||SQL Errors on Patch Job evaluation after 12.6 upgrade and first Patch KB update|
|DRZKZ-1560||After upgrade 12.5 -> 12.6, it is impossible to change the patch manager|
|DRZKZ-1563||SQL error on PatchLanguages table during 12.6 upgrade|
|DRZKZ-1589||Some patches downloaded previously to the upgrade are not installable|
|DRZKZ-1590||Service pack Ids are not matching anymore after upgrade to 12.6|
|DRZKZ-1623||Implement 3 new Web Services to manage Financial relations|
|DRZKZ-1151||Unattended.xml file is truncated because created at same time a reboot is performed|
|DRZKZ-623||BMC Client Management upgrade or hotfix fails if The BCM service did not respond to the start or control request in a timely fashion.|