PPN number and installed software

[nicknick]

Hi,

We have PPN number entered so model got created but as per Discovery map selected in software model table software installations are not getting selected from cmdb_sam_sw_install table.

What are the best practices to assign the installed software to selected PPN number

Do we need to take any manual action to normalized the product as per disocvery map values or what could be done to get the valid list of softwares.

or we shold not use PPN number in this case?

Regards,

Nick

[Onkar Pandav]

Hi,

Please check below link.

https://community.servicenow.com/community?id=community_article&sys_id=99282c46dbded8d011762183ca961...

Also check the pdf attached herewith that may help you.

[nicknick]

Hi Onkar,

Thanks for the reply. But query is as below which makes me confused

Customer says if PPN number is there for big customers like Oracle and Microsoft, we need not to normalized the software in nay case . All software installation should be mapped to software model automatically.

How it works in other organization ? do you need to map the model to installed software manually for big customers as well?

Can anyone comment on this.

Regards,

Nick

[Louis R Ronzitt]

This reference may also help.

KB0790305:  https://hi.service-now.com/kb_view.do?sysparm_article=KB0790305

We continually submit cases when we find we need updates to Publishers, Products, Publisher Part Numbers, Discovery Maps, and Lifecycle Dates within the products table (samp_sw_product) and overtime as those products are updated by ServiceNow we look for the corresponding custom product (samp_custom_sw_product) we may have created in the interim and then remove it/replacing it with the now updated product/product information.

[Daniel Slocum]

Hi Nick,

You've hit on a key process needed to validate your SAM configuration. For every Software Model, you should plan to go through a validation effort that identifies if the Discovery Map (DMap) in use meets your needs. that validation effort starts with a review of the Reconciliation results as presented in the License Workbench. If the results for a software title are as expected, move on. If they are not you will want your first check to be to see if the DMap is returning the expected Discovery Models.  In your scenario the creation of the SW Model by supplying the PPN in the SW Entitlement form auto-populated a DMap value into the SW Model.  That DMap, may or may not fully meet your needs.  In the question you posed, it appears as if the DMap is not returning all of the Software Installations you expect. 

Let me make a quick correction to what you wrote in your original question, the DMap does not directly return SW Installations from the cmdb_sam_sw_install table. Instead, it functions as a query against the Discovery Model Table. When Reconciliation is executed, the DMap is used to query Discovery Models. The SW Installation records related to the Discovery Models returned are bounced against the rights owned and a compliance position is calculated. 

This leads us to the following:

• Entering a PPN will in most cases, create a SW Model and populate the DMap value
• That DMap should be validated to be sure it returns the correct Discovery Models reflecting all of the software that is licensed by Software Entitlements related to the SW Model.
• • You can see what Discovery Models will be utilized during Reconciliation execution by clicking on the "Show matching Discovery Models" Related link.
  • Choose a different DMap or manually set the attributes set by the DMap if the matching Discovery Models are not fully reflective of the software that is licensable by the Software Entitlements linked to the Software Model.