CMDB CI retirement

[Scott Howes]

Hello,

I want to set select Window server ci's to retired so that Discovery no longer reports then as stale.

From information gleaned on the CMDB, Discovery and CSDM it looks like the way to show a ci as retired is to set the Operational Status to Non-operational and the Install Status to Retired. 

My question is why would you not set both the Operational Status and the Install Status to 'Retired' since that value is in both dropdowns.

With both fields set to 'Retired' the ci shows up in the Discovery dashboard as unrefreshed and when I change the Operational status to Non-operational then re-run Discovery it remains on the unrefreshed list. I would like for it to not show up on the unrefreshed list in the Discovery dashboard and not to show up as a stale ci in the CMDB dashboard.

TIA

[Anil Lande]

Please check below links, may help you:

https://community.servicenow.com/community?id=community_question&sys_id=b11eb9f5db6d9344fc5b7a9e0f96...

https://docs.servicenow.com/bundle/quebec-servicenow-platform/page/product/configuration-management/...

Thanks,
Anil Lande

[cyked]

Change the report filter criteria on your dashboard to EXCLUDE where install_status is retired.

[doug_schulze]

Definitely sounds like a bug or a very important missing OOB feature, I'd suggest opening a case with support... And while you do that, I talk about the CI lifecycle here, if it can help.

[cyked]

the OotB health dashboard for CI rel staleness also includes rels where both parent and child are retired, even though the inclusion rules i've set excludes install_status of retired.  It works in other health metrics though (I have a case open for this).