Re: Patching and Firmware versions general question

Alan,

Most days the worst support call I get is along the lines of 'I spilt coke
on my keyboard'.

;)

"Alan" <Alan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6D2126E3-D8C0-4515-BFEE-DBB82F3EAD51@xxxxxxxxxxxxxxxx
Thanks for the post Sean. I like to have a devils advocate to induce
thought
for all. I think in your scenario you have diverged into the surreal just
a
bit though. I think that we all would consider ourselves very lucky to
work
in the utopian evironment you have described.

All in all I guess I just made a new project for myself! I love being the
new guy!

Alan

"Sean" wrote:

"Thee Chicago Wolf" <.@.> wrote in message Admins
who take the "if it's not broken don't fix it" approach always set
themselves up for greater failures later.

- Thee Chicago Wolf

I don't agree, in a well managed environment you wouldn't introduce an
element that would alter the balance of your systems. If you have good
change management procedures and plan changes well in advance you can
keep
all of your systems at a common level and only patch if the patch is to
fix
an issue you are experiencing or to bring systems in line with the
prerequisites of a new element you are introducing under a managed
process.

Reactive management never works in my experience because the knock-on
issues
it can cause are often worse than the problems you were trying to fix in
the
first place (if indeed you were trying to fix a problem) creating a
greater
drain on resource.

Just me tuppenceworth.

Sean






.