Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Discovery models

Log in to subscribe to topics and get notified when content changes.

Discovery models

Software discovery models are automatically created during discovery to identify and normalize the software installed in your environment.

Software discovery models are stored in the Software Discovery Model [cmdb_sam_sw_discovery_model] table. The normalization process is automatically run when a new discovery model is created. Discovery models are not created for software installations that have a name containing Security Update.

There is a difference between software models and software discovery models.
  • A software model is a specific version or configuration of software that is purchased and/or available to users.
  • A software discovery model is a model created when a version of software is discovered in a network environment.
Multiple software discovery models can be associated to one software model. For example, a software model can be defined as follows:
  • Publisher = X
  • Product = Y
  • Version = Starts with 10
If there are two separate installs of this product (version 10.1 and version 10.2), two discovery models are created. One of the discovery models has the discovered version set to 10.1, and the other discovery model has the discovered version set to 10.2. The reconciliation process associates both of these discovery models to the same software model since they both meet the version criterion of Starts with 10.

Software discovery models cannot be created manually. The following field combination, called the primary key, is used to match new software installations to a new or existing software discovery model.

Primary key: Publisher, Display Name, and Version
Note: When analyzing version numbers, an exact match is always searched for first, but rounds down to a major version number when an exact match is not found.

For example, if no match is found for version number 8.0.4, but version 8.0 is found, then version 8.0 is used in the Software model field.

Table 1. Discovery Model form
Field Description
Display name Name of the discovery model as it appears in record lists. This value is generated automatically using the discovered publisher, discovered product, and discovered version.
Normalization status Status of the normalization process:
  • Normalized
  • Partially Normalized
  • Publisher Normalized
  • Match Not Found
  • Manually Normalized
  • New
Publisher Normalized publisher of the software.
Product Normalized product name of the software.
Version Normalized version of the software product.
Discovered publisher Discovered publisher of the software.
Discovered product Discovered name of the software.
Discovered version Discovered version of the software.
Additional Information
Product type Product types include:
  • Child: a subcomponent of main software (not licensable).
  • Driver: software product that controls a device.
  • Licensable: software product that is licensable.
  • Not Licensable: software product that is not licensable.
  • Patch: software product designed to update, fix, or improve an existing computer program.

The reconciliation process only considers software discovery models that are licensable.

Platform Platforms include:
  • Windows
  • Mac
  • Unix
Language Languages include:
  • Dutch
  • English
  • French
  • German
  • Italian
  • Spanish

Additional languages are generated if discovered.

Edition Normalized edition of the software.
Full version Normalized full version of the software.
Exclude from content service Check box to keep the software discovery model from being shared in the Normalization Library. Default is to include software discovery models.
Note: This field is only shown if you have opted in to the Software Asset Management content service.

Revert Normalization

You can revert normalization if needed using the Revert Normalization related link.

Discovery models with a status of Normalized, Manually Normalized, Partially Normalized, or Publisher Normalized revert back to the status of Match Not Found. Fields are reset to their original values, and any rules associated with the software discovery model are deactivated.

Software Installations

All software installations matched to software discovery models are in the Software Installations related list.