What is the best practice to retire Stale Cis which are older than 180 days

[saranyavs]

Hi ,

We are planning to retire Stale Cis which are older than 180 days and still in operational status. More than 50 classes are there in stale list. What are the options to do that and what is the best practice for this requirement. Please assist.

Regards,

Saranya 

[Shivalika]

Hello @saranyavs 

You can use scheduled Jobs which is best option and also in discovery course it's recommended. 

Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket. 

Regards,

Shivalika 

My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194

My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY

[Ashok Sasidhara]

Creating CMDB data manager 'Retire' policies is the OOB solution.

https://www.servicenow.com/docs/bundle/xanadu-servicenow-platform/page/product/configuration-managem...

But if there are so many stale CIs, you should first check if the CI creation and updates in those classes are automated. If it is not automated for some of the classes, then discuss with CI class owners to ensure that the CIs are actually no longer used. In general also, you should discuss with the teams managing each CI class to finalize the suitable CMDB data manager policy criteria to be defined for that CI class.

[abhishekvar]

you can mark them retired based on the "most recent discovery" using "update jobs" , you can try the Archive option too

[saranyavs]

I checked the 'Update Jobs' module, its working fine but can we run this for specific period of time like weekly once..? We need to retire the old CIs in weekly wise.