I would also say that people skills are very important.
My thoughts:
1. Always keep a note book and pen with you. It is important to write down what people's issues are or what they have asked you to do. If you don't write it down you will probably forget it, especially if it is an error message.
2. Ask the "right" questions first:
a. what exactly where you trying to do?
b. is this the first time that you are trying this particular thing
c. If this is not the first time, when was the last time it worked
d. do you know if anyone else is having the same problem
e. are you getting any other errors or problems with your computer
f. how important is getting this done, when is the deliverable due
g. is there another way we can do this in the meanwhile until we can get things fixed
h. did this problem ever happen before, if so when and how many times, if someone fixed it before did they tell you what they did
i. did you recently add anything to the machine
j. has anyone done anything to the machine recently
3. Break your troubleshooting into pieces, e.g. hardware; software; configuration; connections
4. Learn the best steps to resolve a particular problem. Do those things that have the highest probability of fixing a problem first; then the next thing. Once you learn the best way to fix things, use the same order. It keeps you from forgetting to do something simple that may help.
5. Minimize risk. Do not do anything (unless in an extreme emergency) that could really mess up someone machine, like editing the registry.
6. Identify how much time you can have on a person's machine before you take over. They may need to do other things.
Good Luck