ServiceNow Discovery & SCCM discovery overwrite software installation records

[shivani42]

Hello All,

We have seen SN discovery & SCCM discovery overwrites software installation records. In software installation table, we have seen duplicates records but with different discovery source and versions. 

For example, CI is discovered by ServiceNow. But the related software installation is being discovered by both the discovery (SCCM & SN). It has two records for WinRAR software. 

ServiceNow - Winrar Version - 7.0

SCCM - Winrar Version - 7.00.0

That is creating duplicates.

We also have the property glide.discovery.software_sccm_managed property enables in our instances. But still, can see duplicates records being inserted.

Can anyone have any idea??

How we can resolve this.

Regards,

Shivani

[Community Alums]

Hello @shivani42 ,

You can resolve these duplicate entries by checking if this  scheduled job SAM - Deduplicate Install Table is running or not in your instance.. This job is already running on all the instances and you can verify there no of the duplicate records where in both record "active install" field is true (Job will make one record as active true and other as false).

But to avoid any future record created on the software install table you need to turn on this specific property as per ServiceNow.

Property name - com.snc.samp.ire.datasource.integration

You can find the official servicenow doc below

https://docs.servicenow.com/bundle/vancouver-it-asset-management/page/product/software-asset-managem...

To find out if a install is duplicate or not - https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0958768

Thanks,

Subham

Please mark this helpful if this information help you in anyway.

[debendudas]

Please refer this servicenow doc: https://docs.servicenow.com/bundle/vancouver-it-asset-management/page/product/software-asset-managem...

[dreinhardt]

Hi @shivani42 

As already mentioned by @debendudas  and @Community Alums , this is an OOTB function of SAMP and/or Multisource- CMDB.

Only in the case of software installation, the data is not overwritten/updated, but rather an entry is created for each data source for a software package. The above-mentioned job “SAM - Deduplicate Install Table” is the centerpiece of the entire process, as it ensures that only a single installation exists as active for processing in the Reconcile and all others are deactivated. This job runs daily and additionally as part of the Reconcile to ensure that all software installations have been processed and duplicates disabled.

Important Note: The job mentioned can only work successfully if the Discovery Models are normalized accordingly - since the check only goes to the normalized fields for Publisher, Product, Edition and Version. It is highly recommended that you regularly check and normalize the Discovery Models for all products in scope.

ServiceNow SAMP Ranger Session

Understanding Software Installation Data (youtube.com)

Software Discovery Models used by SAM (youtube.com)

Best, Dennis

[shivani42]

Hello All,

Thanks for your responses.

Is there any way, we can tell discovery not to insert the software data if we already have the software available in Software installation??

We are making sccm as source of truth. We want if a Ci has both software installation records discovered by SN & SCCM both, we want to make SCCM to insert the data instead of SN.

Thanks,

Shivani