Discovery models and software installations 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 normalization process associates both of these discovery models to the same software model since both normalized versions meet the version criterion of Starts with 10 on the software model. Discovery Models 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 VersionNote: 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 Models 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 Child: Subcomponent of main software (not individually 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. Unknown: Not discovered.For unknown product types, the product type can be changed to another value. When the product type is changed, the normalization status of the discovery model is updated to Manually Normalized. 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 for keeping 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. Note: If a normalized discovery model has a missing version, edition, language, or platform value, those field values can be set by the user. Once a new value is set, the normalization status changes form Normalized to Manually Normalized.Under specific conditions, certain fields that are typically read-only can be edited. If edited, the status changes to Manually Normalized. Revert normalization You can revert normalization if needed using the Revert Normalization related link. Discovery models with a status of 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 InstallationsThe Software Installations list contains the software installed in your organization and is automatically populated by discovery. Installed software is placed in the Software Installation [cmdb_sam_sw_install] table by Discovery, and a primary key is built (using Publisher, Display Name, and Version fields).Discovery automatically matches the discovered software installation with a new or existing software discovery model using the primary key.Table 2. Software Installations form Field Description Display name. Discovered name of the software installation which is typically a combination of the discovered product name and edition. Discovery model Software discovery model that represents the installed software. Publisher Discovered publisher of the software. Version Discovered version of the software. Edition Override Override of the software edition setting.For Office 365 subscriptions, this field is set from the software subscriptions record.If the edition for the software was not discovered, you can edit this field to set the edition, if known, so reconciliation can be performed successfully.For more information, see Manually override edition value. Assigned to User assigned to the hardware. Installation Prod id Unique ID for the product assigned by the manufacturer. Found through discovery. Install location Path under which the software is installed. Install date Date that the software was installed. Revision Revision of the software. Instance key Unique ID for the instantiation of the software. Automatically generated when the software is installed. Installed on Hardware on which the software is installed. Uninstall string Identifier used to uninstall the software. ISO serial number ISO number of the software. Reconciliation Entitlement The entitlement found to use with this installation. Inferred suite The inferred suite model this installation belongs to. Omit from suites Check box for not counting the software install as a component of a suite during reconciliation. View software usageA usage record tracks the sum of usage on a monthly basis so that you can assess the software usage in your environment. You can import usage information using Microsoft SCCM integration, or using the Import Sets feature.View a software subscriptionView software subscription records for subscription software. Software subscription records are used for accurate reconciliation.Manually normalize a software discovery modelYou can edit a software discovery model to manually normalize discovered software that has not been fully normalized (partially normalized, publisher normalized, or match not found) on the Software Discovery Models form so that it can be reconciled.Manually override edition valueWhen the edition of a software install is not automatically discovered, you can specify the edition on the Software Installation form with the correct value (if known) so the software can be successfully reconciled.