Duplicate ESX records(One in Server Table and other on the ESX table)SummaryThis article explains how to prevent duplicate ESX server records from being created in the server table and the ESX server table during vCenter discovery. Scenario: You already have the records in the server table.When you perform a vCenter discovery, the discovery process doesn't consider the existing records in the server table.This leads to duplicate records being created, one in the server table and another in the ESX server table, both with the same ESX name. Steps: Identify the Correlation ID Value in server table(if Its generic or empty) If the correlation_id field is empty /generic for most or all of your existing records, follow these steps: Navigate to your system properties.Search for the property glide.discovery.alter_esx_server_index.Set the value of the property to true.Save the changes. Explanation: When glide.discovery.alter_esx_server_index is set to true, the ESXHostsSensor prioritizes the serial number when identifying existing ESX server records during vCenter discovery.This ensures that duplicate records are not created based solely on the ESX name.The CI class reclassification process is also considered during this update.