Joined: Mar 31, 2008 Posts: 109 Location: North West England
Posted: Tue Nov 10, 2009 10:32 pm Post subject:
If a CI needs a name change, then I would personally just rename it (after being approved via change management). I don't care what it used to be called but if I need to find it again, I can just search on the unique reference number which should never change. This conforms with my ITIL based process definition - which is 83% ITIL compliant
However, if you want to find CIs based on past and present names and your tool doesn't allow this then, either your tool needs replacing (to match your requirements) or your process needs updating to match your tool.
I would personally suggest cloning the CI and marking the old one as renamed, with a link to the new one.
ITIL (and this forum) don't care about tools, just the process, so as long as your process is clear what you need to do, then that's fine by us.
Hope that helps. _________________ Mick Smith
Change, Configuration and Release Manager
Joined: Mar 04, 2008 Posts: 1884 Location: Newcastle-under-Lyme
Posted: Wed Nov 11, 2009 3:05 am Post subject:
...which is 83% ITIL compliant
Mick, you can gain a few more points, by appropriately colour-coding your documents red and blue for v2.
For all versions, there is a way to achieve over 97%, but it is a complex algorithm concerning the occurrence throughout your documents of phrases matching those in the manuals. If you work hard enough at this you can be very compliant simultaneously with all three versions (if you've got the original books) _________________ "Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
Thank you all.
Yes the server name itself is being renamed as the device has moved to a different location.
We have an auditing tool in our CMDB that shows previous names/attributes which is fine but obviously searching on the device will only find it with its current/new name and not the old one.
Does this seem ok?
If not I guess cloning the devices is an option because you could find the device via old name and/or new name
Joined: Sep 16, 2006 Posts: 3232 Location: London, UK
Posted: Tue Nov 24, 2009 3:26 am Post subject:
So the server is being re-purposed, rehome and re-named
THis would be the following
change request (multiple parts/section)
configuration mgmt db change
what about SLA, OLA, acceptance of system, documentation yadda yadda yadda
While the physicial attribute of the server will be the same - serial number, etc, the fungible data like the company datacenter inventory tag may have to change
So what I would do in this is as follow
transfer the server from one site to another
then add all the new fungible data and delete the old data (archive) I hate deleting data _________________ John Hardesty
ITSM Manager's Certificate (Red Badge)
Change Management is POWER & CONTROL. /....evil laughter
Thanks. Yes we have updated all the attributes relevant to the new location for the device. The CMDB is up to date and there is a history of what was changed. We just cannot search on the old device name any more unless we clone it. Not sure if that is an issue in x months down the line or not
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum