Enterprise license covering Editions with different software model name

Anton22
Tera Contributor

We have an entitlements for an Enterprise Edition of a product. This Enterprise Edition covers all editions of single products (installations) that have been discovered and have a different Product name (Software Model).

I tried 2 solutions.

- I arranged the Single Product Software Models as Downgrade of the Enterprise Edition. Reconciliation ran, but the single products will not be covered by the Enterprise Edition.

- I registered the Single Products as component related to the Parent Enterprise Edition. Also in this case no result.

 

What could be the solution to cover the Single Edition installations with the Enterprise Edition?

 

Thanks for your help.

 

1 ACCEPTED SOLUTION

Engelica Adalia
Mega Guru
Mega Guru

@Anton22  When you set up the Single Products as suite components of the Parent Enterprise Edition, did you put any inference percent? You may also want to check each software discovery model corresponding to those single product software model. ServiceNow will try to normalize it (map it to the Software Model, Publisher, Product, Version) however you can revert it and point it to the correct Software model, Enterprise Edition. 

View solution in original post

3 REPLIES 3

Engelica Adalia
Mega Guru
Mega Guru

@Anton22  When you set up the Single Products as suite components of the Parent Enterprise Edition, did you put any inference percent? You may also want to check each software discovery model corresponding to those single product software model. ServiceNow will try to normalize it (map it to the Software Model, Publisher, Product, Version) however you can revert it and point it to the correct Software model, Enterprise Edition. 

Hi Engelica, 

 

The last part did it, "pointing the Discover Model to the correct Software Model". I anticipated that creating the suite would have done the trick, but the extra pointing was needed. Thanks.

dreinhardt
Tera Sage

Hi @Anton22,

actually both solutions should work, because you can map your use case either way. According to your explanation and the data available in SAMP, however, the solution with the “downgrades” would be more likely (a similar example would be SQL Server Enterprise, which, among other things, covers standard, etc.).

 

As @Engelica Adalia already mentioned, please ensure all discovery models are normalized and the result when running the Software model related link "Linked Discovery Models" is as expected covering the correct discovery model records. Unfortunately, it is not mentioned in the documentation, but if the other editions also have entitlements, these will probably be used before the downgrade rights take effect.

 

Please try to keep only the "Enterprise" entitlement active and run a recon

 

Best, Dennis

 

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