'Ignore installs' field in the Software product form - Software Asset management Pro

[shank1]

Hi

What is the use of the field 'Ignore installs' on the Software product form. How will it work. 

[dreinhardt]

Hi @Christina Guidr ,

when you exclude the installs from your main software model to get accurate results … how does SAM Pro handels the exclude installs? Do you work with two models and the one to capture the installs is set to „license under management True?“

Thanks, Dennis

[Christina Guidr]

Hi Dennis,

I didn't have to create separate software models to exclude the installs - doing the product install condition overrode the software models.  I am still not 100% happy with the solution as in the workspace the installs show as required action even though says we are compliant.  If I find something better I will try to remember to post it!

[Cesar7]

I have logged a case with ServiceNow for this  topic.  Where the metric is set to Resource consumption or User subscription then SAM should automatically ignore the detected install instances and only use resource values.   The only clean workaround that I have found is to create a custom product and configure this as subscription with ignore install set to true.  This configuration allows us to use the discovery model and software models without the need for any hacking as long as we select the custom product definition,

Someone suggested that we should log a ticket where a product definition is configured incorrectly.  Good idea but I have so many products where the product definition is wrong I certainly do not want to waste any time notifying ServiceNow and then having to endure the countless meetings to justify the ticket.

[Christina Guidr]

Well at least what you wrote made my process less clunkier, thanks!  One step instead of two changing the metric to user subscription - the results are the same - the workspace shouldn't show installs requiring action.  I have logged a case once for incorrect content library info (an MS product calculating at per device instead of user subscription) - if you provide enough corroborating information and screenshots they just fixed it for me without a meeting.  Now for other items it is too much effort like Entrust certificates - all their part #s all went to one software model even though all the different kinds existed in the content library so I was not able to do compliance on each type of certificate without creating custom part #s to override their data (same for Cisco Digital Network Architecture licenses).