Facing a challenge in CMDB cleanup. Reconciling Real Server States vs. Recorded Status
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2024 10:30 AM
Hey experts,
I'm working on cleaning up our Windows server data in CMDB and encountering some lifecycle status inconsistencies due to historical decommissioning processes not being followed properly. I've identified two main scenarios I need help with:
Scenario 1:
- Servers marked as Operational/Live in CMDB
- No ping response
- Not found in DNS
- No recent discovery data Question: Is it reasonable to update these to Retired (lifecycle) and Non-operational? This seems straightforward but want to confirm.
Scenario 2 (More Complex):
- Servers marked as Retired in CMDB
- Successfully pings
- Found in DNS
- No recent discovery data Question: What's the best way to validate if these servers were redeployed and should be marked Operational? What additional checks would you recommend before changing their status?
Our goal is to achieve accurate lifecycle statuses while being careful not to incorrectly mark active servers as retired or vice versa.
Any guidance on:
- Additional verification steps beyond ping/DNS checks?
- Best practices for handling potential server redeployments?
- How to prevent this situation in future?
0 REPLIES 0