ServiceNow Discovery setting installed status

[stephenwinter]

Hello

We have encountered our MID Servers updating the installed status for servers to "installed" when they are discovered and are trying to understand if this is expected behaviour and how it's controlled. For instance, which states is it happy to leave a server in. I can understand changing from "retired" to "installed" if the server is found, because it's clearly not retired.

We are trying to find documentation on this, but have been unsuccessful. Can anyone point us in the right direction.

[misty]

We are also seeing this issue.  Very interested in what is found.

[RK25]

I am in the same boat. Did you get a resolution on this? Hardware status is also changing for us, I believe it depends on the Installed status,

[Mateus Oliveira]

I am very much interested in the root cause of that case you opened as well @jimmillet . Please, let me know if you received any news from ServiceNow on this.

[Mahur Silva]

Does anyone have any updates on the topic?

[Thomas Buecker]

Hi we had the issue as well with one of our customers.
From my püoint of view they are 2 "healthy" options:
Don't mess with the states - let discovery do it's job - only set a status when you set the device offline (Repair, retired, ...)
Set all states manually and protect all state fields against updates through discovery. You can achieve it with Reconciliation Definitions - it's a menu entry and not avaiulbale in CI Class Manager

Everything else will be complicated and maintenance intensive on the long run when something get's changed