active install is false in cmdb_sam_sw_install table

[pavan Punna]

Hi all,
I'm investigating install records where active install is false even though there appears to be only one software install row per Ci.
What I already validated so far, 

• Affected records are from Discovery source = ServiceNow.
• all of my same records have deduplication process = true
• I manually executed sam- Deduplication install table job and rechecked sample false rows they remained active = false and did not appear to be touched.
• for the sample records where active install is false, primary install is empty, discovery model is normalized 
• older inactive rows have software model source = empty
• a smaller newer subset has software model = calculator and these are active install true

My questions:
1. If a software install already has deduplicated = true, under what conditions can it still legitimately remain active = false when there is only one visible install row on the CI?

2. what is recommended next step to find the root cause of this and possible solution?

[dreinhardt]

Hi @pavan Punna , facing a similar issue and it was related to a not normalized discovery model (product or publisher) was missing and because of this the engine wasn’t able to process the data. I need to take a look into the SN KB and get back to you.

could you share a screenshot of the sw install and the linked discovery model details.

thanks, Dennis

[pavan Punna]

You are right most of them are not normalized.
Iam aware that The Tanium integration only updates these attributes on the [cmdb_sam_sw_install] table:

Display Name, Version, Publisher, Installed on, Last scanned, Discovery source

Perhaps there's a separated job that updates the assigned_to on the Software Installation records called SAM - Set 'assigned_to' Field on Licensable Install Records but when i checked there are lot of software installed which have software product licensable but still assigned_to is empty.
Do let me know if you could find a solution.

[blanm]

Hi there, 

I have had to update some of my SGCs to deal with the assigned_to field. For example, the SGC for Intune has two ETL maps that we use: SG-Intune Device Reports and SG-Intune Software Reports. In the Device Reports map, there was a mapping to software installation table. However, the OOB script was using a user lookup operation using two raw data fields in the import and those fields didn't match up to our actual data, so it never found a user's sys ID to add. I had to make a custom field/operation that used the correct raw data fields to make a match on the user table. I then replaced the OOB field mapping to my custom one and I started seeing assigned_to correctly fill in. 

This only affected the Device Reports for us, which only adds Windows OS records to the software install table. The Software Reports, which adds all other software found on a device by Intune, lined up correctly so I didn't need to adjust it. 

If you are missing a lot of assigned to data, I would check your raw data mappings for your third party data sources.