Merging, or ignoring Software installs for Reconcilliation (or other solution best practice)

[Stephen42]

Hi all, I'm back with yet another question re how to either merge of ignore specific software Installs from cmdb_sam_sw_install, or some other option, or best practice.  Below is an example of what I am trying to accomplish.  This is with AutoCad, however, there are other titles we are having the same issue with.

First off, we are on Utah, and cmdb_sam_sw_install is populated via SCCM/ServiceGraph connector.

For each 'Installed on' we are getting four AutoCad install records.  AutoCad LT 2023 - English, AutoCad LT 2023 Shared, AutoCad LT 2023 Shared language Pack, AutoCad Open in Desktop.    These map to Three Discovery Models, and then to One Software Model, with appropriate entitlements.  All the components have been normalized automatically be SAM and are flagged as Licensable.

The issue we are having is that the above reconciles to four installs against the entitlement, when in fact, these are sub-components of the same software title.  I checked the cmdb_m2m_suite_model table and no 'suite' exists for AutoCad.

So, how can these four  installs reconcile against the entitlement and only consume one license ?    Do we need to define a 'suite'  ? Is there a way to flag an install as 'ignore' or other ?

As stated, we are seeing this same behavior in other software titles also , so looking for a workaround, solution, or how we can 'group' these somehow to reconcile as only one install against the entitlement.

Thanks in advance

[Stephen42]

Engelica, thanks again.  Everything (through the Normalization and Discovery Model) refer to the One Software Model, as for the Entitlement, we were told it's Subscription with Metric Per Named User.   Not sure why SCCM is reporting installs this way, but in our organization, a work around in ServiceNow would probably be quicker than going back to SCCM.

So I am either looking to ignore what are flagged as Licensable Installs, Or somehow 'merge' the installs. 

Appreciate the help

-Stephen

[Stephen42]

I may have found a workaround, thanks to the magic that is ServiceNow.   ServiceNow creates a Discovery Map based on the detail as sent from SCCM.   In our case, I have different Discovery Models for these components (based on their naming convention) , although they were  normalized to the same Publisher, Title, Version etc.   I was able to 'revert' the normalization on these components, and upon re-applying normalization, I was able to flag them as not licensable, so I now have Discovery Models that ARE licensable, and others not.  Reconciliation now only looks at the Software Installs / Discovery Map that are Licensable, and does not evaluate the rest. 

I'll continue to prototype this, but looks like a possible solution.

-Stephen