Does Discovery change the status of a CI to only installed or retired on updates?

[sanjeev20]

Hi All,

I have a question. When discovery discovers any server CI , it creates a new CI record in the server class and the Status field of this CI is set to "Pending install" as this was default value set for this field.

However when the discovery runs again for the same device , it is changing the Status of this CI between Installed and Retired in multiple runs.

I just want to understand that does discovery change the status of a CI only to Installed or Retired. Also we have many more statuses available in the system like Absent, In Maintenance, on order, Pending repair etc.. How does these values are selected for any CI. Is it not via discovery and through some other process automation? And if it is happening via process automation , how do we ensure that discovery status update should be aligned with it.

Please note we have included Status attribute in the reconciliation rule of the Server class.

Regards,

Sanjeev Kumar

[Rahul Priyadars · Accepted solution]

It seems that some known behavior ..

May be these KB can help you.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0951844

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0998780

Steps to Reproduce

• Run Discovery Schedule for Cloud Resources (Vcenter)
• For ESX Servers the status is flip flopping between retired and installed.

Regards

RP

[sanjeev20]

Thank you for your reply, This is helpful. I will review this with servicenow .

Regards,

Sanjeev Kumar