|
The Art of
Troubleshooting, when on a budget
Douglas Chick

The art of troubleshooting has nothing to do with
rebooting the computer when there is a problem. Although, it does come in
handy when you’re in a pinch and don’t have the time to find the real
problem. In fact, I believe that I’ve said the word reboot more than any
single solitary word that I’ve ever said in my life. With coming in
second, third and fourth--idiot, dump-ass and “Look, you’ve licked off
all the letters on your keyboard again!”
Rebooting does solve a multitude
of problems, such as, memory leaks, (programs that do not unload themselves
from memory once the program is exited.) Programs that try to share the same
CPU or Memory register and lock up the system. And Client software having
issues with the database, connectivity, threading, file locking and so on. I
could continue this forever.
To effectively troubleshoot you must first isolate the
problem. If people are involved I ask what was the last action taken before
the computer stubbornly stopped cooperating. What the end-user hears is;
what did you do wrong now, you idiot! Hmm, maybe it’s the other way
around, I forget. So upon doing so, they immediately deny doing any and
everything and become a useless tool to aid you. All you can do now is ask
what is the computer suppose to do and when did it stop doing that. And of
course immediately demand to seat in their chair. That’s the part I like
the best.
At this point you might be saying to yourself; wait a
minute; you’re talking about what helpdesk people have to do? Network
Administrators only work on servers. In a perfect world, yes, but you can
have an army of helpdesk personnel and still somewhere along the line
you’re going to make the mistake of helping someone, and then they’ll
tell someone else, and the next thing you know you’re working on their
home computer…. I’m sorry; I had to pause for a moment and shiver.
I don’t like to admit it but, with some
problems, especially with Windows, it’s faster to re-image the hard drive
than troubleshoot the problem. I mean, if you’re department in
understaffed as my is, you don’t have a lot of time to spend searching the
archives of a software company that shipped out yet another program that is
up to you to debug. If however, you do have a lot of time to spend,
investigating the whys and what happened, than please forward it on to us,
because quite frankly we could use the break.
DougChick@TheNetworkAdministrator.com
|
|