decomissioning servers and children from CMDB

[oscarestrada]

we need your advice on best way to decomission main asset classes and children from CMDB.   Seervicenow provides a mechanism to remove (delete) an asset (for example a server) and all it's children.   what we want to do is to mark that device AND all its children as 'Retired' and 'Non-Operational', whithout removing from CMDB.   we need to avoid "orphan" entries.

this is critical to CMDB data quality.

what features avaible in Servicenow have you used to accomplish this and if this is the best approvach to address this need?

Any help is veery welcome

[Patrick DeCarl1]

Oscar,

OOTB if you make the asset record retired, it will auto update the CI record status value to retired also. You can create a business rule that is trigger when status on CI record is moved to Retired to update the Operational Status to "Non-Operational".

[oscarestrada]

Hola Patrick, I tried this immediately but there seems to be no connection between the Asset and the CI; I 'Retired' the asset and the Server still shows Install and Operational. I check the Asset-CI mapping and the maop already exists.   Anything else you think needs to be done?

In addition, will this mark the CI (Server) components as retired?   i.e. Disk, Network Cards, etc. ?

[prabhash_snow · Accepted solution]

Hi Oscar,

Are you also capturing the sub state for asset and CI ?

Check this :

1. go to Asset Ci Hardware State Mapping and filter it with "asset_state=7".

2. You will see that there are sub state values defined for both Asset and CI.

3. Check if you are following the rules.

// OOB this thing should work properly, if everything looks fine but still you are facing any issue, check for any customization in your instance that might be blocking the OOB functionalities.

Regards,

Prabhash

[oscarestrada]

Thank you Prabhash for your insight on this. please review my comment to Patrick's response and if you have additional advice on this please share.

Regards,

Oscar