install_status is set to retired even if the discovery of the server completed successfully.

[Jha1]

Hello Experts ,

I noticed when I checked one server under the cmdb_ci_win_server it's status changes to retired .Also when I checked the same VM under the table cmdb_ci_vm_instance it's status is on .

I have gone through the audit log and understand as per the activities that its update the status to retire but didn't give me any clue for the same.

I have manually updated the status as installed . 

Kindly let me know how to troubleshoot it  .

Also for install_status I can see we have business rule enabled but that related to Cascade deprovisioned status to server. Is it related to above issue .

I have also followed the below article but its related to different issue ,

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

Please advise !!!

[Anshu_Anand_]

Your issue is similar to the KB.

The server set to retired state when VM is deprovisioned but when VM is UP again, the cascade did not happened to make windows CI status installed .

It will be good if you create a Business Rule so that if the VM instance goes back UP, change the install_status of the windows server record to "Installed" .

Before that contact the cloud admin about the current state of the server and vm and discover it at that time.

Hope its helpful