How and when install_Status is set to absent for CIs and its related CIs

[NirmalSharma]

I am trying to understand a mind boggling fact that how install_status is set to absent for any CI in ServiceNow. We are running Discovery; I see discovery MID server changes the install status from installed to absent. I now want to trace it back as why that happened and who were the players in doing so. Script includes, business rules etc.

I am seeing 17k+ CIs marked as absent by Discovery in our environment. This is a huge concerning thing for us and I am looking for some assistance/

[Mannapuram]

@NirmalSharma  Posting another thread from Community. 

Solved: Install status as Absent - ServiceNow Community

Also, I tested this by changing the 'Install Status' to Absent, on my test instance from a course. 

Ran the discovery again, the Install status is set back to ' Installed'.

This means, the infra marked as 'Absent' is actually not reachable to Discovery. Check for one CI, whether IP address associated with that CI is touched by Discovery. 

[NirmalSharma]

Good One. Adding next to it do someone know what sets the operations status of the same CI as Retired. For your example CI did Operational status changed based on the install_status change?

[Mannapuram]

@NirmalSharma  The Install status is driven by Discovery. The operational status is driven by Staleness rules or manual entries. 

In my case it was manually changed to 'Retired' and it remained there even after the discovery run

[NirmalSharma]

ok...so retired gets set based on "something" but does not get set to "Operational". Mystery to me.