Unsupported content


This version of the product is in limited support. However, the documentation is available for your convenience. You will not be able to leave comments.

Release notes and notices

This set of Release Notes describes version 11.2 of BMC Discovery.


To stay informed of changes to this list, click the  icon on the top of this page.

Node changes in Technology Knowledge Update TKU 2019-Dec-1

TKU December 2019 enhances the model for Cloud Regions and Cloud Services to be segregated by account. If you discover more than one AWS Account, more than one Azure Subscription or more than one GCP Project, all the data from Cloud Region through to individual nodes within services will be clearly separated, where before it was intermingled.

As a result, the keys of all CloudRegion and CloudService nodes, and many contained nodes will change, even if you only discover a single account. If you synchronize to a CMDB, the identities of the corresponding CIs will also change.

The existing nodes are not deleted automatically with the application of the TKU. To remove the old nodes from the BMC Discovery model, you can delete the patterns that were deactivated by the new patterns in the TKU. However, the old CIs in the CMDB will not be deleted automatically. The simplest way to remove them is to perform a resynchronization.

Enhanced support for AWS role-switching in Technology Knowledge Update TKU 2019-Dec-1

In the December TKU we have enhanced the support of AWS role-switching in discovery. Previously, it was only possible to specify a single role for an AWS credential. Now, you can specify a list of roles. This allows you to reduce the number of AWS credentials and associated Scheduled Scans that need to be maintained.

However, the new configuration to support role-switching cannot be added automatically to existing AWS credentials, and consequently, any existing scheduled AWS scans using those will fail. The workaround is straightforward. Simply click Edit on the scheduled scan, and then click Apply. In all likelihood you will edit all of your scheduled AWS scans to take advantage of the role-switching functionality. Using the Edit/Apply workaround enables you to continue scanning AWS without interruption.

Version history

The following table displays the version history of BMC Discovery 11.2:

May 03, 201911.2 patch 6This release resolves important defects and security vulnerabilities. It also introduces a feature for restricting the paths on which you can run commands.
July 11, 201811.2 patch 5This release resolves important defects.
June 22, 201811.2 patch 4This release resolves important defects and security vulnerabilities.

11.2 patch 3This patch was not made generally available.
December 15, 201711.2 patch 2This release resolves important defects.
September 25, 201711.2 patch 1This release resolves important defects.
September 15, 201711.2For complete information about this release, see the features listed in the following section of this page.

You can only upgrade to version 11.2 from version 10.1 and later.

Model changes

BMC Discovery 11.2 changes the way that virtual machines are modeled. In previous releases VMs were modeled using a SoftwareInstance (SI) node with a vm_type attribute. They are now modeled using a Virtual Machine node which makes it easier to find and relate VMs to their containers and Hosts.

Logical databases are now stored in dedicated Database nodes rather than the DatabaseDetail nodes previously used. Dedicated Database nodes simplify the separation of databases from other database details. DatabaseDetail nodes are still used for other information about databases, for example schemas and tablespaces.

For more information, see 11.2 Enhancements and for full details of the changes, see Model changes.

CentOS 6 replaces Red Hat Enterprise Linux 6 in BMC Discovery 11.2

The upgrade to BMC Discovery 11.2 replaces Red Hat Enterprise Linux 6 with CentOS 6 . CentOS is an enterprise-class Linux platform which is derived from, and aims to be functionally compatible with its upstream source, Red Hat Enterprise Linux  (RHEL).

As CentOS is derived from, and aims to be functionally compatible with its upstream source, Red Hat Enterprise Linux, BMC performs the same testing against the Red Hat 6 STIGs.

When applying OS upgrades to BMC Discovery 11.2, ensure that you download and apply the Latest CentOS 6 operating system upgrade.

Release Notes

These Release Notes detail the following information:

Additional permissions required on XML and CSV APIs

The permission required to access the CSV and XML API has changed since BMC Discovery 11.0. If upgrading from BMC Discovery 11.0, you must grant the new API access permission (api-access group), or updating group permissions to include the api/access permission for users who require access to the CSV and XML web APIs. Existing integrations will fail if you do not add the permission.

Updated SSH server

The SSH server installed on BMC Discovery appliances 10.2 and later has been modified. This modification removes some weak ciphers and HMAC algorithms (and non-FIPS approved) from the list of allowed connections. Therefore, some older versions of ssh clients might be unable to connect. The following client versions (or later) have been tested and are known to work:

  • PuTTY (0.64)
  • WinSCP (5.7.2)
  • mRemoteNG (1.72 using ssh2)
  • MobaXterm (6.5)
  • KiTTY (
  • Bitvise SSH Client (6.22)

BMC Atrium Discovery OS and application software have been tested and found to be free from susceptibility to date/time issues which may occur as the result of the additional day in a leap year.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.