Stale Records & Auto-Retire - Should Auto-Retire Be Used for Stale Network Devices?"

[VIvek V]

I have reviewed the analysis of stale network records and identified multiple devices marked as stale. Can we implement an auto-retire process for devices that are not present in the IP Address Management system or monitoring tools like SolarWinds?

Would auto-retirement be the most effective solution for addressing this issue?
Should we take any additional factors into consideration?

[Nikhil Bajaj9 · Accepted solution]

Hi @VIvek V ,

Check this and you will get your solution- https://www.youtube.com/watch?v=Hndaax8qf60

If my answer helped you, please mark it- solution accepted. 

Regards,

Nikhil Bajaj

[AJ-TechTrek · Accepted solution]

Hi @VIvek V ,

* Would auto-retirement be the most effective solution?


No, not directly. Best practice is semi-automated retirement via CMDB Data Manager + review tasks. Fully automated retirement should be used only when you are 100% confident in your data sources.
* Additional factors to consider?
Yes:
* Discovery schedule gaps (e.g., mid servers down).
* Devices with changed credentials but still in use.
* Business criticality — auto-retiring without owner validation can impact IT operations.
* Regulatory/audit needs — ensure you retain historical CI records for compliance.

Best Practice Recommendation
 Implement CMDB Data Manager Policy with conditions based on last discovery + monitoring/IPAM checks.


 Generate tasks for CI Owners to validate before retirement.


 Once maturity is high, consider moving toward auto-retire for very low-risk classes (e.g., transient cloud VMs).

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
 

Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025

[Nikhil Bajaj9 · Accepted solution]

Hi @VIvek V ,

I hope you have reviewed my answer as well.

[Nikhil Bajaj9 · Accepted solution]

Hi @VIvek V ,

Check this and you will get your solution- https://www.youtube.com/watch?v=Hndaax8qf60

If my answer helped you, please mark it- solution accepted. 

Regards,

Nikhil Bajaj

[VIvek V]

@Nikhil Bajaj9  

Can you help me to understand on can we convert this process request based ?

Thanks in advance 

[VIvek V · Accepted solution]

HI 

Can you please help me to understand can we convert the flow designer process to RITM request ?

Regards
Vivek V

[AJ-TechTrek · Accepted solution]

Hi @VIvek V ,

* Would auto-retirement be the most effective solution?


No, not directly. Best practice is semi-automated retirement via CMDB Data Manager + review tasks. Fully automated retirement should be used only when you are 100% confident in your data sources.
* Additional factors to consider?
Yes:
* Discovery schedule gaps (e.g., mid servers down).
* Devices with changed credentials but still in use.
* Business criticality — auto-retiring without owner validation can impact IT operations.
* Regulatory/audit needs — ensure you retain historical CI records for compliance.

Best Practice Recommendation
 Implement CMDB Data Manager Policy with conditions based on last discovery + monitoring/IPAM checks.


 Generate tasks for CI Owners to validate before retirement.


 Once maturity is high, consider moving toward auto-retire for very low-risk classes (e.g., transient cloud VMs).

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
 

Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025