Discovery updates the older Hostname while the IP is reused.Issue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Discovery is modifying the Ci names with the old decommissioned CI names with same IP.Actual CI name for example was "ABC" in CMDB. After the discovery scan, the CI name "ABC" is updates as "ctx_test". Release Kingston Patch 14a Cause Upon reviewing the system property "glide.discovery.use_probe_results_cache" found it is set to true, hence the Discovery looks at the available cache based on the IP and populates the basic Data to CMDB using the cache rather using the real output, hence we might see the issue. Resolution Delete the CI which is populated with the older hostname.Navigate to "sys_properties_list.do" and search for "glide.discovery.use_probe_results_cache" https://<instancename>.service-now.com/sys_properties.do?sys_id=68b748eddf511100079367f53df2635e&sysparm_view=&sysparm_record_target=sys_properties&sysparm_record_row=9&sysparm_record_list=nameCONTAINScache%5EORDERBYname&sysparm_record_rows=17 Open the "glide.discovery.use_probe_results_cache" record and set the value to "false"Execute a new Discovery on the IP