This is a fundamental law that needs to be learned amongst Geeks these days. The need to fiddle and twiddle seems to be pretty well ingrained, and yet it rarely leads to immediate success, but instead hours of trying to work out how to make it do whatever it did before, again.
I have always been of this belief, something instilled in my by my Mechanical Engineer father - but this ideal became a mantra while working at an ISP:

The System Admin spent most of his time doing Adminy things, and then whatever time was left he would be bored, and to alleviate said boredom, fiddle with things.
Upgrade this software package, tweak this configuration, install this monitoring software, so on, so forth.
And, invariably, something would go wrong, and for two days the rest of the ISP would be complaining that X doesn't work like it did - or at all.

When this System Administrator left the ISP (after finding a much higher paying job), I took over the role of Administration, and being also the only programmer who was spending most of his time previously on an eCommerce platform, I made things work in the System - and then went back to programming.
Lo and behold! Things just kept on working, and working, and working - thusly the moral of the story is simply:
If it ain't broke, don't fix it.
Because if you don't let it alone, you're in for more trouble than its probably worth.

JP,
-- Alexander Widdlemouse undid his bellybutton and his bum dropped off --