
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2019 07:54 AM
I'm generally curious as to the community's opinion on keeping historical information about previously imaged server and computer class CI records in the cmdb for an accurate representation on the use of an asset for an organization.
Or whether it is best practice to keep data updated based on what the current OS and specs are for a device and overwriting previously collected information.
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2019 12:18 AM
Hi BatMan,
Point 1-->I'm generally curious as to the community's opinion on keeping historical information about previously imaged server and computer class CI records in the cmdb for an accurate representation on the use of an asset for an organization.---> Avoid deleting CIs which are old or historical. Its a good practice to identify such Ci's with Status and some other mechanism.
Point 2-> whether it is best practice to keep data updated based on what the current OS and specs are for a device and overwriting previously collected information --> CMDB must contain fresh and latest data. Stale CMDB will not give you effective information to Run your ITIL Processes. So with every Discovery Cycle and Sync Active CMDB CIs must be updated.
https://community.servicenow.com/community?id=community_blog&sys_id=f7fca6a5dbd0dbc01dcaf3231f9619fa
Regards
RP

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2019 12:11 PM
Hi -- A common rule of thumb is to keep all CI's, but when they are no longer used/needed, set their status to something meaningful to you (uninstalled, removed, whatever...) so your reports/dashboards, etc. don't include this historical data. Why keep it at all? Because what if CI's are linked to incidents, problems, change records? or historical or accounting data/reports over a period of time.
Keeping the CMDB healthy and reliable as a system of record is valuable but that doesnt mean deleting CI's that used to be used... just use the platform to 'mark' them as unused via some of the status fields, ownership fields, etc.
Hope this helps?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2019 12:18 AM
Hi BatMan,
Point 1-->I'm generally curious as to the community's opinion on keeping historical information about previously imaged server and computer class CI records in the cmdb for an accurate representation on the use of an asset for an organization.---> Avoid deleting CIs which are old or historical. Its a good practice to identify such Ci's with Status and some other mechanism.
Point 2-> whether it is best practice to keep data updated based on what the current OS and specs are for a device and overwriting previously collected information --> CMDB must contain fresh and latest data. Stale CMDB will not give you effective information to Run your ITIL Processes. So with every Discovery Cycle and Sync Active CMDB CIs must be updated.
https://community.servicenow.com/community?id=community_blog&sys_id=f7fca6a5dbd0dbc01dcaf3231f9619fa
Regards
RP