Known and corrected issues in patches for version 12.7
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.
For download instructions, see Downloading the installation files. To apply the patch, see Applying a patch to BMC Client Management.
Note
Before you apply a patch, ensure that you do the following:
- Backup the database and the master installation folder 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.
July 2021
The following table provides information on the July 2021 patch deployment for BMC Cloud hosted BMC Helix Client Management. We perform the patching operation between the hours of 04.30 and 09.30 UTC.
Region | Date for patch deployment on Sandbox environments | Date for patch deployment on | ||
---|---|---|---|---|
EMEA | 3 July 2021 | 10 July 2021 | ||
USA | 4 July 2021 | 11 July 2021 |
Patch 8 for version 12.7 (201022i)
The following issues were addressed in Patch 8 for BMC Client Management version 12.7.
Issue Number | Issue Description |
---|---|
DRZKZ-5097 | Patch groups are installed without taking the timer into account. |
DRZKZ-5714 | Update OpenJDK to version 15. |
Patch 7 for version 12.7 (200428r)
The following issues were addressed in Patch 7 for BMC Client Management version 12.7.
Issue Number | Issue Description |
---|---|
DRZKZ-5051 | Update OpenSSL to version 1.0.2u. |
DRZKZ-3688 | Update OpenJDK to version 14. |
DRZKZ-5108 | Change the version numbering to detect the minimum version for the console. |
DRZKZ-5156 | When you retry to transfer a build package to a device, the transfer stops at offset 4294967296. |
Patch 6 for version 12.7 (191105l)
The following issues were addressed in Patch 6 for BMC Client Management version 12.7.
Issue Number | Issue Description |
---|---|
DRZKZ-3688 | Update OpenJDK to version 13. |
DRZKZ-3100 | After deleting the patches from a patch group or a patch job, the deleted patch files are still displayed at the Client directory on the Client devices. |
DRZKZ-3532 | The relay selection by DHCP mechanism sometimes does not work. |
DRZKZ-3007 | The Security Products Management fails if a category is unknown. |
DRZKZ-2776 | Keyboard is not responsive on the PXE menu on some computers. |
DRZKZ-2969 | Upgrade of Windows 10 devices with Encryption. |
DRZKZ-2624 | Mouse cursor doesn't appear when remote control on a device with no display and mouse connected physically. |
DRZKZ-2743 | Java Web Start console fails to launch with an error. |
DRZKZ-3025 | Patch statuses cannot always be updated. |
DRZKZ-2426 | SQL Execution Error on Report After 12.7 Upgrade. |
DRZKZ-4203 | Remove the SCAP validation tool. |
Patch 5 for version 12.7 (190515j)
The following issues were addressed in Patch 5 for BMC Client Management version 12.7.
Issue Number | Issue Description |
---|---|
DRZKZ-2650 | You can no longer use the Google mail server. |
DRZKZ-2734 | Wallpaper is not always deactivated during the Remote Control session. |
DRZKZ-2733 | Asset discovery for network devices (switches) does not retrieve full operating system details. |
DRZKZ-2740 | 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. |
DRZKZ-2834 | 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. |
DRZKZ-2385 | The logged in user's details are missing on Linux operating system. |
DRZKZ-2843 | Update OpenJDK to version 12. |
DRZKZ-2707 | The patch installation date information is deleted from the database when full patch inventory is uploaded. |
DRZKZ-2660 | Changing DefaultTimeout in mtxagent.ini is not possible. The value is set to 300 seconds by default. |
Patch 4 for version 12.7 (190124n)
Patch 4 for BMC Client Management version 12.7 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.7 patch 4 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.7 patch 4, 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 4 for BMC Client Management version 12.7:
Issue Number | Issue Description |
---|---|
DRZKZ-2658 | The User Message Box steps are available only if you have a Software Distribution license. |
DRZKZ-2609 | 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. |
DRZKZ-2547 | After the Patch Manager has published the patches, the patches remain in the To be downloaded status and are not deployed to the BMC Client Management Master server. Additionally, the status of the patch group is displayed as Build and Publish pending. |
DRZKZ-2629 | On a BMC Client Management Master server in a SaaS environment, the relay activity overlooks the Archiving of Downloaded Patches after Publication parameter setting. The patches are saved in the C:\ directory, instead of the default archived files location, causing higher than expected disk space use. |
DRZKZ-2652 | 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-2667 | After you upgrade to BMC Client Management version 12.7 Hotfix 2, the search for bulletins is very slow. |
DRZKZ-2520 | Cannot remove devices from dynamic device group if both the parent and child dynamic device groups used the same query and that query was later deleted. |
DRZKZ-2329 | The User Account List step does not stop running if the profile sizes are requested. |
DRZKZ-2680 | Cannot expand the POST/device/{deviceID}/Windows/service operation from the REST Web API service. |
Patch 3 for version 12.7 (181127q)
The following issues were addressed in Patch 3 for BMC Client Management version 12.7.
Issue Number | Description |
---|---|
DRZKZ-2526 | While integrating the Patch Inventory file on the Master server, a |
DRZKZ-2536 | Every time you try to upload the SCAP inventory, an SQL error message is displayed. |
DRZKZ-2494 | The Patch scan failed on Windows Device with an SQL 2008 R2 server. |
DRZKZ-2470 | When adding a new license software, the category drop-down box values are not sorted alphabetically. |
DRZKZ-2475 | The software inventory loops on the Application Data sub folder. |
DRZKZ-2447 | All Windows 10 devices that are scanned by the Asset Discovery, show the operating system as Windows XP instead of Windows 10. |
DRZKZ-2433 | If BCM tried to install multiple patches at the same time, only the first patch is installed. The installation of the rest of the patches fails and the following error message is shown:
|
DRZKZ-2395 | If one of the files from a PackedFile archive cannot be extracted, the other files are also not extracted. |
DRZKZ-2424 | After switching to a secure mode, the Diagnostic tools fails on PAC parameter. |
DRZKZ-2390 | Assets Discovery crashes when network queries do not return good number of result. |
DRZKZ-2482 | If the assigned rule is not executed yet, the Patch group status updates is sent after every minute. |
DRZKZ-1528 | When the UI option in an MSI package is set to Basic Hide Cancel, the resulting msiexec command line does not hide the Cancel button. |
DRZKZ-1862 | You cannot use environment as a variable in the Packager Configuration fields. |
DRZKZ-2078 | Environment variables fail program executions of MSI packages. |
DRZKZ-2438 | It is possible to inject information into the Java web start XML configuration file which might enable potential attackers to manipulate the data. |
DRZKZ-2452 | The macOS Mojave version 10.14 is not supported. |
DRZKZ-2517 | The pop-up windows on MacOS Mojave do not have text on the buttons. |
DRZKZ-1965 | After an unmanaged device assigned to a Patch Deployment transitions to a managed device, the device is not notified when a patch is assigned. |
DRZKZ-2389 | After a deployment, from Preferences in patch Group Wizard, the Reboot option is not considered. |
DRZKZ-2382 | Workflow is not always correctly handled for verification steps. |
DRZKZ-2388 | If the Package is deleted from the Console but, is partially downloaded, the Agent service crash on Relays. |
DRZKZ-2208 | The Nmap version is not updated to 7.70. |
DRZKZ-2621 | The OpenSSL is not updated to version 1.0.2p. |
DRZKZ-2635 | When using a remote UpdateManager, the software catalog is not updated on BMC Client Management version 12.7 Master server. |
Some security related defects were also fixed.
Patch 2 for version 12.7 (180813o)
Patch 2 for BMC Client Management version 12.7 introduces Enhanced security, a new secure mode for reinforcing the security of communications between BCM agents. Enhanced security enables the security of the restrictive SSL=3 mode (see Using SSL for Connections) for internal, agent to agent communication, but with simpler configuration.
Note
All agents must be upgraded to a version that supports enhanced security before you can enable it. See Enabling enhanced security for more information
You can use the new security checklist to get an overview of the communication security of your BCM environment, and see whether your environment is ready for enhanced security, and whether legacy bespoke cryptography or shared certificate authority is still in use in upgraded systems.
The following issues were addressed in Patch 2 for BMC Client Management version 12.7.
Issue Number | Description |
---|---|
DRZKZ-2407 | The Get patch details by machine report does not return any result for patches. |
DRZKZ-2346 | The Patch inventory node displays two different values for missing patch count. |
DRZKZ-2057 | Sub report data is processed by waves of 1000 items (internal hard coded value). |
DRZKZ-1379 | If you add a slash (\ or /) to a package name in the package factory, the package will not appear on the console but it will be stored in the SQLite database. |
DRZKZ-1499 | If the inventory is purged, the Hardware Inventory Last Update date is not updated as expected. |
DRZKZ-1533 | The Clean Security Settings Inventory step does not work. |
DRZKZ-1760 | If you copied a report, the logo selected in the original report is not retained. |
DRZKZ-2060 | You are unable to Add Package Files while creating the Custom Package by using the Package Creation Wizard and a value is added to the Folder field on Custom Package page. |
DRZKZ-2135 | If you purge the inventory then upload inventory again, the Custom Inventory Last Update field is not updated. |
DRZKZ-2140 | The Windows Update Status remains empty even after the Security Settings Inventory and Security Product Inventory are updated. |
DRZKZ-2201, DRZKZ-2364 | Occasionally the BCM master services crash. |
DRZKZ-2244 | If the package Publication folder is selected as a Sub-directory, each time the package is published, a warning message is shown even if the package has no changes. |
DRZKZ-2246 | After you rename the MSI package, you cannot modify the MSI package installation options. |
DRZKZ-2254 | The CVE IDs for some patches released patches are missing. |
DRZKZ-2296 | Passwords are stored without encryption in the operationalrules.sqlite database. |
DRZKZ-2313 | The OpenSSL version used in BMC Client Management has been upgraded to OpenSSL 1.0.2o. |
DRZKZ-2315 | Some Windows systems are incorrectly detected as switches by BCM Discovery. |
DRZKZ-2316 | Unable to collect the IsVirtual information because the opswatproxy parameter is not available. |
DRZKZ-2328 | If a screen is set to be displayed on top of the primary screen in the Windows Display properties, the Remote Control feature does not work. |
DRZKZ-2340 | If the PatchName is different from the Patchkey, the Patch Installation Date is not uploaded onto master server. |
DRZKZ-2345 | Due to case sensitivity, on an OpRule export, an SQL errors occurs. |
DRZKZ-2353 | If an operational rule failed before the patch group is executed, the system might crash. This issue occurred because of a missing variable in the query. |
DRZKZ-2357 | When trying to install certificate from the Console web page, a Java exception error occurs. |
DRZKZ-2361 | When you double-click on the jtable in the Application Monitoring module, a Java exception error occurs. |
DRZKZ-2368 | The USB keys are not disabled the first time you plug them. |
DRZKZ-2212 | Device groups are not properly assigned to patch jobs on Masters with Oracle. |
Patch 1 for version 12.7 (180531r)
The following issues were addressed in Patch 1 for BMC Client Management version 12.7.
Issue Number | Issue Description |
---|---|
DRZKZ-2063 | Dashboard messages should take into account the product license. |
DRZKZ-2087 | Customers without Software Catalog are still shown the software catalog upgrade warning after upgrade to 12.7. |
DRZKZ-2049 | The "Force Reboot if Session is locked" parameter has no effect. |
DRZKZ-1616 | Flexera Integration: Fixed 2 performance issues on software catalog for Oracle. |
DRZKZ-1211 | OS Deployment Repository Cache Deltas might in some cases require additional storage consumption. |
DRZKZ-2101 | Occasionally, agents stop processing incoming connections. |
DRZKZ-2004 | Regression detected on OSD Performance Load Test using Boot Listener for deployment using Unicast. |
DRZKZ-2086 | Tunnel between Master and MDM Manager is not recreated after it is closed. |
DRZKZ-2141 | Upgrade to 12.7 might cause OSD module and LDAP Client module to function improperly. |
DRZKZ-2148 | Asset discovery might occasionally fail to parse Nmap result file and return all targets as "Unreachable". |
DRZKZ-2088 | Op Rule Step fails to verify file existence on Linux. |
DRZKZ-2142 | Adding dependencies to operational rules is displayed incorrectly. |
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-2173 | 12.7 Relay List Server provides results that 12.6 and earlier agent cannot use. |
DRZKZ-2174 | 12.7 Master Server with a Relay List Upgraded from 12.6 provides results that 12.7 Clients cannot use. |
DRZKZ-2179 | 12.7 Relay List Automatic Synchro Timer Execution results in "Action RelayListSendSyncInfo is not registered" error. |
DRZKZ-2058 | Some relay list servers in an agent's communication node do not work. |
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-2183 | BCM 12.7 May result in Operational Rule Steps being marked as unavailable due to inaccurate license evaluation. |
DRZKZ-2033 | For some object types, SendTime is not reset when changing status to "Unassign Waiting". |
DRZKZ-2218 | Attempting to preview or view results for a report with a chart, results in the message "Subreport invalid". |
DRZKZ-2178 | Cannot add Master Server as Relay List Server in Remedyforce Provisioned BCM version 12.7 due to SaaS Mode Restriction. |
DRZKZ-2177 | BCM 12.7 Asset Discovery returns incorrect or blank data for DeviceType, HostID, Netbios Name, and Operating System Name. |
DRZKZ-2069 | License status randomly changes to "Invalid". |
DRZKZ-1730 | SCAP reports cannot be collected automatically. |
DRZKZ-2250 | Package publication failing. |
DRZKZ-2239 | Windows 10 devices shows Type as "Server". |
DRZKZ-2263 | FileStore DeleteThread : A transaction error may occur |
DRZKZ-2134 | In a query preview, the date format does not reflect user preferences. The Year part is displayed with 1 or 2 digits. |
Comments
Log in or register to comment.