Yes, yes, agreed - those are great rules to live by but it still does not change the fact that MT may have just introduced one of the biggest bugs in their history. The fault here lies (mainly) with MT - IMO.
Not following proper upgrade protocol doesn't change the fact that MT widely distributed a horrendously faulty and completely broken update. We updated like we always do and this box is completely hosed now. This absolutely should have been tested by MT - PERIOD. I believe this does give us some right to vent.
BTW, this was a replacement box (not live - but supposed to go live tomorrow morning - thank god it wasn't). So, I wasn't applying in a production environment (this time). This will just delay our deployment deadline by a few days, cost us valuable time and further agitate the customer(s). I guess it could always be worse though.
This has me very hesitant to apply an upgrade to a pre-configured MT box ever again, which makes me very sad. I feel like we are now approaching the M$ update model. I have been known, once in a while, to upgrade a live production box in a pinch - never again! BTW2, not everyone has the time or money for a lab environment (e.g. people that buy extremely inexpensive routing software like MT). Luckily, we usually do. I guess we're just so spoiled because all of the previous upgrades have gone so flawlessly.
I sincerely wish the best of luck to all affected by this. Good Luck!