System used incorrect Discovery Map to link the Software Model to the Discovery Model

[Simon Wong]

I have Snagit 2023 installed on one machine. The Software Model represented it as TechSmith SnagIt but the name is version-less, not good.

The Software Discovery Model is called Snagit 2023 23.2.1 and it is represented in the Discovery Model as this:

	Discovered	Normalized
Publisher	TechSmith	TechSmith
Product	Snagit 2023	SnagIt
Version	23.3.1	2023

You can see pre and post normalization for the 3 fields.

So the Discovery Model for Snagit 2023 23.2.1 is mapped to the Software Model "TechSmith SnagIt", which is version-less.

The Software Model is linked to DMAP0012115, which is Publisher = TechSmith, Product = SnagIt, and other conditions as "Anything", hence explains why the name is version-less.

It also showed that it was mapped automatically by the system.

However, in the Discovery Map table I do see that there is one set of conditions DMAP0190597 (see screenshot) that should have captured the normalized Discovery Model based on the data:

Publisher = TechSmith

Product = SnagIT

Version starts with 2023

By my logic, the system should have used DMAP0190597, instead of DMAP0012115 to map Discovery Model Snagit 2023 23.2.1 whereupon it would have created a Software Model called "TechSmith SnagIt 2023", instead of "TechSmith SnagIt".

Any ideas why the system used the seemingly incorrect DMAP?

[dreinhardt]

Hi @Simon Wong,

the main function a DMAP is to represent the PPN specific software product details (Product, Edition, Version) of a PPN and help the system to create/link the correct software model as part of the entitlement onboarding process.

In case you’ve onboarded a SnagIt Entitlement with a PPN, the model and DMAP is correct, as it seems to be that the use rights for this PPN allows you to use a version-less SnagIt.

From a reconciliation view, SAM Pro processes  software model with linked active entitlements first and will use the details from „Software Model - Related Links - Show Matching Discovery Models) to identify all DMAPs and its linked Software Installationens to calculate your compliance.

• Question: Do you facing any issues with the current setup and you compliance? 

Note: Pleae add the column „active“ to your DMAP table to check if the maps are active and can be used.

Best, Dennis

[christianseppDL]

HI @Simon Wong ,

the question for your software model in regards to the selected DMAP is the source of "creation".

- Created from entitlement --> DMAP of the linked PPN (software entitlement definiiton)

- Created "manually" --> user selects the appropriate DMAP 

- Created from discovery model --> SAM option to auto-create (licensable / non-licensable) software models from discovery models must be enabled; ServiceNow applies best matching definition

In addition, the DMAP on the software model serves different purposes:

a) DMAPs are used to link DMAPs (software models) for downgrade rights, suites etc

b) DMAPs are used as "filter parameter" to pick up the installations of the available discovery models in your environment, e.g. the generic SnagIt software models finds all discovery models (and the installations) for the normalized product "SnagIt", independently of the normalized version (see Dennis' reference to "Show Matching Discovery Models"

Thus, if you want to have more "transparency" on the software model level, you may create more specific software models. Please note that the same installation on a device may be counted in multiple software models, i.e. if multiple DMAP search filters are applied.

Best, Christian

Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.