Snow Inventory Server version 6.9.4 introduces enhancements to the computer identity management module. In a limited number of cases, depending on pre-existing data, the new implementation might generate new identities, duplicating some computer records. 

These discrepancies will need to be resolved in Snow License Manager, either by manually deleting the original computer records or by leveraging the product's Quarantine Management capabilities. This article outlines potential causes of such duplicates and provides guidance on resolving them.

Possible reasons for data merging and duplication

• Multiple identifiers changed simultaneously in a Snow Agent snowpack, leading to the creation of a new record.
• A single identifier changed in External SIM data when it's the sole inventory source (i.e., no Snow Agent data), resulting in a new record.
• Using cloned images with identical identifiers and changing the hostname can cause data to merge. In such cases, enabling Hostname Only mode on one or more identifiers is recommended. This scenario is indicated by a high IdentityUpdateCount in the inv.AgentManifest table.
• Devices without unique identifiers (e.g., Linux devices) reported prior to version 6.9.4 created unique identities both with and without Hostname Only mode. In version 6.9.4, these devices may require Hostname Only mode to prevent merging.
• A device with Snow Agent reported in prior to version 6.9.4, has since been reimaged (e.g., with a new SID) but retains all other identifiers. If Hostname Only mode has been enabled since the device last reported in, and there's no Hostname Only lookup present, it may create a duplicate.

IdentityUpdateCount

The IdentityUpdateCount value in the inv.AgentManifest table is updated in the following scenarios:

• When External SIM data processed prior to version 6.9.4 is updated with new topology and lookups, the count increases by 1. This should occur only once, as the old data is overwritten.
• When the system cannot match on the topology, the count increases by 1. Frequent increases suggest that data is merging and may benefit from enabling Hostname Only mode on one or more identifiers. This scenario is common for devices without unique identifiers (e.g., Linux devices).