Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

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

ladrake
Mega Expert

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?

1 ACCEPTED SOLUTION

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

11 REPLIES 11

Hi Again,

It is difficult to troubleshoot your situation through the Community.  The suggestion I made should work just fine unless you've created a SW Model for each version.  If that is the case, you'll need to use Upgrades/Downgrades to accomplish your goal while being sure the distinct SW Models do indeed return corresponding Discovery Models when clicking the "Show Matching Discovery Models" UI Action.

Daniel

ladrake
Mega Expert

Thanks again, Dan.  I appreciate your thoughts on this.

 

We did consider using downgrades and tested it.  We didn't get the results that were expected and thought that we were overthinking the process.  Also, ServiceNow is auto-creating the Software Models - not sure if that is a good thing, or if we should consider trying to disable that feature.  What are your thoughts?

 

Larry

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

Dan, this worked!  We will wash, rinse, and repeat...

 

Thanks for your help.  It is greatly appreciated.

 

Larry

Hi Daniel.

I'm facing a similar challenge and like the idea of setting com.snc.samp.automaticsmrcreation to "false" to prevent Software Models from automatically being created.  Per your comment "It's very useful for identification of SW in your environment you weren't aware of", couldn't we rely on "Software Discovery Models" which are also automatically created to answer this?  And from that knowledge, we can create new "Software Models" as needed?

Thanks,

Ron