Page 1 of 1
Tips for CI Control?
Posted: Sun May 29, 2011 5:32 pm
We already have the tools (System with Auto Discovery tool as well), naming convention, etc. Im currently in the need to create CI Control / Status processes and would love some tips from the pros. Anything will do, just enough to get ideas on how its usually handled.
Im worried about maintaining CI Status (in use by, stored, disposed etc) up to date with the way the CIs are being handled right now. Autodiscovery tool helps with everything except the CI status and the Asset Tag (label) which have to be entered manually. Basically, all workstations are received, deployed, handled, repaired and released to users by Service Desk. So I depend a lot on their work.
Re: Tips for CI Control?
Posted: Mon May 30, 2011 4:18 am
kevo wrote:Autodiscovery tool helps with everything except the CI status and the Asset Tag (label) which have to be entered manually.
Just for clarity, kevo, what is the scope of "everything" in your statement. For example, I doubt if auto-discovery helps much with relationships in the CMDB, but perhaps that is outside the scope of your question.
Posted: Mon May 30, 2011 8:05 am
I meant CI attributes. Software installed, Last logged in user, Hostname, Serial Number, RAM, HDD Space. Things like that.
Theres not many relationships configured in our CMDB as of yet, on a Workstation CI theres the relationships with software (some) and the relationship with the user assigned /owner. The latter being one of my worries.
Sorry If I didnt explain myself correctly.
Posted: Tue May 31, 2011 4:08 am
An Autodiscovery tool is not Configuration management
It merely provides information that has to be verified to determine whether what was discovered actually should be there
What has to happen is Human involvement in verifying the details that was identified in the AD tool.
As well as entering all the information that the AD tool can not do
Posted: Tue May 31, 2011 11:19 am
Yeah, Its proven useful to some extent but like you said there has to be human involvement for the attributes the ADTool doesnt catch.
Ill have to work on a process for SD to help me with that. Im thinking since theyre the ones who have direct contact with most of the assets (mainly workstations) they should check that the CI information is accurate on our CMDB. In other words, every time they have to handle (repair, redeploy etc) a workstation, for example, they'd have to check the accuracy of the information on our CMDB for that specific CI.
Thanks and please excuse my English, its not my first language.
Posted: Tue Jun 21, 2011 5:42 am
you are in error. The process is the configuration management process. period. end of story.
You need to have a proces - config - that adds, removes, updates and verifies the CIs that are in the CMDB
The CIs need to be added when they are installed
Classified throughout their lifecycle and
archived from the CMDB (do not like remove)
regardless whether they are phsyical or virtual
You need to define states for the CI