Retired ESX server will be changed to "Installed" by servicenow discovery

[creelyu]

Hi We have a ESX server, it is changed to "retired" via customer request. However, it is changed to "Installed" after the discovery. Could anyone know where is the code that changes the ESX server's status back to "Installed". I did a test that if the ESX server is changed to "In stock", "On order" or any other status value other than "Retired", it will not be changed to "Installed" by discovery. However, if it is changed to "Retired", it will be changed back to "Installed" after discovery. But I did not find the code behavior in discovery script include. If anyone knows the code, please help to tell me. Thank you.

[doublelight]

I will advise you exclude the retired servers from discovery rather than making changes to the OOTB behavior of ServiceNow discovery. The beauty of discovery is to help with reconciliation, auditing and ageeing CI rules. 

Thus, so long the device is live and active on the rack it will be discovered and report back.  

[creelyu]

Thank you for your advice. I just want to know where is the code so that I can tell the cause correctly. Even I guess it is a OOTB code behavior but I can not show the code to customer which does not make sense.

[Rahul Priyadars]

+1

Do not make changes in OOTB behavior of Product when ESX is still active on N/W and we just trying to manipulate the data in CMDB record. 

Use Global Exclusion IP list which will stop discovering this ESX or a List of IPs.

Regards

RP

[creelyu]

ESX server's ip address is not set in discover schedule directly. Vcenter's is set up instead.  So Global Exclusion IP list will not work.