Re-using an Asset for a new CI

jasondrisko
Giga Contributor

‎03-02-2016 11:36 AM

Let's say you have a physical server in your data center that's the Microsoft Exchange server. The company decides to move away from on-premise Exchange and the server is completely wiped of all applications and operating system. The CI should be marked as having a Status of "Decommissioned" or something similar in ServiceNow, and the Asset part has a Status of "In Stock" and Substate of "Available".

The company decides to re-use the hardware to build a new ServiceNow MID server. The old CI for the Exchange server should be left "as is" for historical records and a new CI should be created for the MID server. In ServiceNow how does one go about creating a new CI for the MID server, but tie it back to the Asset that was formerly the Exchange server?

Out of the box the following is true:

  • The Asset field in the CI record is read-only.
  • Creating a new Asset or CI will create the complimentary one as per the Model they are based on.
  • Deleting the Asset only and leaving the CI is possible.
  • Deleting the CI will remove the Asset as well.

Unless I'm missing something, you have to customize ServiceNow to allow for Assets to be re-used and associated with new CI's, correct?

0 Helpfuls
  • 1,317 Views
3 REPLIES 3

conmic
Mega Guru

‎08-29-2016 08:34 AM

Hi Jason,



From a process point of view: it's still the same CI, just with another purpose. All this should be recorded under the same CI record.


What is the benefit of creating a new CI? Anyway the history of the CI should be saved in the audit data and CI activity.



EDIT:


The "asset" field on a CI (and "CI" field on an asset) are just protected by the "Read only" checkbox on the dictionary entry.


So you could just temporarily un-check it and then change the values to your needs.


kiranbahl27
Kilo Contributor
In response to conmic

‎01-24-2018 05:27 PM

Hello



I have tha same question how do you relate the old to the new .... if we reused a server with the same serial number and renamed it how can I just relate it instead of showing duplicate


0 Helpfuls

Phil32
Tera Expert

‎06-27-2017 09:01 AM

I had someone suggest creating a CI for the server, then creating CIs for each existence of the server.


So you would have 3 CIs in your example


  1. For the server hardware
  2. For the Exchange installation
  3. For the MID server installation


I thought this idea sounds great, but not sure how to work it in practice yet.


0 Helpfuls