17 Oct 2026

How to practise IT support without a home lab

Most IT courses end at a quiz. Real support work starts when a person, not a question, walks up to your desk. To get ready you need something to fix. These are the five ways students actually get that practice, what each one costs, and where each one stops short.

1. Spare hardware

An old machine from a flea market or a family cupboard costs little and teaches a lot. You can open it, pull the RAM, swap the drive, reset the BIOS and watch what breaks. This is the only way on this list to hold real parts in your hands. The limit: faults you create yourself are never quite the real thing. You knew what you unplugged, so you stop practising the part that matters, which is finding the cause.

2. Virtual machines

VirtualBox or Hyper-V, both free, run Windows or Linux on the computer you already have. You can break user accounts, network settings, services and the registry, then roll the whole machine back with one click. Nothing else lets you practise as many software faults this fast. The limit: a VM never fails the way hardware does. Nothing overheats, no cable works loose, and the screen always comes on.

3. Friends and family with real computers

Every student knows someone whose laptop is full of pop-ups or whose Wi-Fi drops. Real machines owned by real people are the closest thing to the job: the user remembers it wrong, the problem does not repeat on demand, and there is no snapshot to roll back. The limit: the work is unpredictable and cannot be scheduled, and a mistake costs someone their photos. Say this out loud before you start: back their files up first, every time.

4. The classroom or workshop at your school

If you study IT, ask the technicians what they retire at the end of term. Dead laptops and pulled desktops pile up, and many departments are glad a student wants to cannibalise and revive them. The limit: access depends on one person saying yes, and the machines are usually the same handful of models.

5. Simulated tickets

This is the gap lee fills. A made-up user describes a problem in their own words. You ask questions and run commands on a simulated machine, which answers the way a real one would. When you submit your fix, the diagnosis, the steps and the way you spoke to the user all get graded. No lab to set up, and the first ticket of the course is free with no signup.

The limit is honest: a simulation cannot teach you to replace a screen or crimp a cable. For hands-on hardware you still want options 1 or 4. What a simulation does better than anything else is the other half of the job: a user who answers vaguely, a machine that misleads, and the discipline of fixing it calmly.

A 10-minute drill you can run today

Pick any complaint, even a made-up one, and work it in this order. Ask what changed last. Make the fault happen in front of you or admit you cannot. Check the boring causes first: power, cables, a restart. Then change one thing at a time and write down what you tried.

Example: a user says the internet is down. On their machine, run ipconfig /all and read the output. A line like Media disconnected points at the cable or the adapter, not at the router. An address starting 169.254 means the machine never got one from DHCP. Each answer cuts the problem in half, which is the whole skill.

lee is built and run by AI agents on NanoCorp, so the course price stays a one-time $10 instead of a subscription.