BMC Client Management 21.02.02
- BMC Client Management 22.4
- BMC Client Management 21.02.02
- BMC Client Management 21.02
- BMC Client Management 20.08
- BMC Client Management 12.9
- BMC Client Management 12.8
- BMC Client Management 12.7
- BMC Client Management 12.6
- BMC Client Management 12.5
- BMC Client Management 12.2
- BMC Client Management 12.1
- BMC Client Management 12.0
- BMC Client Management
Learn what’s new or changed for BMC Client Management 21.02.02, including new features, urgent issues, documentation updates, and fixes or patches.
The following table lists the enhancements in this release:
To stay informed of changes to this list, click the icon on the top of this page.
|23 February 2022||Fixes a number of important defects.|
|17 November 2021||21.02 Patch 2 |
This version includes the following enhancements:
|31 May 2021||21.02 Patch 1 (210506p)||Fixes a number of important defects.|
19 February 2021
Links to a different documentation space.
This version includes the following enhancements:
For BMC Cloud hosted BMC Helix Client Management, patching is undertaken by BMC. For information on the scheduling of such patches, see the BMC Client Management Patch deployment schedule.
Ready-made PDFs are available on the PDFs and videos page. You can also create a custom PDF.
Creating PDF and Word exports
You can create a PDF of a page or a set of pages. (Non-English page exports are not supported.) You can also create a Word document of the current page.
To export to PDF or Word
- From the Tools menu in the upper-right, select a format:
- Export to Word to export the current page to Word format
- Export to PDF to export the current page or a set of pages to PDF
- If exporting to PDF, select what you want to export:
- Only this page to export the current page
- This page and its children to export a set of pages
Concepts, architecture, deployment, planning, and system requirements.
Information about installing the product and migrating product data.
Upgrade process, migration, and configuration.
Issues resolution, error messages, logs, and contacting Support.
Interface descriptions, using the product.
Security, system administration, maintenance.
Development interfaces and toolkits.
Integrations with other products.
The following topics contain videos that supplement or replace the text-based documentation:
- Deploying Operating Systems
- Managing software licenses
- Configuring SCAP Compliance
- Managing compliance
- Managing patches
- BMC Client Management web console overview
- Remotely controlling an unmanaged device
- Configuring the remote control recording parameters
- Distributing software
- Managing packages
- Accessing and navigating the BMC Client Management web console
- Installing on-premises on Windows and installation options
- Preparing for upgrade
- Performing the upgrade
- Verifying the upgrade
- OSD Managers
- Automatically rolling out agent using a wizard
- Downloading and installing a rollout from a server
- Performing remote operations on managed mobile devices
- Configuring mobile device management
- Managing configuration profiles for managed mobile devices
- Enrolling mobile devices
- Managing mobile applications
- Integrating Footprints Service Core 12 with BCM
- Prerequisites to roll out BCM agents on MACs
- Remotely controlling a device through a web browser
- Managing applications purchased through the Apple Volume Purchase Program
You can find the answer to this question and more information about upgrade in Upgrading.
Starting from version 12.0, updating the tablespaces is no longer required.
You can find the answer to this question and more information about the product compatibility in Product matrix compatibility.
Master server does not support any children other than relays. It should not have more than 500 direct children. It is mandatory to have a first level relay for SaaS. You have to configure these settings on the Linux master. For more information, see Best practices for masters and relays deployed on Linux.
Relays have 2000 clients for Windows and 5000 for Linux. You have to configure these settings on the Linux master. For more information, see Best practices for masters and relays deployed on Linux.
You have to ensure that the configuration is set on the master or relay. For more information, see Best practices for masters and relays deployed on Linux.
BMC Client Management is not a real-time agent. The time before the device icon turns red is set in Global Settings > System Variables > Connection management. It is recommended to not reduce the default values.
For information about about installing updates on the Mac devices, see Patch Management steps.
For Linux, it is possible to run commands through BMC Client Management. For more information, see this Knowledge Article Client Management: How to use BCM to Patch Mac OS X or Linux devices
Yes, BMC Client Management manages devices through internet either through a DMZ relay if no VPN is available or it is not necessary to set up a DMZ relay. If you cannot use VPN to connect to the relays, see DMZ architecture for more information.
If you are using a DMZ relay, you must configure the DMZ relay and its clients to properly manage unstable communications. For more information, see this Knowledge Article Client Management: Improve Internet / DMZ / VPN communication and limit "Queue Full" on Relays.
Relays support 2000 clients for Windows and 5000 for Linux. You have to configure these settings on the Linux master. For more information, see Best practices for masters and relays deployed on Linux.
You can find the answer to this question and more information about the type of objects BMC Client Management can discover in the Attributes collected for managed and unmanaged devices topic and its sub-topics.
BMC Client Management does not support patching of older operating systems that have reached their end of support (i.e. Windows 2007). These older systems can be patched by BMC Client Management through a special process if needed. To accomplish this, you must subscribe to extended support with Microsoft and then work with BMC Support and to purchase and set up a custom configuration in the Patch Management module in BMC Client Management to include these older patches.
To do this, perform the following steps:
- Contact Microsoft to purchase extended support for the older operating systems like Windows 7.
- Contact BMC Support to request more information on purchasing a custom subscription for these older systems.
- BMC Support will refer you to BMC Product Management to help you connect with and purchase this extended support subscription from our 3rd party patch vendor Ivanti.
- The 3rd party vendor will provide a URL to a custom patch manifest file to be used with BMC Client Management.
- Once you have your URL, you must perform the following steps on the BMC Client Management agent that is set as your Patch Manager:
- Go to Program Files\BMC Software\Client Management\Client\config and edit PatchManagementPremium.ini.
- Under [ConfigFilesManagement] section, add the following entry with the custom URL:
ConfigFileUpdateURL=<URL received from Ivanti>
- Restart BCM service and then update the patch knowledge base.
The new URL can now be used.