Well it’s a new week and I’m sure everyone that read last week’s blog is as been waiting with baited breath to see what happened when the IT tech showed up to fix the computers in our office. OK, so that’s probably an exaggeration but I hope your back to find out what happened anyway.
For those that have just joined us here, last week I wrote about our fabulous IT department. To get a real feel for the whole thing, you’ll have to read last week’s post. Either way here’s part two of the computer technician fiasco.
It had been nearly three days since I called the charismatic fellow at the IT desk to tell him my computer wasn’t working. He’d mentioned there might be a slight back log for repairs, since they had disabled several hundred computers; so frankly, I was shocked when a technician called to tell me he was on his way over. He asked if I could be there to meet him, and I told him I could if I rearranged a few appointments.
As soon as I hung up the phone, I went to work changing my schedule to free up the afternoon. Lunch time came and went. As did one, two, three, and four O’ clock and guess what; no IT guy. The next morning I got another phone call from the computer office again saying they were on their way. This time they asked for directions (Perhaps they got lost the first time). I told them I was at the fire department.
My answer was met with silence and the sound of rustling paper then the man said.
Now this might seem like a perfectly logical question, except it just so happens we are the only fire department they serve… oh and we’re less than a block away.
“Walk out your front doors, turn left, then look for the building with the great big fire trucks!”
OK… I didn’t really say that. What I did was give him the address and hope he wouldn’t have to put it into a GPS to find the place.
Moments later he arrived, looking frazzled, and introduced himself as the department supervisor. At first I thought I was in luck. If anyone could help me here it would be this guy right; wrong. As I watched him work, I realized why our IT department had always provided us with such abhorrent service.
He sat down, hit the power button, and waited for the computer to power up. When the screen came on, displaying the code telling him the computer had been disabled, he looked at me with a straight face and said.
“Yup your computers down. I’ll have to go back to the office and get a disk so I can fix it.”
Then he got up, walked to his car, and left.
Now this should have been shock, but considering or history together, it didn’t surprise me at all. As he left I wondered what he would say if he called 911, and when we got there we said,
“Yup, that’s a fire. You’ll have to hold on while we go back to the station to get some hose.”
The IT pro got his disk and was back in a flash. He came in, sat down, put the disk in and… made a phone call. As he waited for the other line to pick up, he clicked the mouse nervously. I knew something was wrong.
The other party picked up.
“OK, I have this disk in. Now what do I do?”
I could not help but stare in disbelief. This was the head IT guy and he was calling back the office for step by step instructions. He would listen; type a few lines, then listen again, then type some more. After several agonizing minutes he got the process started, then stood triumphantly to announce it would be an hour before it was finished.
I sighed and agreed not to touch it. (God forbid I would cause another problem) and waited for it to go through its paces.
As soon as it was done the IT guy came back, apparently he did have that timed pretty well, and he sat down to log in. He typed his admin password and hit enter and… nothing. He did it again and again; still nothing. After a few more tries he called his office.
“Ummm, yeah,” He mumbled into the phone. “I think I forgot my password”.
I pretended not to listen, looking out the window so he wouldn’t see me laugh.
“No, I don’t remember... OK”
A few moments of silence went by, and I realized he was on hold, in the perpetual Barry Manilow limbo. I guess even the tech guys get this treatment.
A few more moments went by and he hung up the phone.
“I need to get some additional software from the office,” He said, as if I hadn’t heard the whole conversation. ”I’ll be right back”
Again he went, and again he came back. He put his new disk in the computer and; you guessed it, he called back for instructions.
On the up side, once he limped through the log on, it didn’t take long before he was in. I know this because as soon as he was successful, he whistled some obscure superhero tune. In fact, he was so happy, he did the same thing every time something went right.
Click, click, click… program loaded correctly, superhero tune. Click, click, click, password accepted, superhero tune. It was hilarious.
Another 20 minutes of his heroic efforts, and my computer was running again. When he was done, he stood, leaving as swiftly as he’d come, ready to do more good deeds. Unfortunately, I had to chance him down in the parking lot to give him back the password crack disk he left in my computer. Oh well, nobody’s perfect. What’s a little security breach between friends anyway?
So that’s my story. A little long winded but I hope you got a kick out of it. Until next time, happy reading.