De Dup tasks for HAM

[Daniel Grande]

We are noticing an abundance of duplicate items in our Hardware Asset tables:

We have been going through and manually remediating these items. In some cases we have deleted a record and the CMDB and discovery process recreates the record. I have checked the identification rules in CMDB and there is no reason for these duplicates to be created and not recognized. We are not seeing the duplicates in CMDB only in Hardware Asset tables. 

2 questions: 

1. Can we create de duplication tasks similar to the ones in CMDB to run on Asset tables? Currently we have no de dup tasks showing up in CMDB. All duplicates are in Hardware Assets tables. 

2. How do I prevent the CMDB from creating these duplicates?

[Ashok Sasidhara]

Deduplication tasks are available only for CIs and it is not there for assets. From the screenshot, i can see that the configuration item Name is same for both. As the serial number is also same in the screenshot, please review whether the identification rules are set correctly for the Computer class in CMDB. Following are the main considerations for preventing duplicates in CMDB:

1. Review and refine identification rules if needed.

2. Use service graph connectors for integrations. Then only integrations will go through the IRE and consider the identification rules which are configured. Without service graph connectors, customizations will be required for integrations to force them to follow IRE.

3. Use integration hub ETL for manual data import. This follows IRE while normal data import does not follow IRE & so will not consider identification rules.

Also review the business rules & system properties mentioned in following URL to check whether how they are set up in your instance is leading to the creation of duplicate assets from CIs:

https://docs.servicenow.com/en-US/bundle/vancouver-it-asset-management/page/product/asset-management...

[DavidWallace1]

Notice that in the screenshot your 2 asset records have different model categories.. check the definitions of those model categories as they may both be mapped to the same CI class...