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

[Soooie]

Thank you for your previous comments.

Delving a little further.   
is this due the asset details being managed within a seperate Asset Database that is linked and updated in real time when a Ci record is changed in CMDB?

The scenario would be a little different when an end point is returned to the warehouse (no longer In Use)?

The issue I have is. The same device can be redeployed under a different hostname (has the same (SN YYT0001, A/T AAA0001)

example

was ABCW10AAA0001 connected to domain ABC

Now redeploying as WWCW10AAA0001 connecting to domain WWC.

Would you expect old CI (hostname) to decommission and a new CI (hostname) to be created.   Both would have the same SN, A/T, or the endpoint hostname would change so not to create duplicate on S/N?

maybe I am confusing the Asset Management and Configuration Management

[Kumar Premankit]

I think you are confusing Asset and CI. Based on reimaging information, what you are doing is updating your CI, asset information has no dependency on the configuration piece. It is still going to be hardware with a specific model. 

It would make sense to update the CI in the scenario above with new information as the configuration is updated. Always remember Asset and CI hold a 1-1 relationship.