How to exclude Software Installations and/or Discovery Models from Reconciliation

Go to solution
dimitrisala
Tera Expert

‎10-16-2024 06:08 PM - edited ‎10-16-2024 06:30 PM

Hi,

 

I currently have a particular product for which we have commercial editions and free Community editions installed. The discovery models for each of the installs are associated with the same Software model / Product which includes all editions. Is there a way to exclude installations with a particular 'Edition' from being counted in the software reconciliation. 

 

I have already troubleshooted/tried the following;

 

- Add a software install condition on the software model (Software Installation>DiscoveryModel>Edition IS NOT "Community"), however this then seems to then seems to also exclude the valid installs. It looks like the Install condition can only be an inclusive condition.

 

- Update the Discovery Map / Software Model to only match where Edition = empty (all the other editions installed have an empty edition populated so this picks up all the other valid installs). This works in terms of excluding the Community versions from being calculated against the particular software model, however on reconciliation the Community versions still appear as unlicensed installs on the Parent product i.e this just stops them from being counted against the specific entitlement/software model but still includes them as unlicensed installs for the Product.

 

My thoughts are to create a Software Model for the Community Edition and a generic 'unlimited' entitlement as a workaround, however this seems unnecessary and keen to understand if there is a better way to exclude these installation records.

 

--------------------

 

After further investigation the issue appears to be that the normalization is normalizing the Discovered Product "IntelliJ IDEA Community Edition" to the licensable Normalized Product "IntelliJ IDEA" rather than the correct Normalized Product "IntelliJ IDEA Community Edition". Therefore, I can revert the normalization and manually normalize this to be correct, however there are many different "Community" Edition discovery models so it will be quite tedious to update all of these and any time a new version is installed the new Discovery models will continue to normalize to the incorrect Product and need to continuously be reverted and manually normalized. 

 

Is there a way to resolve this with a workaround that does not involve having to manually normalize every discovery model while a request is raised with SNOW to update the content service to correctly normalize the "Community" Edition to the correct "Community" Edition product rather than the Licensable product?

0 Helpfuls
  • 2,616 Views
1 ACCEPTED SOLUTION

Go to solution
dreinhardt
Tera Sage

‎10-17-2024 06:58 AM

Hi @dimitrisala,

with the W.DC release ServiceNow introduces a new feature to cover your use case, as the default product type is tied to the product and does not take of the edition, until now.

 

The Feature is called "Product License Exception Rules" - Content updates for Software Asset Management (servicenow.com)

 

Product types can be updated on a product’s edition level using the Custom Product License Exception Rules [samp_cust_prod_lic_excep_rules] table. For cases where certain editions are non-licensable, the product type gets updated automatically if the exception rule is defined in the Product License Exception Rules [samp_prod_lic_excep_rules] table or the Custom Product License Exception Rules [samp_cust_prod_lic_excep_rules] table. However, if a product is non-licensable, an exception rule can’t be created for ​a licensable edition. For this case, you must raise a case with the Content Service team​ with supporting documentation and the team reviews ​whether the edition must be tagged as licensable.

dreinhardt_0-1729173502716.png

 

Best, Dennis

 

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

View solution in original post

5 REPLIES 5

Go to solution
dreinhardt
Tera Sage
In response to mikereaves77541

‎10-25-2024 11:37 AM

Hi @mikereaves77541, you've to find a way to distinguish between the trial and the licensed version.

Adobe provides some detailed insights into the ways of edition licenses are applied based on SWID Tag files. Appendix A: Identifying Installs — Deployment Planning and Configuration.

 

ServiceNow ITOM Discovery, ACC-V, SCCM and others are able to capture the swid content and support the identification of the correct edition

  • Software edition information

    Starting in ACC-V version 2.3.0, edition information is supported for Adobe Acrobat and MS SQL server. In future releases, additional software will be supported. With this feature, SAM admins can get clear visibility into the editions of their installed software. Osquery commands are used to fetch the edition information which then shows in the Software Installation [cmdb_sam_sw_install] table in the Edition Override column. 

 

 

Hopfe this will help you! Best, Dennis 

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