Change a CI name

cochrantim · ‎04-21-2014

I have CI's in the system that have been redeployed with new names.

What is the best practice for changing the name since it seems to be a key datapoint?

Tim

prdelong · ‎04-22-2014

Name is a key data point, but for most types of CIs I would recommend just renaming the CI. Hardware CIs will likely have at least a serial number, if not that and an asset tag. Deleting the record isn't a great idea since it removes all the references to historical incident/problem/change data. Retiring the CI isn't a great option either, since any type of automated discovery or data import would likely still update the CI (though there are ways around it).

How exactly is this data getting populated in the first place?

View solution in original post

cochrantim · ‎04-28-2014

Thanks again.

Our former implementer from Triad suggested that we document the change through the CM process as well.

jesusemelendezm · ‎04-23-2014

If you are using discovery. The name will be updated with the naming information It encounters through SNMP, WMI or SSH. I tested it this afternoon. With a new printer we added. I needed to log into the printer and re-name it there then re-scan the same IP and obtained the new record name.

cochrantim · ‎04-28-2014

Thank you for the response. Good to know.

jdavid · ‎04-24-2014

If you are not using discovery, a time-saving but slightly messy method would be to use a transform map on a spreadsheet from excel. 2 columns-old name and new name. You can set the parameters to ignore matched names.

cochrantim · ‎04-28-2014

Thanks. Good to know.