Head in a blender

Shooting yourself in your own foot

Andy Pedisich  September 25 2009 10:56:52 AM
I'm pretty much a control freak when it comes to upgrading the design of the address book prior to an upgrade.  I don't just push the new design over the old template because it almost always brings over junk that I don't want to perpetuate.  Over the last week, I blinked twice and was bitten twice.

It happened at the usual meeting that I have with the admins where I ask the big question:
"What customized design elements should be brought over from the current address book to the Release 8.5 address book?"

Client 1's answer: "All of them!"
Client 2's answer: "None of them!"

I want to point out that both of these clients are informed, smart folks who have solid domains.  They are both conservative and careful and hate service interruptions.

At client 1, who kept all "customized" design elements, one of the design elements that was modified was the desktop policy settings document.  I renamed the 8.5 version in the template and popped the old one in.  As I did this I wondered what the admin had changed that might be important, but I threw it in, assuming it was a requirement.

As it turns out, IBM made a boatload of modifications to the desktop policy settings document in R8.5.  Keeping the customized R8.0.2 document was a mistake.  It was impossible to edit a policy document in that configuration.  No harm done to anyone, fortunately, as they only had desktop policies in pilot mode.  I had kept, but renamed, the 8.5 form, so it was easy to put humpty dumpty back together again.  Today I rolled out an Org level policy that included a desktop settings policy and all went well.

By the way, client 1 didn't really make any changes to the design of the policy document.  It was one of those situations where you open an element in designer and save it by accident.

At client 2, who kept none of the "customized" design elements, I did the redesign around 10 PM with the R 8.5 template.  At midnight, I got a call because iNotes web access was broken.  One of the customized views I dropped was critical to the way they pointed their users to their mail files.  We're in planning stages for rolling out IWAREDIR.NTF, but just not there yet.  We were back in business with the old view in a short time.  No real problems, no real service outage because everyone was diligent in testing after the redesign.

The lessons for me were clear.  I usually list out and review every customized design element in the address book and make everyone look at them one at a time, deciding blow by blow what is worth of keeping and what gets dumped.  This was the first time I had "all" or "nothing" answers to the big question,  and it was the first time I took that answer on face value and did not specifically review every element.  It's the last time I'll let that slide too.

I will continue to do do what I have done since the stone age, and that is to redesign the address book prior to upgrading the first server.  That's still proves to be the right way to go.

And now I will return to writing my slides for The View's Admin Boot Camp, which are grossly overdue.

- Andy

1LeiLei   9/29/2009 2:22:21 AM  Shooting yourself in your own foot

"Shooting yourself in your own foot" means "搬起石头砸自己的脚" ?

2Victor Toal  10/3/2009 5:25:41 PM  Shooting yourself in your own foot


Classic story - I totally understand and we all do that one (or something similar) some time.

I just recently totally screwed up a clustered install of new 8.5 server because I did not stop to check the correct assignment of IP addresses first. ALWAYS check THEN configure. I ended up having to re-do allot and even had to replace the public key of the serve document. And I am supposed to be the highly qualified resource that is paid to do the job right and quick .... man did I want to kick myself in the rear end then but I did not want to get any dumbass on my shoes .....