ECC is not an intrinsically bad thing. In large environments it is a requirement.
Even with ECC, look how human error has caused issues with Microsoft's online services, Google's online services, etc. It could be far worse. However, there is no reason for it to take as long as has been reported in this thread for a typical change. In my large environments, ECC items are classified as to potential impact and have OLAs (Operational Level Agreements) that define how quickly they must be resolved or escalated based on the potential and OLA. This is all part of Operational Maturity (ITIL). And if a company is having issues with this, I will be happy to work with them and assist in the correction of their challenges, all in accordance with ITIL and industry best practices. -----Original Message----- From: Kurt Buff [mailto:[email protected]] Sent: Wednesday, February 20, 2013 6:41 PM To: NT System Admin Issues Subject: Re: Slightly OT: RE: Migrate DHCP from 2003 to 2008 R2 On Wed, Feb 20, 2013 at 3:13 PM, Webster <[email protected]> wrote: > And I think the Windows team is now making the network infrastructure > team go through change control every time they need something done in > DHCP or DNS (payback is hell you know). Now that's funny, but I hope for everyone's sake that that silliness stops soon. Kurt ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
