Training a newbie tech.... What do you teach first?

I've never trained someone from scratch, I've always had people with some exposure.

I would start with installing the OS. Build a PC for them, and have them first install the OS through the defaults, then do it again with the custom - have them play with some of the custom installs.

Once they can install the OS without too many thoughts, have them build the basic PC - put the MB in the case, install the base components, then boot it up, format, install the OS.

Then have them add the often additional components - video card, sound card, ethernet card etc. Install the HW, then configure it in the OS, one by one.

Once they have the basic box stuff, then you can move to networking.

James

Thomsen Course Technology has several resources (http://tinyurl.com/y3gw66), but they are rather pricey.

The best other source is probably the current edition of Scott Mueller's [i]Upgrading and Repairing PCs[/i]. If you also can get a copy of the Tenth Anniversary Edition, you will pretty much have all the information you need from PC Day One. Start him reading.

what will be the primary skill needed, hardware, OS, software?

A basic understanding of all is needed, but then focus on the ONE that is the most important.

Too many times I see people that know a little about everything, but not a lot of any one thing. They can get by in the day to day, but when there is a real problem, they don't have the abiltiy to resolve it.

Also stress to be methodical. Always make one change at a time until the problem is solved or you will have no idea which change fixed your problem.

Relaxing is important too. It drives my co-workers nuts becaues they will be all frantic over something for a while trying to get something going. I go back to my office, turn on the tunes, grab my coffee and "just sit there" or "browse the web". What they don't relize is I am doing that "thinking" thing, or I am looking on the web for people that have had the same type of problem. It usually doesn't take me long to get the answer.

When you rush, you make mistakes. Dumb mistakes.

The condensed version is best- it will present the information in logical order and help to reinforce it while not actively in the lab environment.

There are a number of good A+ manuals out there- I like the "Passport" series for well condensed information.

Another important thing to keep in mind are the old tricks that the new kids don't seem to understand- like the sensibility of keeping a paperclip handy...

pound it into their head that you do NOT need to change bios settings every time.

I recently had someone change a cdr for a dvdrw on a system, which failed completely.
they had changed the bios settings and created an irq conflict.

which really means:
do as little as possible to get the system running, tune it later if needed.

A lot of people think they have to adjust pins and bios settings for every hardware change, or even os change. the default bios with plug 'n pray options enabled can, now, usually get it right, so "if it ain't broke don't fix it" needs to be retaught to a lot of people.

Troubleshooting a PC starts with the basics. He will need to read and study a good A+ training book. That will teach all the basics of computer components. As for repair the usual components that are the problem are: Hard Drive (bad sectors), Memory (Memtest 86 is good to check), Power Supply (always have a reliable replacement to test with). I have a POST card. This is essential for trying to diagnose a defective motherboard or CPU or Power Supply.
As to building a computer set a procedure. What parts get put into the case first and in a certain order. Be methodical, and don't let him deviate from the procedure. That way he can build systems consistantly and speed will come with repetition.
Usually we build CPU and Memory on motherboard and run it on the bench or desktop before installing it into the case. Don't assume it will work. It may not. We have had defective motherboards right out of the box! Also defective CPU's and memory that were brand new. Once the board runs on the table then it can be placed into the case using the standoffs. Then comes the hard drives, cd or dvd drives. then cards and cables and power added last. It should all work if the board ran on the table to begin with.
During OS install sometimes defective parts show up like Video or CD/DVD drives (the setup reports unable to copy/find/certain files). Also defective media (CD's or DVD's) sometimes show up, but not too often. Hard drives usually show to be defective during this time also. If the OS installs properly and all drivers and devices work, let it run about 24 hours and see if still works (no lock ups or resets) before putting it into everyday use.
I have been in the PC repair/construction business for about 18 years. I have A+ and Network+ certifications. The main requirement of an IT job is to LOVE WHAT YOU DO!

osi first, tcp/ip second and not silly stuff like how to build a pc. no-one builds pcs anymore. we buy them in, and throw them away at the end of their life-cycle.

most importantly, teach non-invasive attitudes and techniques. no point fiddling about at the top layer (application) if the cables dropped out (physical.

Or just an individual personal issue, but some people just can't seem to get the idea:

Just because you [u]can[/u] do it doesn't mean you [u]should[/u] do it.

I would start with objects, and the communication that links them. Like you already did...
Motherboard goes here and is connected to the power supply. There are a few different PSU connector types...
CPU goes here and is connected to the motherboard via the socket.
Hard drives and CD/DVD drive goes here and is connected to the motherboard with these types of cables.
Video Card...blah blah blah...

Once they get the object and connection basics, and can get a basic system to turn on and only beep once at post have them disassemble it and rebuild it five more times. Be sure to use old stuff you don't need as breakage amongst newbs is quite common until they get a feel for it. Hence the repetition.

Above all, let them know to ask questions frequently if they're in doubt of what to do next. As with most technicians, communication is an essential skill to learn. Not just listening, but talking too, and communicating an their thinking correctly and coherently.

After the hardware assembly basics are finished, a light dose of introduction to BIOS is in order, followed by determining what to setin the bios to boot the installation media.

I am a very techincally savvy person, and I must say that the most common theme I remember from my childhood is the continual breaking of things while taking them apart to figure out how they work.

Its very important for the fledgling tech to break some things to get a good idea of the limitations of the parts, and how to correctly handle them.

In my work, I have found the best techs and support people to be those adventurous types that aren't afraid to break the rules, but know when to use common sense. Its a very rare combo that is in short supply these days.

Teach your studnet to use complete sentences,
paragraphs, and thought patterns so that he may avoid
miscommunication. Communication is essential in any
field, especially Information Technology. I agree, a
grounding strap and a knowledge of DOS are essential. Also,
an understanding of addressing and base 2 is helpful.

Tell them to get a "PC for Dummies" book. If they like it and can handle the detail then go more advanced. Micheal Meyers maybe.......

I just believe to keep it very simple, to get a base for their interest and go from there.

ELECTROSTATIC DISCHARGE
He MUST understand that he can destroy electronic componenents "silently" by touching them without having proper precautions in place. You don't have to throw a spark to ruin a MB or card.

1) Hardware training: Tell them to be humble,
2) Software training: Branch unconditional statement to instruction #1: tell them to be humble.

I state this because after training newbies at electronics maintenance down to the component level and then later at my present career, training newbies as a desktop \ server site support specialist many come in with inflated views and objectives, money wise and knowlege wise. Its not just about imparting the knowledge but getting them to see the whole process, the big picture, the actual knowledge to complete the task, properly "seeing" the user base i.e. you user base is not supposed to have your skill set, just what they need to do THEIR job. etc.Getting them to do a thorough job etc.
Write down all the important tasks to complete your most critical tasks. then break them down.
Its a complicated issue and I suggest that you visit the library and look at HOW TO Teach/Train technical material subject matter. There is lots of good material out there. I come from a technical\maintenance and training background and your task is not as easy as it may seem BUT properly done once and you have proper training documentation specific to your needs it will save you time and effort in the future with future tainees and it will make you look sharp. I'm in that process right now for my new shop it works.
email me if needed

1)Have the trainee create a set of DOS Boot Disks that will boot to a network share. The boot disks should work on any of your PCs

2)Have him do the same with Linux boot disks.

3)Have him install a custom Linux OS. He should be able to re-compile the kernal with a custom set of device drivers.

4)Have him do the same with Windows using Sysprep.

Once he/she can do that, he is ready to do basic desktop support. Unless he is supporting Servers, he should be able to do basic hardware support (NICs, HDD, Vid cards). Send him to vendor training if he is to do server hardware support; or better yet, just get a support contract for vendor HW. Once the trainee is comfortable doing desktop support, send him to get trained on whatever network OS you have running in your shop.

First rule is safety.
Second rule is keep the boss informed.
Third rule is keep the user informed.
Fourth rule is When in Doubt, Don't.
Fifth rule is try the obvious first. (Check to see if it's plugged in)

After that you guys have it pretty well handled. I would echo the people who said to take notes, but go futher and make them build detailed run sheets or check lists for for everything they do. Bring the check lists back to you and you approve or modify them. The little gotchas will show up then. If you need to change a procedure because you now replace a specific part or change the way you do something because of a case mod change, you can without rebuilding the whole check list.

Young minds are a terrible thing to waste, but they are also a trial to train. More power to anyone who undertakes that task.

For the trainer my advise is to take long breaks away from your trainee to recharge your attitude and regenerate your own ability to patiently give instruction. Remember you were once a newby too. They will also appreciate not having you breathing down their necks for a short period of time as well. Its how they grow. But don't over do it, they need to know there are limits also.

One of the key parts of understanding a computer is what they are doing when you use one. Understanding the things that take place when it boots, when it makes any beeps, and what signs to look for as it boots up to the final screen will give them a guideline so they know what to expect.

Its vital they know the proper sequences and what the results are to be able to determine when something isnt working properly. What should happen when you push the power button? What visible/audible indicators do you have to know everything is connected and working? Start with a working computer to give them a frame of reference. I would show him/her the major components, what is needed for them to "talk" to the system, staying as simple as possible. After this I would introduce built-in troubleshooting tools for simple problems. The light on your monitor, the beep sound during boot up, the sound of the hard drive spinning up,things like that. Dont over look the simplest things like the power supply setting or a pin bent on the VGA cable, keyboard or mouse cable. Most existing computers are not using USB keyboards and mice yet, so this is important.

Lastly I would walk through some logical procedure to help them troubleshoot some of the most common problems. I find it useful for the new tech to have solved some of the simpler problems in our lab giving them a sense of confidence before sending them out to work in the field.

1. The Humans are smarter than the machines.

2. Make sure he has a good grasp of the nomenclature (part names)that make a machine go.

3. There are five elements that make a computer (pc, desktop,laptop,)the rest of the parts are peripherals. (monitor, keyboard, mouse, etc).

The peripherals; are what the Humans use to comunicate with, and monitor the machines input or request, or store and retreive input and data.

4. The basic elements are power(supply), Motherboard, memmory, video card, and of course the processor.

Once he can grasp the basic and advanced functions of the basic five elements, as they interact in the POST, how they come together as a unit (PC); then it is time to
Teach the steps of identifying and troubleshooting the basic five. It depends on how far you want to go with the MB, different types of connectors and agp, versus/ and or pci and of course bus structures.

5. Once that happens, now you can teach memmory, the different types and how they interact.

6. ROM, Ram, cache, video, upper,(umb)640k, 384, and beyond 1024k, protected, reserved,etc. this is a good time to touch binary math, and large numbers. Spend time with this one; couple this information with... this is the building block of how the machines "think".

He will have a better appreciation for this when you add a harddrive and start to teach storage devices, the different types of storage and what role they play in the boot process. The sectors cylenders, rpm's, FAT table(s), boot sector, etc.

7. That mystical term we call bootstap, that hyper leap from POST, to the machine showing the OS Logo, text or what ever the Humans need to acknowledge that IT's; yeah IT is ready for Input.

This is only the very basics of what you must know about machines to be a technician. There is a great deal of infmation I did not touch on or include,....I appologize.
Some things I don't think about anymore, they are quite literaly second nature to the way I troubleshoot "think about" machines.

Greg

Did not have time to go thru all posts, so don't know if already said. In addition to existing posts I did read...

Any problem, for 99% of problems, someone has already had and the answer is posted somewhere. Learn some solid research skills so that you can find a needle in a haystack on the general Internet and within any specific site if need be when looking for an answer. Comes in great when you need to learn by fire, and/or are on your own without help, or know more than anyone else with you and what you know can fit on the head of a pin. Or even when you do know quite a bit, too.

I say this as a previous business researcher (non-IT) who uses those skills every day in my IT job.

I don't mean that literally, well not necessarily... lol

There are a lot of good suggestions in the previous posts, between them you should be able to assemble a plan.

What I mean is, when building a PC, once you have shown him how to do something, introduce faults. Use known faulty hardware, if you have any, a bad RAM chip, faulty keyboard, or whatever. If you are any good with a soldering iron, unsolder a few wires/connections, this will be easy as you can always fix it afterwards, since you know what the fault is. If you don't have any faulty hardware, try something non destructive, such as (re)moving a jumper or loosening a connector.

On the software side, try altering settings in the BIOS. Change some OS settings.
If you feel brave, introduce a bit of malware, but only after you have shown him the tools to deal with it. Keep off any network while doing this though, that includes the Internet.

I remember in another post that you were considering a possible Linux distro, so try him with the idea of using a Linux LiveCD to troubleshoot a system.
For an advanced lesson, get him to know how to use the utilities of a system rescue disk, such as Ultimate Boot CD.

Lastly, in all of the software lessons (hardware too) drum into him the necessity of saving vital data, making back ups, and document, document, document.

He'll thank you for it later, any notes he takes will prove invaluable in the future.

I got my start in PC's with a game called Cranston Manor, on an Apple IIe donated to our school. Spent hours trying to find the funny commands unusual commands would give. (ie "Pray -> Praying won't help you"....

I then recieved my first PC (Timex Sinclair ZX81 as a present for my birhtday the year following. I was too poor to buy any games, so I started writing my own. Over time, moved to a Commodore128, and built a speech processor for it ($20 in radio shack parts),along with writing a few games.

My point? Find a couple fun projects which meet some of your student's interests. Particularly projects where there is room to "hack". Those are a great way to help the individual develop an understanding of the fundamentals - an understanding not just of how, but also why.

- Teach him all the components of the computer. MB, Mem, HD, floppy (if any), USBs, etc...

- Have him study for the A+ exam. This covers the basics on computers HW and SW.

Not fault guessing, fault assuming or fault dunno lets change this.

First rule of fault finding change only one thing at a time. If it doesn't fix it put back how it was and try the next possibility.

Next rule 99.99% of the time if you are coming up with some really weird scenario based on the time of the day , the colour of the users socks and wind direction, you've missed something obvious.

Third rule, the fault is always in the last place you looked, which is usually the place where you assumed it couldn't be.

Google.

There is not a problem he will ever come up against that he can't find somewhere to start from with the G.

There must be some A++ certification guide or book you could use as a reference/outline to your teaching. Then give him a PC and get started.

I'm not a huge certification fan, but it would be a nice payoff for your apprentice.

I've been invited into shops and supervise most auto repairs unless I know they will take too long. Much of my programming is with managers/end user sitting next to me to provide instant feedback. If I think something will need some extensive code or I need to think/plan, I tell them to take a break. Usually they have something else to do.

My fees are based on the value of my solution to the customer and not how much time I take.

Get the kid close to customers; they'll be paying his salary.

This reply probably goes a bit wider than your question, but is relevant to many initial training tasks. It revolves around your last comment: "So I need help putting my knowledge in some sort of logical order."

This is often the problem with training - you know that lots of things are important, but you don't really know which to do first, or which is most important.

Knowledge Structure Mapping is a technique that lets you analyse the knowledge an organisation or person needs to accomplish a particular task, and understand how all the knowledge hangs together and what knowledge is an essential precursor of other knowledge.

This sort of approach is probably over the top for a single student, but it has proved very useful in clarifying the sort of issue you raise. You can read some more at www.akri.co.uk

Hope that helps.

Having been both the tech and the person who calls a more knowledgeable tech when I am in over my head, I will second how important personal / social / communication skills are.

I hate it when I get a tech that cannot ask intelligent questions when I haven't given him or her all the details needed to fix a problem or when the tech cannot explain to me how to avoid a recurrence. (Maybe that is job security?)

You know, I think it is a full time job and they call them teachers. But the best teachers that I have always had did the following
1) took alot of time for what seems like on task, so that they could explane ALL of the middle work.

EG. When you build the computer for the first few times, you need to stop him alot to explane the do's and the do nots to him. As well as spelling out the anatomy of the system (this I think includes the sub componets of the MoBo [North Bridge, South, Video, Sound, Caps, ZIF PGA SEC Pin counts and the world of the socket]) He/She needs some GOOD reading material that not only goes over the inerworking of the machine but the HISTORY TOO! That will tell him tons on the WHY? questions.
2) Hands on always works best in a 101 setting.
He/She holds the screw driver. You hold a beer.
3) I have never seen a teacher with out a well layed out game plan from the get go.
Sit down and do some doodling.. Helps it flow if you draw your own mental pictures out for yourself.
4) (And this is the hardest) PATIENCE!
You didnt understand binary the first time it was shown to you....C'mon dont lie now. You learned it 2 or 3 ways till you had it down pat and you did some self study of some sort.

Thats all I got realy. Good luck.
I do suggest that you spend the extra $3 an hour to save some of the hair on your head. Training a new guy could kill you.

Hey! Thanks for the info. I just moved back to Charlotte and I'm looking for work. Do you happen to know of anything that might fit my profile, gmboat1?
Thanks.