Thanks Rick, it definitely helps. Eventually when we upgrade to 7.6.03, I'll go to management and ask if DNS changes is something we would want to track. There is no audit tracking for DNS modifications.. I know some management do believe there is a risk with changing/adding dns entries because if they 'fat fingered' an address it could potentially brake another app. Also, in the past we've tracked them as a means to identify people who would bring up new apps (web apps) without invoking Change Mgmt process. I will also eventually ask BMC for some use cases of 7.6.03 to make sure we deploy it in a consistent way.
Thanks, Marcelo From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Rick Phillips Sent: Monday, October 11, 2010 9:58 PM To: [email protected] Subject: Re: DNS changes ** Marcelo, You may want to check out the 7.6.03 .pdf, 160651_CDMClassedMapping (I got is with my 7.6.03 download). In it DNS servers are categorized (prodcats) as: Software>Software application/system>Software Server.p Not sure that this will help you, but it may be something of value to you in the future. rp -------Original Message------- From: Martinez, Marcelo A To: [email protected] Subject: Re: DNS changes Sent: Oct 11 '10 14:34 ** Thanks Rick! We are managing DNS changes, but not classifying them correctly. I wasn't sure if others were tracking these. You're correct, since they are not objects it is difficult to add them as CIs. We are not on 7.6 yet, just wanted to see how others are doing with Release thus far.. I remember lightly covering it in ITSM 7.5 training. From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Rick Cook Sent: Monday, October 11, 2010 4:04 PM To: [email protected] Subject: Re: DNS changes ** Well, you are obviously managing DNS changes, so that means that there needs to be some way of classifying them. However, they aren't technically objects, so that makes them difficult to manage as CIs, unless you want to manage them as server attributes or something. So it would seem that having some categorization around them for the CM module would probably do the trick. As far as Release goes, it has it's place, but I think if you can make it work with Changes and Tasks without having to twist or compress the process, you're probably fine without Release. If you find that you have large projects that need to be managed and scheduled at multiple sites or on multiple timelines, having a Release encompassing several RFCs, which can still have Tasks subordinate to them, is probably the way to go. Rick On Mon, Oct 11, 2010 at 1:55 PM, Martinez, Marcelo A <[email protected]<mailto:[email protected]>> wrote: How does your company categorize DNS changes in Change Mgmt? Do you have it under Ops Cat Tiers or set up as a product? Does your company have a criticality level for these? Do you differentiate between 'creating' vs. 'modifying' them? I'm just trying to see how others classify these.. seems as if lately we've had an influx of DNS changes (new or mods) and my current classification isn't in line with what the change is requesting. ARS 7.1 ITSM 7.0.03 ----------------------------- On another note, to the people already using ITSM 7.5 / 7.6 ... Do you use Release Mgmt or can you get by with just Chg Mgmt? Thanks all - Marcelo _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org<http://www.arslist.org> attend wwrug10 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are" _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
