BMC Helix Discovery information for BMC Helix AIOps users
A version of BMC Helix Discovery is provided for users of BMC Helix Portal and BMC Helix AIOps, though can be used without those applications. This is the only version commissioned since 1 June 2021.
- If you are using an instance of BMC Helix Discovery commissioned before 1 June 2021, you are using the standalone version of BMC Helix Discovery and should see Recent updates for information on updates and enhancements.
- If you are using an instance of BMC Helix Discovery commissioned after 1 June 2021, you are using the version of BMC Helix Discovery for BMC Helix Portal and BMC Helix AIOps users, and should continue reading this topic for information on updates and enhancements.
Updates
Your BMC Helix Discovery instances are updated each month. You will receive an email notification at least 21 days before your Prod instance is updated, and 7 days before your Non-Prod instance is updated, in accordance with our notification policy.
For BMC Helix Discovery, each month's TKU is applied to Non-Prod, and Prod instances on the dates advised. The included BMC Discovery Outpost is automatically updated by default unless you have configured manual updating. If you have configured manual updating, you should ensure that you apply the updates as soon as is practical, otherwise there could be a mismatch between BMC Helix Discovery and the BMC Discovery Outpost that might result in an incorrect model or slightly degraded discovery. See Configuring the BMC Discovery Outpost for more information on configuring automatic updates.
The TKU changes which occur each month improve the capabilities of BMC Helix Discovery, and sometimes these change the model. If you have a single Outpost operating with your Non-Prod and Prod instances, the Outpost is updated to the latest Non-Prod version causing a mismatch between the Outpost version and your Prod instance. Occasionally this mismatch might result in an incorrect model or slightly degraded discovery, and would be noted in the updates table below. The mismatch will last until the next update and is likely to be infrequent. You can avoid this situation by installing a separate Outpost for your Non-Prod and Prod instances.
You can see more information on TKU content and schedules in BMC Discovery content reference (Configipedia).
Changes to regular expressions in Python
Global flags in Python are meant to be placed at the start of regular expressions. Earlier versions of Python issued warnings for misplaced flags. BMC Helix Discovery now uses Python 3.11, in which misplaced flags are an error. TKU patterns have been updated for this change, and the TPL compiler now warns if flags are misplaced in your custom patterns. However, regex searches with misplaced flags fail silently. In Blueprints, the searches fail to match and, without notification, your Blueprints will be empty, or will not contain what you expect.A simple example of a misplaced flag is: '^(?i)Linux' which can be corrected to '(?i)^Linux'
Similarly: '/Common/(?i)((FV|dl)515sy):2121' can be corrected to '(?i)/Common/((FV|dl)515sy):2121'
An example from the EMC ControlCenter StorageScope pattern is: '^(?i)EMC ControlCenter \d(?:\.\d)*' which has been corrected in the TKU to '(?i)^EMC ControlCenter \d(?:\.\d)*'
Generally available 2024 enhancements
April 2024
This is the release of BMC Helix Discovery version 24.2.01.
This version applies the Technology Knowledge Update TKU 2024-Apr-1 and includes the following enhancements:
- Discover and display additional attributes for TLS Certificate Discovery.
- The BMC Discovery Outpost only uses 'Modern' ciphers as defined by Mozilla. See this article on the Mozilla website.
The update also resolves the following defects:
Description | Defect ID |
|---|---|
Content Security Policy contained in BMC Helix Discovery does not allow Gainsight-required artifacts to be displayed. | DRUD1-47014 , DRUD1-47216 |
The licensing page shows "Not Installed Storage Discovery" while Storage TKU is installed. | DRUD1-47068 , DRUD1-46828 |
Powershell discovery failure message is not helpful. | DRUD1-43886 , DRUD1-46439 |
Outpost SSH workers remain after the scan is finished. | DRUD1-43058 , DRUD1-43920 |
When clicking on a host, the Discovery UI page displays the error "This system is having technical difficulties with this page." | DRDC1-22878, DRUD1-43302, DRUD1-43579 |
SSM Setting on a scheduled Discovery Run cannot be changed to Disabled. | DRUD1-43392, DRUD1-43928, DRUD1-46862, DRUD1-43057 |
Contributor:Inference relationship should be deleted or updated with new Package version. | DRUD1-40477 |
The dashboard does not uncheck the checkbox for a custom channel in the UI. | DRUD1-40019 |
March 2024
This is the release of BMC Helix Discovery version 24.1.02.
This release applies the Technology Knowledge Update TKU 2024-Mar-1.
The update includes the following new features:
- Enhanced pattern compilation and execution:
- Reduced compile times
- Improved compile-time errors and warnings
- Runtime ECA Errors now include a traceback of the TPL calls
- The changes fix or improve some of the existing behaviors in TPL. See What's new in TPL for more information.
- Pattern management enhancements:
- Deactivated patterns stay deactivated when a new TKU is applied.
- Provide a direct link to newly imported pattern modules after upload.
Securely register BMC Discovery Outposts by using the Outpost and BMC Helix Discovery REST APIs. See Authenticating with the Outpost REST API for more information.
- Securely register Outposts using the REST APIs
- Exchange tokens by calling APIs on both Outpost and BMC Helix Discovery.
- Filter on relationship attributes in the visual query builder.
- Produce compact JSON output from the REST API.
The update also resolves the following defects:
Description | Defect ID |
|---|---|
The licensing page displays "Not Installed Storage Discovery" although the Storage TKU is installed | DRUD1-46828 |
The taxonomy does not contain the relationship (GenericElement) | DRUD1-46696 |
Windows UBR (Update Build Revision) Registry Key is not discovered when using WMI. | DRUD1-43532 |
The TPL | DRUD1-41529 |
February 2024
This is the release of BMC Helix Discovery version 24.1.01.
This release applies the Technology Knowledge Update TKU 2024-Feb-1.
The update also resolves the following defects:
Description | Defect ID |
|---|---|
New documentation is provided for the BMC Helix Discovery ServiceStatus page. | DRUD1-42635 |
Documentation for SNMP discovery has been updated to clarify that login attempts with SNMP queries are used only if:
| DRUD1-42455 |
January 2024
This is the release of BMC Helix Discovery version 24.1.00.
This release introduces the ability to automatically synchronize services from BMC Helix CMDB into BMC Helix Discovery.
The Technology Knowledge Update TKU 2024-Jan-1 was applied.
The update also resolves the following defects:
Description | Defect ID |
|---|---|
Discovering Citrix NetScaler devices by using the REST API fails after November TKU. | DRUD1-43492 |
In certain rare upgrade failure circumstances the vault could become inaccessible. This has been corrected. | DRUD1-43484 |
BMC Discovery Outpost connection through proxy does not work until name resolution is available from the BMC Discovery Outpost. | DRUD1-43456 |
External events are not sent by consolidation. | DRUD1-43342 |
When the BMC Discovery Outpost released with the November TKU is installed on a FIPS enabled host, if it is not installed in the C:\ drive, the installation/upgrade does not place the | DRUD1-43256 |
HTML bold font code is visible when searching for ModelDefinitions. | DRUD1-43119 |
Since outpost 130.86.7818.867818, connection to the Hashicorp credential vault fails. | DRUD1-42843 |
tw_svc_cluster_manager.log showing security.api: WARNING: User 'xxxxxx' does not have permission for operation 'cmdb_sync'. | DRUD1-42587 |
The REST API does not honor maintenance mode. | DRUD1-42324 |
A connection error is displayed in the UI on CMDB timeouts. | DRUD1-41552 |
You cannot bulk delete Recognition Rules, or sort rules in the UI according to Status. | DRUD1-41491 |
Generally available 2023 enhancements
December 2023
This is the release of BMC Helix Discovery version 23.4.02.
This release introduces the Visual query builder which enables you to define queries using a visual representation of the nodes and relationships. You can filter using combinations of attributes, focus the results on any of the nodes, and specify columns from any of the related nodes to show in the results. See Using the visual query builder for more information.
The Technology Knowledge Update TKU 2023-Dec-1 was applied.
The update also resolves the following defects:
Description | Defect ID |
|---|---|
For some AIX 7.1 targets, the getIPAddresses method fails with error "Unexpected Output format". | DRUD1-42906 |
Running a saved query fails and displays an error page. | DRUD1-43324 |
RunCommand fails with a 'Bad HTTP response returned from the server. Code: 400, Content:' error although the command result is visible and correct. | DRUD1-43072 |
SSH discovery is timing out for some Linux hosts. | DRUD1-42317 |
The ServiceNow dependencies for classes "cmdb_ci_logical_datacenter" and "cmdb_ci_resource_group" are undocumented. See ServiceNow Mapping for Cloud for updated documentation. | DRUD1-35561 |
A lookahead in a regex does not work correctly in the regex.extract() TPL function. | DRUD1-42619 |
When syncing Microsoft Azure subscritions, | DRUD1-40883 |
Outpost API Patch Credential Fails for AWS Credentials. | DRUD1-41040 |
ServiceNow syncmapping: sync of stacked devices is not working correctly. | DRUD1-32009 |
ServiceNow syncmapping: sync of Serial Number for cmdb_ci_lb class is not working correctly. | DRUD1-32010 |
ServiceNow syncmapping: sync of ip_version mapping for IP Address CI is incorrect. | DRUD1-31779 |
ServiceNow syncmapping: the ServiceNow.SoftwareInstance_cmdb_ci_appl syncmapping does not consider related pattern publishers to set manufacturer. | DRUD1-34794 |
ServiceNow syncmapping: the ServiceNow.NetworkDevice_Host_Linkage does not create Connects_to__Connected_by relationship for edge connectivity. | DRUD1-34817 |
ServiceNow syncmapping: for Linux hosts, the OS service pack is not synced to ServiceNow CMDB for Linux Hosts. | DRUD1-34886 |
November 2023
This is the release of BMC Helix Discovery version 23.4.01.
The Technology Knowledge Update TKU 2023-Nov-1 was applied.
The update also resolves the following defects:
Description | Defect ID |
|---|---|
When Outposts or TKUs are updated, some Outposts were disconnected from the instance and must be updated manually. | DRUD1-40540 |
Cross-Services CI links were not exposed by 'topology/nodes' endpoint | DRUD1-40253 |
SAAM modeling: Following Management connections added large numbers of unwanted nodes to the model. The system no longer follows Management connections. | DRUD1-42057 |
Incorrectly formed .xml report files caused a Critical Exception. | DRUD1-42337 |
October 2023
This is the release of BMC Helix Discovery version 23.4.
The Technology Knowledge Update TKU 2023-Oct-1 was applied.
The update also resolves the following defects:
Description | Defect ID |
|---|---|
Occasionally scans fail showing an SSH timeout error on hosts with non-English locales. | DRUD1-42317 |
A credential test failure in Thycotic credentials broker shows password in readable format. | DRUD1-42295 |
When editing and saving a CyberArk credential, the BMC Discovery UI shows a 502 Error - Service Temporarily Overloaded. | DRUD1-42129 |
September 2023
This is the release of BMC Helix Discovery version 23.3.02.
The Technology Knowledge Update TKU 2023-Sep-1 was applied.
Description | Defect ID |
|---|---|
Cannot download a BMC Discovery Outpost through an HTTP proxy that has a backslash character '/' in its name. You can workaround this problem by using percent encoding for the backslash. See Downloading and installing a BMC Discovery Outpost for more information. | DRUD1-42216 |
The models API gives the state of a published model, including the published node's node ID. It should also include the published node's key. | DRUD1-42082 |
August 2023
This is the release of BMC Helix Discovery version 23.3.01.
The Technology Knowledge Update TKU 2023-Aug-1 was applied.
July 2023
This is the release of BMC Helix Discovery version 23.3.
The update provides the following new enhancements:
- Discover hosts by using PowerShell and Windows Just Enough Administration (JEA).
- The Technology Knowledge Update TKU 2023-Jul-1 was applied.
The update also resolves the following defects:
Description | Defect ID |
|---|---|
The | DRUD1-41408 |
Cannot generate a new key when the company name is too long. | DRUD1-40932 |
Cannot extract DOMAIN from Cyberark from an arbitrary attribute. See Using CyberArk credentials for discovery for more information. | DRUD1-40301 |
Unable to load credentials when the Enter key is used instead of the APPLY button. | DRUD1-39597 |
Windows package names can contain garbage characters. | DRUD1-38879 |
Windows could not start the Outpost Service because of timezone setting. | DRUD1-37180 |
ECA error:RuleError on rule reasoning_host_create_if_necessary. | DRUD1-31727 |
June 2023
This is the release of BMC Helix Discovery version 23.2.02.
The update provides the following new enhancements:
- View log files to help you diagnose problems with CMDB synchronization and writing patterns. You can watch logfiles in the BMC Helix Discovery UI, or you can download them to analyze on your local computer.
- The Technology Knowledge Update TKU 2023-Jun-1 was applied.
The update also resolves the following defect:
Description | Defect ID |
|---|---|
Lifecycle reports enhancements (end of life data). | DRDC1-19678 |
May 2023
This is the release of BMC Helix Discovery version 23.2.01.
The update provides the following new enhancements:
- Use blueprint-based modeling to model services.
- Restrict Outposts to organizations and limit discovery scans.
- Create and upload custom reports.
- Improvements in Start Anywhere Modeling:
See combined software and infrastructure in a single view with Display > Focuses.
Turn individual types of data on or off.
Choose to see only incoming or only outgoing impacts.
Mixed focuses.
'Directly Connected' focus allows you to see all the relationships of any node, and enables you to view imported graph data.
'Provenance' focus shows how data is inferred.
- Improvements in visualizations, such as mixed focuses.
- Miscellaneous improvements:
- New and enhanced REST APIs, such as the ability to import topology information.
- Set default values for the Cloud Host Detection and VMWare Guest scanning options. These options set the defaults, the setting can still be specified for each Discovery run.
- The Technology Knowledge Update TKU 2023-May-1 was applied.
The update also resolves the following defects:
Description | Defect ID |
|---|---|
The PRIV_LSHW privileged command was undocumented. | DRUD1-40899 |
SIs hosted on MFParts were not aging correctly. | DRUD1-40594 |
The last_discovered attribute should be set when a destroyed node is synced to ServiceNow CMDB. | DRUD1-40421 |
Recent run in Consolidator showing an error regarding "Outpost no longer registered". | DRUD1-40320 |
Discovery Run Errors on LPARs when Job Name is not reported. | DRUD1-40268 |
Powershell credential failures are not recorded in UI Session Result List. | DRUD1-39829 |
Deep discovery of VMware Guest Hosts feature performing unnecessary implicit scans of vCenter guest. | DRUD1-39805 |
Occasionally Amazon Web Services fails with ECA error, | DRUD1-39802 |
Audit Log did not record login failure for user without correct permission. | DRUD1-39641 |
Unable to load credentials when Enter key is used instead of Apply button. | DRUD1-39597 |
Thycotic token expires after 20 minutes leading to scan failures. | DRUD1-39596 |
It is possible to get a URI Too Large Error. | DRUD1-39226 |
There is no detail within model Activity Record for some nodekinds. | DRUD1-38847 |
Database discovery attempts to use disabled credentials. | DRUD1-38387 |
Outpost login page unresponsive after vulnerability scan using Qualys. | DRUD1-37923 |
The Solaris serial is not discovered when the sneep utility is not in /opt/SUNWsneep/bin. | DRUD1-36534 |
CMDB resync may occasionally use excessive memory and the resync fail. | DRUD1-33393 |
DiscoveryRun node not able to attach to the DataSourceAccess node when a custom pattern triggers on the same DiscoveryRun node. | DRUD1-32538 |
Discovery pre-scan phase with Nmap, many non-existent unsupported devices were being created. | DRUD1-31351 |
Multiple processes running on the Proxy server are not being killed, resulting in the server requiring rebooting. | DRUD1-30304 |
April 2023
This is the release of BMC Helix Discovery version 23.2.
The update provides the following new enhancements:
- For users who access BMC Helix Discovery from BMC Helix Portal, in-app help is available from a floating widget at the bottom of every screen. Click the self-help widget to access a product tour, interactive guides, instructions for setting up and going live, and more.
- The Technology Knowledge Update TKU 2023-Apr-1 was applied.
The update also resolves the following defects:
Description | Defect ID |
|---|---|
The BMC Discovery Outpost automatic update occasionally fails resulting in a BMC Discovery Outpost that can no longer connect to BMC Helix Discovery. The installation failure is not logged. | DRUD1-40329 |
After applying the Technology Knowledge Update TKU 2022-Dec-1 (December 2022) the BMC Discovery Outpost can no longer scan its own host. | DRUD1-39911 |
Discovery of OpenVMS using ssh from the BMC Discovery Outpost fails. | DRUD1-39902 |
A link is displayed to a report of CIs awaiting incremental resync, though the link is not documented. | DRUD1-23565 |
March 2023
This is the release of BMC Helix Discovery version 23.1.02.
The Technology Knowledge Update TKU 2023-Mar-1 was applied.
The update resolves the following defects:
Description | Defect ID |
|---|---|
| The Host node view page shows a table of network interfaces and their IP addresses. If there are no NetworkInterfaces, no IP address information is shown. | DRUD1-40243 |
vCenter polling can stop if interesting events are infrequent. | DRUD1-40114 |
Explicit and Implicit scans of the same endpoint can cause odd failures. | DRUD1-40107 |
| The CyberArk vault management page usability improvements. | DRUD1-39985 |
February 2023
This is the release of BMC Helix Discovery version 23.1.01.
The Technology Knowledge Update TKU 2023-Feb-1 was applied.
January 2023
This is the release of BMC Helix Discovery version 23.1.
The update also provides the following new enhancements:
- Deep discovery of VMware Guest Hosts using vCenter APIs.
- You can disable cloud host detection for individual scans, avoiding an unnecessary step when you scan hosts that, for example are on a subnet that is not hosted in the cloud.
- The calls made to target systems have been further optimized. For example, irrelevant methods are skipped for targets and the DiscoveryAccess shows the reason as
RequestSkipped. - Installation of the BMC Discovery Outpost is supported on a Windows Server Core host.
- The Technology Knowledge Update TKU 2023-Jan-1 was applied.
The update resolves the following defects:
Description | Defect ID |
|---|---|
The Model > Devices page shows error "Something went wrong!" | DRUD1-38936 |
The first credential test or scan after a Kerberos Outpost start fails. | DRUD1-36819 |
ServiceNow CMDB Sync. The | DRUD1-39294 |
The boot_time attribute on the HostInfo node is not described in the documentation or taxonomy. | DRUD1-39293 |
Boot Time for Windows hosts is not in the same date format when discovered using WMI and PowerShell. | DRUD1-39014 |
Clicking the scanner name on the consolidation configuration UI on the Consolidator reports | DRUD1-39250 |
Exporting Visualizations does not center on the printout. | DRUD1-39141 |
The Disk Monitoring email notifications do not provide the machine details. | DRUD1-39398 |
The documentation and Swagger UI require detailed options for | DRUD1-39390 |
A duplicate HBA is created on clustered Windows hosts when using Remquery (hbacmd). | DRUD1-24146 |
Searching RootNodeKeyInfo can create queries too complex to run. | DRUD1-30120 |
Disk Monitoring can stop Discovery or shut down services even when Online Compaction is in progress. | DRUD1-39399 |
Insufficient error filtering leads to bogus Disk Drive model and vendor. | DRUD1-39393 |
Incorrect dns_domain reported for Windows servers when | DRUD1-34157 |
Discovery Outpost proxy settings issue | DRUD1-39178 |
AWS Cloud Credentials show failure when you test them, but work during scanning. | DRUD1-37688 |
During ServiceNow sync, the | DRUD1-33343 |
The getPackageList method returns less data using PowerShell than WMI, and gives different architecture values. | DRUD1-38524 |
vCenter polling can stop if interesting events are infrequent. | DRUD1-25931 |
Model and Vendor are missing from the PDF Profile. | DRUD1-39010 |
Generally available 2022 enhancements
December 2022
The Technology Knowledge Update TKU 2022-Dec-1 was applied.
The update also provides the following new enhancements:
- Deep discovery of VMware Guest Hosts using vCenter APIs.
- The update applied the December 2022 (TKU 2022-Dec-1).
The update also provides the following new fix:
Description | Defect ID |
|---|---|
The Model > Devices page shows the error "Something went wrong!" | DRUD1-39307 |
November 2022
The Technology Knowledge Update TKU 2022-Nov-1 was applied.
October 2022
The Technology Knowledge Update TKU 2022-Oct-1 was applied.
The update also provides the following new enhancements:
- You can disable cloud host detection for individual scans, avoiding an unnecessary step when you scan hosts that, for example, are on a subnet that is not hosted in the cloud.
- The calls made to target systems have been further optimized. For example, irrelevant methods are skipped for targets and the DiscoveryAccess shows the reason as
RequestSkipped. - Installation of the BMC Discovery Outpost is supported on a Windows Server Core host.
The update also provides the following new fixes:
Description | Defect ID |
|---|---|
When scanning Google Cloud Platform, occasionally ECA errors of the type | DRUD1-38766 |
When a snapshot scan is in progress, and you use the REST API Get method on the | DRUD1-38738 |
The version is not set for the discovered package "ibm-semeru-open". | DRUD1-38276 |
CMDB Sync does not handle duplicate CI and Relationship errors when syncing to RemedyForce targets. | DRUD1-38241 |
You cannot send email from a BMC Helix Discovery (SaaS) instance. | DRUD1-37847 |
When adding a credential in the Outpost, you cannot select multiple types, such as PowerShell and Windows. | DRUD1-37533 |
When scanning recent vCenter instances (5.1 and later), | DRUD1-33939 |
In searches that contain repeated traversals with | DRUD1-33538 |
| The following security-related defects were also resolved: DRUD1-38521, DRUD1-38522, and DRUD1-38539. | |
August 2022
August 2022 hotfix 2
The Technology Knowledge Update TKU 2022-Sep-1 was applied.
The update also provides the following new fixes:
| Description | Defect ID | ||
|---|---|---|---|
Occasionally when scanning particular hosts in Google Cloud Platform, the scan times out, and then logs an error. | DRUD1-38461 | ||
When CMDB Sync attempts to create a duplicate CI or Relationship, RemedyForce reports a "duplicate value found" error. | DRUD1-38403 | ||
The npcap component in the BMC Discovery Outpost has been updated to version 1.71. | DRUD1-38401 | ||
After restarting the BMC Discovery Outpost the first scan or credential test using a Kerberos credential fails, though the subsequent scan or test succeeds. | DRUD1-38315 | ||
August 2022 hotfix 1
The Technology Knowledge Update TKU 2022-Aug-2 was applied. This replaces and resolves some issues in the earlier Technology Knowledge Update TKU 2022-Aug-1 update. For full information, see the TKU 2022-Aug-2 documentation.
The August 2022 hotfix update made improvements to our internal infrastructure and management tools.
August 2022 release
The Technology Knowledge Update TKU 2022-Aug-1 was applied.
The update also provides the following new enhancements:
- Integration with a new third-party credential manager, One Identity Safeguard for Privileged Passwords.
- Running the BMC Discovery Outpost on Windows Server 2022 is now supported.
The update resolves the following defect:
| Description | Defect ID |
|---|---|
| DRDC1-19403 |
July 2022
The Technology Knowledge Update TKU 2022-Jul-1 was applied.
The update also provides the following new enhancements:
- You can now discover Oracle Cloud Infrastructure. See Discovering Oracle Cloud Infrastructure for more information.
- You can now change the application ID of BMC Helix Discovery when integrating with CyberArk Enterprise Platform Vault using the AIM Provider.
We have made a number of documentation corrections and clarifications, including:
Updated and expanded the descriptions of business services and technical services.
- Added information on the Google Cloud discovery topic, How to disable IPv6 on an Outpost server.
- Added information on impact arrows displayed in the system taxonomy. For more information, see Viewing the system taxonomy.
The update resolves the following defects:
| Description | Defect ID |
|---|---|
Missing documentation regarding the use of an HTTP Proxy with a BMC Discovery Outpost. See Registering an Outpost. | DRUD1-37527 |
TLS Certificate Serial Numbers are in Base 10 when they should be Base 16. | DRUD1-37426 |
Secondary sessions assume that all ports are open, leading to some long scan times and time-outs. | DRUD1-37425 |
Background color shading for system-added nodes does not show model updates properly. | DRUD1-37267 |
TKU update warning displays the wrong version number. | DRUD1-37197 |
"Data Completeness Issues" shown for RuntimeEnvironment. | DRUD1-37188 |
When a BMC Discovery Outpost skips an IP because it is in the Outpost's Exclude Ranges, the result is ERROR when it should be SKIPPED. | DRUD1-37128 |
For AWS SSM discovery, the discovered endpoint has no 'Credentials used' information. | DRUD1-37110 |
Discovery.sqlQuery can query using the wrong bind_address. | DRUD1-37001 |
OS Support Details for NetworkDevice are not displayed in the UI. | DRUD1-34804 |
Hashicorp SSH Credential requires a Password checkbox to be set. | DRUD1-34304 |
SQL Query Result display can have an excessively long title. | DRUD1-34015 |
Discovery.fileGet can fail in Windows Server discovery. | DRUD1-33428 |
Add Rest API Swagger UI to BMC Helix Discovery. | DRUD1-31180 |
Provide information on how to disable IPv6 on an Outpost server for Google Cloud Discovery. | DRUD1-30730 |
When configuring the Cyberark AIM interface, the application ID must be editable. | DRUD1-29236 |
June 2022
The Technology Knowledge Update TKU 2022-Jun-1 was applied.
The update also provides a Swagger UI to the existing BMC Helix Discovery REST API. For more information, see Using the REST APIs and Swagger and the REST APIs.
The
npcap
tool used in the component of the BMC Discovery Outpost has been upgraded to version 1.60. Npcap 1.60 causes instability in Windows Server 2012 R2. You should disable automatic updates of BMC Discovery Outposts until you are able to upgrade the host.
The update resolves the following defect:
Description | Defect ID |
|---|---|
The BMC Discovery Outpost installer always reinstalls npcap. | DRUD1-37386 |
April 2022
The following enhancements were provided in the April release:
- The BMC Discovery Outpost now has a REST API that you can use to manage credentials.
- The BMC Helix Discovery REST API has been enhanced to enable you to manage scheduled scans and exclude ranges.
The update resolves the following defects:
Description | Defect ID |
|---|---|
HRD row on Host node shows no details. | DRUD1-37104 |
The Outpost npcap driver might cause the Outpost host to reboot. | DRUD1-36738 |
Update documentation for the discovery of certificates for Windows targets. | DRUD1-36458 |
CyberArk and HashiCorp client certificate UI do not work as expected | DRUD1-36308 |
Missing information about Host licensing in documentation. | DRUD1-36291 |
Misleading message from Outpost when WMI and Remquery are disabled. | DRUD1-36212 |
Outpost installer deletes the "HKLM\Software\BMC Software" registry tree on uninstall | DRUD1-36189 |
Technical difficulties page is displayed if you try to view a ModelDefinition node without a "properties" attribute. | DRUD1-36172 |
In SAAM, the model kind switches to "Business Service" when editing a BAI. | DRUD1-36045 |
GCP IAP scanning doesn't handle "block project-wide ssh keys" setting on VMs. | DRUD1-35988 |
Binary data returned by the REST API comes in the form of a Python bytes literal. | DRUD1-35628 |
Include ServiceNow dependencies for classes "cmdb_ci_logical_datacenter" and "cmdb_ci_resource_group" in documentation. | DRUD1-35561 |
Custom report message: "Failed to generate query please check manually". | DRUD1-35526 |
OpenVMS Discovery is not working through the Outpost | DRUD1-34827 |
Outpost_id and outpost_name attributes are not populated in the DiscoveryRun node for Cloud scans. | DRUD1-34483 |
Validate and document latest CyberArk Enterprise Password Vault. | DRUD1-33834 and DRUD1-36817 |
Web request logging (API and UI) can create very large log files. | DRUD1-33486 |
Long auto-generated collection names spoil visualizations and break context menus. | DRUD1-27605 |
Additionally, the April 2022 (TKU 2022-Apr-1) was applied.
March 2022
The March 2022 (TKU 2022-Mar-1) was applied.
February 2022
The following enhancements were provided in the February 2022 release:
- Discovery of Google Compute Engine instances by using Identity-Aware Proxy
- Enhanced mainframe discovery includes observed communications
- Intelligent discovery of cloud services by region
- BMC Helix Intelligent Integrations
enabled
- Additional miscellaneous enhancements
The following defect has been resolved and included in the January release:
Description | Defect ID |
|---|---|
Add a limit of events to poll from vCenter. | DRUD1-36200 |
Additionally, the February 2022 (TKU 2022-Feb-1) was applied.
January 2022
The January 2022 (TKU 2022-Jan-1) was applied.
Generally available 2021 enhancements
Review the BMC Helix Discovery enhancements for features that will benefit your organization and understand the changes that might impact your users.
December 2021
The following defect has been resolved and included in the December release:
Description | Defect ID |
|---|---|
| AWS SSM sessions are returning "No Access" responses. | DRUD1-34198 |
Additionally, the December 2021 (TKU 2021-Dec-1) was applied.
November 2021
The following defects have been resolved and included in the November release:
Description | Defect ID |
|---|---|
Session logging now supported in scheduled discovery runs. | DRUD1-34984 |
Application ID can be changed for integration with CyberArk Enterprise Password Vault when using the REST API. | DRUD1-33525 |
September 2021
The following enhancements were provided in the September 2021 release.
New integration with third-party credential manager HashiCorp Vault
BMC Helix Discovery supports integration with a new third-party credential manager, HashiCorp Vault. HashiCorp Vault is application software that stores and manages credentials securely, according to the policies that your organization implements.
For the BMC Helix Discovery instance to be able to access HashiCorp Vault, you must perform the integration from the BMC Discovery Outpost on the Manage > Vault Providers page.
You can access the credentials stored in HashiCorp Vault from the Credentials UI using a series of filters to uniquely identify the element of the credential to use.
OpenShift OAuth authentication
Discovering Red Hat OpenShift clusters has been simplified by the addition of OpenShift OAuth authentication. Red Hat OpenShift clusters are discovered by using an API scan and an improved Kubernetes/OpenShift credential. The OpenShift OAuth authentication obtains an OAuth token from the OpenShift REST API Well Known Endpoint (WKE) using the provided username and password. Once the token is obtained, it is used to access and discover the OpenShift clusters specified in the credential. OpenShift OAuth provides the ability to discover many OpenShift clusters using a single credential. The WKE authorization server must be resolvable.
August 2021
The following defects have been resolved and included in the August release:
Description | Defect ID |
|---|---|
Pre-scanning incorrectly classifying dropped endpoints as no response causing lengthened scan times. | DRUD1-33008 |
VMware PhotonOS should be a supported, discoverable Linux platform. | DRUD1-33384 |
Discovery using SSH on Windows fails slowly if the shell/dialect is CMD.EXE. | DRUD1-33021 |
Documentation error: AWS SSM agent discovery of Windows devices was not released in 21.05. | DRUD1-32994 |
ECA error when remote filesystem has no remote_fs_name attribute. | DRUD1-32763 |
getHostInfo script is omitting every other DIMM from dmidecode causing incorrect physical RAM. | DRUD1-32578 |
RedHat Linux server can be incorrectly classified as AIX server when AIX appears in the uname output. | DRUD1-32213 |
JavaScript "Unknown collection" error occurs when a group is expanded in a visualization. | DRUD1-31953 |
An AWS Credential test fails with HTTPS Proxy, | DRUD1-31205 |
CSTM command no longer works on all HP-UX models. Replace with the cprop command. | DRUD1-27723 |
Tags are not currently synchronized to BMC_Tag in the Remedy CMDB. | DRUD1-26842 |
Additionally, the following security-related defect has been resolved: DRUD1-33007
Notable differences in BMC Helix Discovery for BMC Helix AIOps users
The version of BMC Helix Discovery for BMC Helix AIOps users includes a few notable changes that are described on this page:
Licensing limitations
BMC Helix Discovery for BMC Helix AIOps users is intended for service modeling using data from BMC Helix AIOps rather than automated asset discovery and identifying systems and services in your IT environment. However, you can try discovering some of your IT environment. You can download a BMC Discovery Outpost from the UI, and you can discover up to one hundred hosts. See Getting started for more information.
Start anywhere application modeling
This section describes the new service modeling capabilities introduced in the release of BMC Helix Discovery for BMC Helix AIOps users.
Comments
Log in or register to comment.