How do I manage multiple software model version with 1 entitlement?

ladrake · ‎11-18-2019

Example:

I have a single software Model for SnagIt version 12 with 10 rights
I have 4 different versions of Snagit 12, 12, 12.1, 12.2 and 12.3
Each software model has 2 device installs
Result: The Software Model version that is associated with the Entitlement is compliant and the other version are not compliant

How do I manage the other versions to show compliance and an accurate license availability quantity in my License Workbench?

Daniel Slocum · ‎11-21-2019

Larry,

The SAM System Property which auto-creates models can be both a help and a hindrance. It's very useful for identification of SW in your environment you weren't aware of, but it can also complicate reconciliation in situations such as you've presented here. You might try turning the property to off in a Dev environment and removing the extra SW Models for which you don't have a linked SW Entitlement. Then go the route I first suggested of altering the Discovery Map section of the remaining SW Model to capture all of the 12.x flavors of Discovery Model you have in your system. Hopefully, this resolves the issue. If not, feel free to reach out to me. My email address is on my Community Profile.

Daniel

View solution in original post

LarryHerrmann · ‎11-18-2019

You could do this a couple of different ways. You could normalize the discovery map, or create a pattern normalization rule that would normalize all dot versions up to the main version. Just make sure your software model is pointing to the correct discovery map.

Daniel Slocum · ‎11-18-2019

The method I recommend to our customers is to alter the Discovery Map attribute on the SW Model. You can choose an out of box map that returns all of the desired values or you can remove the discovery map and fill in the corresponding values yourself.

On the SW Model record clear the [Discovery Map] value. Then, set the [Version Condition] to "Starts with" and set the [Version] attribute to "12".

In the "Related Links" section of the form, just above the tabs showing the related lists, click the "Show Matching Discovery Models" UI Action. This will open a new tab containing all of the Discovery Maps whose related software installations will be considered during reconciliation.

Daniel

mikewhalley · ‎11-18-2019

My assumption is that the software model doesn't reference a SnagIt software entitlement that has a Publisher Part Number associated which means an OOB discovery map will not be auto-assigned and discovery mapping conditions will be based on the Publisher, Product and Version set on the software model record which means that the license calculator only reconciles installs and purchased rights when the installed version of SnagIt = 12.

Therefore, in the Discovery Map referenced in the SnagIt 12 software model record, update Version = 12 to Version starts with 12 and this should address your problem.

ladrake · ‎11-21-2019

Thanks, Larry, Daniel, and Mike.

We attempted that suggested methods prior to submitting my question here with the exception of creating a Pattern Normalization Rule. When we reviewed the possibility of using the Pattern Normalization Rule it seems that we are limited to a single version per publisher. Am I missing something here?