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.

[Jatin Sohane]

Any updates on this?

[MattSN]

When a new CI is discovered, it uses the default value from the install_status defintion of the data dictionary.

Also see:

https://www.servicenow.com/community/now-platform-forum/change-default-ci-status-from-installed-to-c...

[Michael Craven]

We are also seeing the same thing.  Everything seemed fine until recently.  What Instance version and Discovery pattern store app are you using?  We're on Tokyo and 1.0.90.

We use a custom status called "Pending Install" as the default status to allow for qualification and other paperwork.  Then the server is manually updated to "Installed".  In our process, we don't ever want Discovery to update the status. 

[jimmillet]

We are also seeing the same issue. Our default for install_status is set to 4 (Pending Install), but Discovery is creating CI's with install_status=1 (Installed). We have opened case CS6500827 with ServiceNow support, but no root cause or resolution yet. We are at Tokyo. We never saw this behavior before Tokyo.