Ignored installs

[BelindaViegen]

Hi,

I have a lot of ignored installs in SAM Pro with 3 different reasons I don't understand: 

• Inactive install - Even if an install is 'inactive' (what does this even mean?) we should pay for the license if it is installed
• Installs for Microsoft SQL Server on device just having SQL Server component - SQL components also need a license for the server so this reason doesn't seem valid
• Unsupported cloud install - these are installations on Azure VM's which also require a license. 

Can someone shed some light on this? I am kind of lost and thinking that the compliance position in SN isn't valid because of these ignored installs

Thanks,

Belinda

[dreinhardt · Accepted solution]

Hi @BelindaViegen,

please check the following table to get more details about each Unlicensed reasons [samp_unlicensed_reason]

• Inactive install - Even if an install is 'inactive' (what does this even mean?) we should pay for the license if it is installed
  • "Inactive Install" is an outcome of the deduplication process of SAM Pro. Software installations that are discovered on the same configuration item, but from different discovery sources, are considered duplicates. The value in the Active Installs column for only one of the duplicate record is set to true. The remaining duplicate entries for the software installation record is set to false.
  • Resolve duplicate software installations in the Software Installation table

• Installs for Microsoft SQL Server on device just having SQL Server component - SQL components also need a license for the server so this reason doesn't seem valid
  • (Internal SAM Pro process) This record is required to handle the SQL Server component requirements as mentioned by yourself
  • Check the table [mssql_components_info] for all details about detected components
  • SQL Server component editions discovery

• Unsupported cloud install - these are installations on Azure VM's which also require a license. 
  • Please reach out to the ServiceNow support and request more details why your product is not supported when running a VM in Azure

Best, Dennis