Software installation table - Fields/data required for SAM pro

[Naresh Kumar6]

 Hello everyone!

I am trying to make the software installation before validating the license workbench for SAM pro. 

May I know what are the key fields which we have to make sure we have the right data in the software installation table?

Is there any recommendation from Servicenow for software installation fields mandatory for SAM pro? 

What is Is Used and the last scanned fields mean?  do we make sure those have the right data? 

Any information is appreciated!

[Daniel Slocum · Accepted solution]

Hello Naresh,

I'm not sure I understand what you mean by "make".  SW Installation records are primarily created as an output of the SCCM Integration's "Software" data source or from the ServiceNow Discovery integration. There are other integrations available on the ServiceNow store, which also write software installation records.

From your description, it seems as if you are trying to create sw installation records either manually or via an import set.  This is not a solution recommended by ServiceNow.  Ideally, you'll have a discovery source populating the CMDB to form the foundation of the ServiceNow Platform. That discovery source will identify not just CI details and CI relationships, but also the software installed on a CI.  That software is written to the sw installations table.  

The SAM reconciliation engine leverages data from the CMDB as well as the sw installation table to calculate a license position. Without the full picture of a well maintained and correctly populated CMDB, you will not achieve optimal results.

All of that said, you can import into the sw installation table, though the use case should be very limited and rare. I've not done an import into this table myself, but I believe you'll want to be sure to populate the following attributes for which I'm providing the Field Label, not the SQL name: Installed On (sys_id of the ci the software is installed on), Publisher, Version, Display Name (Name of the software title (space) version).  Be sure to leave Business Rules as active during import.

[servicenow begi]

Hello, I have a followup question related for software install table.

The issue is, we are populating server CI using servicenow discovery in the samp_sam_sw_install table. We are getting "Publisher, Product, Version  and Installed On" information. But we are unable to bring "Assigned TO" information, it seems like Assigned To field is not discoverable from our client source system.

My question is :

- How is the SAM pro process impacted if we cannot bring ASSIGNED TO details for end user devices and servers(datacenter software). 

- Is it mandatory to bring Assigned To information