Bladewatch.com

I got a call from a rather emotional Chris (he’s still enjoying the view in his very nice office down in Canary Wharf at an organization that shall remain nameless).  Anyway, they bought a new server (1 of 11 actually). A nice new impressive 2u ultra fast, ultra efficient (using the new Intel processor) server with 16GB of RAM, enough local storage for their new web application.

There was however an issue.  The server got unboxed, it got configured to the organization specifications (a dvd drive fitted), an asset tag added, a nice sticky label to identify asset SRV00109821 as SW0001923. To avoid arguments and debate, I’ve removed any reference to the vendor and the hardware involved, I suspect we’re all guilty of following process, let’s move on to the story.

The hardware guy successfully racked the server, he plugged in the power cables and no green lights came on (the ones to suggest there was power, that the server was operational). So he did the first line things, he removed and re-seated the power supplies, he checked the power cables were ok, he unplugged the power for five minutes, he looked at the front and decided that the server was broken. It was unracked taken back to their lab, where he was unable to get the server to switch on at all.

Chris emailed me to illustrate his pain within the organization and when dealing with the vendor. It follows in the next post, and illustrates wonderfully not only service delivery but also vendor/customer relationships.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.