How to best update the entire CMDB when a server is decommissioned or retired?

[Bob D]

When we decommission a server in our environment,  we update the Status of the Configuration Item (Windows Server or Linux Server, for example) to Retired and the Operational Status to Non Operational.  No issues there.   But what should we do about all of the Configuration Items related to this now-decommissioned server?   They are not updated after the decommission and it causes issues.  For example,  the software instance counts (cmdb_software_instance) don't update...the CMDB still thinks software is installed on the decommissioned server.   Same thing for database instances, DNS entries, storage device usage, and so on...all these CIs and tables contain data as though the decommissioned server is still active,  This affects reporting and decision-making.

How does everyone handle this?   Do you have a way to update all of these related CIs when you decom a server?  Or do you have a way to filter out data related to decommed servers when you run reports?  Do you just live with the issue?   tia for your thoughts

[DaveHertel]

Hi -- 1 approach is to implement business rules that look for server class w/'decommission' status (or whatever) and the loop thru related CI items (software or whatever is related to the CI record) and take action on that related CI.  it might be deleting it (like if its  NIC... you probably don't need that non-existant CI laying around since it likely doesn't affect anything downstream like Asset Mgmt) or flipping a status, etc.    Bottom line -- some biz rules may be needed to do some housekeeping when the main CI is decommissioned.

Hope this helps?