CMDB / Staff

[broadway]

I won't mention the parties involved but basically one of our Exchange servers containing certain Public Folders was being re-sized hence an outage. Sadly our provider could not tell me who would be impacted!

Therefore should the CMDB contain users, mailbox location, public folder usage, etc? I hope you see where I'm getting to?

Regards
Broadway

[UKVIKING]

Ask your self this question

If you had that data, would the issue had still happened

I think it would

THe CMDB or any data base or any reference tool should not be used in place of the due diligence people should do

If I was running a project like that, I would look at EVERYTHING that could possibly be impacted by it as part of the risk assessment and classification of the risk potentials
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter

[broadway]

Can't argue with what you said John but I'm 3 weeks into a new job where part of our IT/Services are outsourced.

As the provider could not supply the info (another debate) it got me thinking about what level of staff / resources should or should not be included in the CMDB

Regards
Broadway

[Timo]

Question is not so much whether it should, but rather would you be able to keep that information up to date and relevant? And how much effort will you need vs the benefit that you will get from it.

[Mark-OLoughlin]

sounds like it is review time - from there identify where you see the gaps and from there identify what can realisticly be achieved.
_________________
Mark O'Loughlin
ITSM / ITIL Consultant

[cjmt]

As maintenance is one of the major issues to consider, it makes sense to only consider including the data that can be easily maintained up to date and for which the maintenance overhead brings visible added value.

[sseliquini]

I can see the value of knowing which users are impacted by an outage. Currently in our company, when an outage occurs (planned or unplanned) ther service desk sends an email to the entire community notifying them of the outage. This leads to people being spammed and then ignoring the email when it is applicable to them. Our solution was to include the users associated with a particular service such that when there is an outage, we can target the outage email notification to only those impacted by the outage.

So, in our case, we do keep the users of services in our integrated CMDB. The actual userids are stored in groups in LDAP (MS Active Directory) and the groups associated with the services are in the cmdb