Known and corrected issues in patches for version 12.8
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 7 for version 12.8 (210427i)
The following issues were addressed in Patch 7 for BMC Client Management version 12.8.
Issue Number | Issue Description |
---|---|
DRZKZ-6236 | Update OpenJDK to version 16. |
DRZKZ-6111 | Every time the master service starts, after upgrading to version 20.08.01, a warning message about the SQL errors is displayed. |
Patch 6 for version 12.8 (201022k)
The following issues were addressed in Patch 6 for BMC Client Management version 12.8.
Issue Number | Issue Description |
---|---|
DRZKZ-5714 | Update OpenJDK to version 15. |
Patch 5 for version 12.8 (200429l)
The following issues were addressed in Patch 5 for BMC Client Management version 12.8.
Issue Number | Issue Description |
---|---|
DRZKZ-5051 | Update OpenSSL to version 1.0.2u. |
DRZKZ-5199 | Update OpenJDK to version 14. |
DRZKZ-5108 | Change the version numbering to detect the minimum version for the console. |
DRZKZ-4671 | Some UserAccess requests can lock the communication threads, as a consequence, connection on the Master system is no longer possible. |
DRZKZ-4672 | A new parameter DeadLockTimeOut (mtxagent.ini/Threads) is added to configure the timeout for the deadlock detection. Its default value is set to 6 hours. |
DRZKZ-2556 | After upgrading to BMC Client Management version 12.6, most of the OOTB template-based PDF reports are incomplete and have some other issues. |
DRZKZ-5143 | Auto-deployment of the BMC Client Management agent creates a new installation hash every time it creates a package. |
DRZKZ-5156 | When you retry to transfer a build package to a device, the transfer stops at offset 4294967296. |
DRZKZ-4257 | Improve the patch queries execution time due to languages table. |
DRZKZ-5256 | Add a support for the UK English language in Patch Management. |
DRZKZ-5097 | Patch groups are installed without considering the timer. |
DRZKZ-3104 | Review superseded patches management. A new option is added on the superseding popup. Now it is possible to:
A new menu has been added under a device group inventory to add patches directly in a patch group without using the wizard. |
DRZKZ-3759 | Add support for macOS Catalina (10.15). |
DRZKZ-2550 | Postponing the reboot forever without taking care of the allowed postpone count value is possible. |
Patch 4 for version 12.8 (191031p)
The following issues were addressed in Patch 4 for BMC Client Management version 12.8.
Issue Number | Issue Description |
---|---|
DRZKZ-3046 | Patch jobs never execute if they contain patches in a language that the module does not support. |
DRZKZ-3047 | Need support for Ukrainian (code 0422) and some other languages for patches. |
DRZKZ-2576 | Dots are no longer allowed in package names since 12.7 hotfix 2. |
DRZKZ-3035 | Mtxagent.exe fails on ORA-01000: maximum open cursors exceeded. |
DRZKZ-2932 | Connectivity inventory is not uploaded with SNMP V3. |
DRZKZ-3083 | SNMP V2 inventory scans fail if a user is set in the SNMP credentials. |
DRZKZ-3068 | The timeout for SNMP scans is in milliseconds instead of seconds. |
DRZKZ-3069 | The Unconnected Devices Inventory no longer displays information messages in BMC Client Management UI, though the inventory is collected. |
DRZKZ-3025 | The patch status cannot always be updated. |
DRZKZ-3043 | The patch installation date is not always correct. If several attempts are made before a successful installation, only the first attempt date is stored. |
DRZKZ-3688 | Update OpenJDK to version 13. |
DRZKZ-3758 | PUT /discovery/scan/configuration/{configurationId}/protocols does not correctly set SNMP credentials. |
DRZKZ-3087 | Change default options for Patch Job Detail by Patch and by device template reports to reduce their size. |
DRZKZ-3079 | Reboot is not detected when the Windows build 1903 is applied because some services start with a delay. |
DRZKZ-2969 | Upgrade of Windows 10 devices with Encryption. |
DRZKZ-3100 | After deleting any 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-3957 | The patch installation fails because the 'OfflineStatus' attribute is not managed by the mtxpatch module. |
DRZKZ-3532 | The relay selection by DHCP mechanism sometimes does not work. |
DRZKZ-3689 | The EventLogManager Module Setup step cannot modify the Minimum Upload Gap parameter if the value is already set to 0. |
DRZKZ-3007 | Security Products Management fails if a category is unknown. |
DRZKZ-2776 | Keyboard is not responsive on the PXE menu on some computers. |
DRZKZ-3301 | Deprecation of the devices does not work when we select the Agent uninstall option as the window remains after you select OK. |
DRZKZ-2743 | Java web start console fails to launch with an error. |
DRZKZ-4141 | AcknowledgeTime is spelled AcknowlegdeTime in a query that unassigns a transfer window. |
DRZKZ-2702 | BCM service stops on Master after a deadlock is detected. |
DRZKZ-3018 | Tunnel connection can be closed in case of communication error. |
DRZKZ-3754 | Relays do not correctly handle tunnel recreation. |
DRZKZ-2624 | Mouse cursor does not appear when remote controlling a device with no display and mouse connected physically. |
DRZKZ-3117 | While creating a custom package, if we edit the destination path to .../ from ../, it creates a new master/client link with the name 'Master.' and 'Client.' respectively in the root directory. |
DRZKZ-4128 | Unable to install BMC Client Management profile on iOS 13.1. |
DRZKZ-4203 | Remove the SCAP validation tool. |
DRZKZ-3759 | Need support for MacOS Catalina version 10.15. |
Patch 3 for version 12.8 (190606k)
This section details important changes for BMC Client Management customers using patch management, and the additional issues addressed in BMC Client Management version 12.8, patch 3.
Important notice for BMC Client Management customers using patch management
BMC Client Management currently uses Ivanti Patch SDK 9.2 as its patching system. 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.
Issues resolved
The following issues were addressed in Patch 3 for BMC Client Management version 12.8.
Issue Number | Issue Description |
---|---|
DRZKZ-2650 | You can no longer use the Google mail server. |
DRZKZ-2680 | Unable to expand POST/device/{deviceID}/Windows/service while using API. |
DRZKZ-2329 | User Account List step never ends if 'Profile sizes' is requested. |
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-2760 | The 'Restore Directory' step does not work if the 'backup on relay' option is selected. |
DRZKZ-2796 | Compatibility 12.0 -> 12.8: Operational Rule status are not updated. |
DRZKZ-2782 | The custom inventory is not inserted into the database. |
DRZKZ-2388 | The agent service crashes on Relays if the package is deleted from the Console. The file is partially downloaded under '..\data\FileStore\downstream\OperationalRulePackage'. Deleting the file from the same location resolves the issue. |
DRZKZ-2741 | The keyword '_MESSAGE_CLOSEWEBPAGEDONE_' has not been translated after providing the response on the output of the step 'Send Customized Form'. |
DRZKZ-2672 | BCM system accounts are locked unexpectedly. |
DRZKZ-2820 | The 'Account Locking Attempts' and 'Automatically Unlock Account' values can be set as blank in BMC Client Management version 12.8. |
DRZKZ-2753 | SaaS customers can no longer send emails. |
DRZKZ-2311 | Implement Ivanti SDK 9.3. |
DRZKZ-2520 | If parent and child dynamic device groups use the same query, and that query was subsequently deleted, you cannot remove devices from the group. |
DRZKZ-2707 | The patch installation date information is deleted from the database when full patch inventory is uploaded. |
DRZKZ-2702 | The BCM service stops on the Master after a deadlock is detected. |
DRZKZ-2754 | Bad name in the console for Windows 2019 Server. |
DRZKZ-2806 | Type is shown as Workstation instead of Laptop for Ubuntu laptop. |
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-2843 | Update OpenJDK to version 12. |
DRZKZ-2844 | If more than one SNMP communities are updated in the scan configuration, then only one community is used to scan the target devices. |
DRZKZ-2660 | Changing DefaultTimeout in mtxagent.ini is not possible. The value is set to 300 seconds by default. |
DRZKZ-2903 | IP Address is not updated when network configuration is changed on client device. |
DRZKZ-2942 | SQL execution error while running a report when we include FAM columns on 12.7/12.8. |
DRZKZ-2947 | Patch execution pending for patches because of language code 080a. |
DRZKZ-2797 | The 'Send Customized Form' step fails if the 'Retry interval' field is greater than the default timeout for the TCP communications. |
DRZKZ-2962 | Search on bulletins by products fails because the multi-part identifiers p.PatchName and p.PatchID could not be bound. |
Patch 2 for version 12.8 (190124r)
Patch 2 for BMC Client Management version 12.8 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 12.8 patch 2 and later uses OpenJDK which is only supported on 64 bit platforms. 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.8 patch 2 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.8 patch 2, 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 2 for BMC Client Management version 12.8.
Issue Number | Issue Description |
---|---|
DRZKZ-836 | In a few instances, the device type for Linux servers is displayed as Workstation instead of Server. |
DRZKZ-2658 | The User Message Box steps are available only if you have a Software Distribution license. |
DRZKZ-2639 | While rolling out an agent, a few files remain in the temporary folder /tmp or C:\Windows\Temp depending on the platform. As a result, the temporary folder is filled quickly and affects the server performance on devices that host multiple master instances. |
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-2636 | When you access a Windows 2012 R2 server through a remote control session and press the CTRL+ALT+DEL key sequence, no action is performed. |
DRZKZ-2645 | While upgrading a SQL server, a few views are not created because the database schema is different than the user's database schema. |
DRZKZ-2649 | Cannot install the BMC Client Management Console by using a Windows installer (MSI) package. |
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-2668 | The Connected Consoles node does not display a complete list of consoles and console administrators that are connected to the BMC Client Management Master server. |
Patch 1 for version 12.8 (181122n)
The following issue was addressed in Patch 1 for BMC Client Management version 12.8.
Issue Number | Issue Description |
---|---|
DRZKZ-2626 | After you upgrade to BMC Client Management version 12.8, the master server fails to start at the first start up because the upgrade packages are not created. |
Comments
Log in or register to comment.