Vmware Instance or ESX Server "Install_status" is updated to Retired but not making an Audit entrySummaryVmware Instance table field "install_status" is changed from "Installed", or any other value, to "Retired". The install_status is update is not reflected in the Audit History. In the following image see a record where "install_status" is "Retired", however the audit show the last update is from "Retired" to "Installed". InstructionsThe Sensor "VMWare - vCenter Datacenters" marks CIs not returned (Vmware Instance or ESX Server) in the latest discovery as "Retired".Out of the box, the script will directly run a SQL commands in the database. As this will be done directly on the Database, no Business rule will be triggered. Hence, these updates will not be captured in the audit as well. From VCenterDatacentersSensor script include: // Mark stale VMs as 'retired' gr = new GlideMultipleUpdate('cmdb_ci_vmware_instance'); gr.addQuery('vcenter_ref', vCenterSysId); gr.addQuery('object_id', 'NOT IN', vmObjIds); gr.setValue('install_status', '7'); gr.execute(); // Mark stale ESX servers as 'retired' esxGr = new GlideMultipleUpdate('cmdb_ci_esx_server'); esxGr.addQuery('vcenter_ref', vCenterSysId); esxGr.addQuery('object_id', 'NOT IN', output.hosts); esxGr.setValue('install_status', '7'); //Retired = 7 esxGr.execute(); The VCenterDatacentersSensor script include can be updated to avoid the Configuration Items being marked as retired. Customized script includes are not updated on upgrades and would be owned by the team which updated the script. In this case, it is best to leave the script Out of the box as this is expected behavior.