Some users may have issues creating a community account. For more information, please click here.

Deduping rules in Normalize

Deduping rules in Normalize

Summary

This article discusses the deduping rules in Normalize.

Synopsis

What are the deduping rules in Normalize and how do they work?

Discussion

When a single data source or multiple data sources are used, there is a possibility that the assets may have duplicates. To eliminate duplicate records from your inventory, there is an option to specify deduping rules and how to handle duplicates when they are discovered.

You can select a deduping key from the deduping key drop-down. Refer to the screenshot below. The available deduping rules are:

  1. Hostname (domain\machine)
    1. Domain + Hostname
    2. Hostname + Serial Number
    3. Hostname
  2. Serial Number
    1. Serial Number only (except Virtual Machines), and for machines without a Serial Number.

If Domain/Machine is selected:

  • 1st level of de-duping: Normalization rules check if there are duplicate machines with the same Domain and Hostname.
  • 2nd level of de-duping: then Normalization rules check if there are duplicate machines with the same Hostname and Serial Number.
  • 3rd level of de-duping: lastly Normalization rules check if there are machines with the same hostname.

If Serial Number is selected

  • Normalize does a simple deduping based exclusively on the serial number. With this option, Normalize does not dedup Virtual Machines and machines with no Serial Number.

User-added image

Labels (2)
Was this article helpful? Yes No
No ratings
Comments

Does "To eliminate duplicate records from your inventory ..." means, all data linked to this device (HW & SW information) from the other inventory source isn't processed/used by BDNA - or is just to avoid multiple devices with the same Name/SN, but includingt he full set of  information over all sources.

 

Thanks 

Version history
Revision #:
3 of 3
Last update:
‎Jul 30, 2020 08:05 PM
Updated by: