Server Assets vs CIs

[Erick18]

Hello, 

In our environment we have physical servers that are reimaged during the lifecycle of the hardware asset. When the server is reimaged the CI name and other configurations are changed. What is the best practice for retaining previous CI information as well as maintaining the link from the old CI and the New CI to the existing asset record? Should the CI be overwritten each time the server is reimaged? Should a new asset record be created each time with a new CI? 

Thanks,

Erick

[Kumar Premankit]

A server when reimaged its Operating system information will change but hardware details should remain the same such as Serial Number, and model details. In those case the Asset information according to me is still valid.

On contrast, CI should hold all valid information that is associated with the configuration item. So updating configuration items makes sense with new information. 

Foundationally I believe you should refrain from deleting the data in the system instead use lifecycle to indicate the item condition. But every business has its own use cases and a valid reason to do something. I have not come across any document around reimage best practices, they all are perspectives. 

[Sohail Khilji]

Hi @Erick18 ,

This is very common with all infra across the globe. There are certain best practices which needs to be followed here to manage those reimaged devices. 

1. I do not recommend Deleting any CI.

2. I do not recommend creating a new CI with new informations, this may lead to duplication as we use serail number as primary key for assets in CMDB a lot of time. 

3. I Strictly recommed to Update the record with new information based on new Image. Your old information can be tracked and managed in WorkNotes, Audit data etc..

The best why to manager and to retrive the old information when the reimage happens is to update the Old info of the device in Comments field / Worknotes of CI/Asset record before update and if necessary you can have a check box as custom field which indicates if the devices is reimaged every before...

I hope this help...

[Soooie]

Would you expect to follow this same scenario detailed above, when the physical device is replaced under a break/fix (see scenario below), or is different again

example:

server (physical) SN0001 filing role hostname  ACPG32SER0001.

replaced with server (physical) SN0005.

CI record in CMDB Updated:

The Ci record (ACPG32SER0001) would go through an update which would have the attributes related to the asset modified to represent the new device SN0005.

- Reference to the old SN0001 and any other details relevant to SN0001 would need to be added to comments field or work notes, and SN0001 would no longer be searchable in CMDB?

[Sohail Khilji]

True, Whats the business need here to search for old CI after its been replaced after break or fix. if there is a need you can refer the worknotes/comments for historic info of the device. I hope this helps 🙂