Nobody learns to drive from a slideshow about steering. Everyone in IT education agrees with the equivalent statement about tech support, and then a surprising amount of coursework is still reading followed by a quiz. Not because instructors want it that way, but because hands-on activities are expensive in the currency that matters: prep time.
So here is an honest tour of the hands-on formats I have seen work, ordered roughly by how much of your evening each one consumes.
Role-played support calls
Pair students up. One is the technician, one is a user with a problem you hand them on a card, and the technician has to get from “my email is broken” to an actual diagnosis by asking questions. The user card includes what is really wrong plus a personality note, because handling a frustrated person is half the job and no one practices it by accident.
This costs nothing and teaches the skill employers complain most about missing. Its weakness is that seventeen-year-olds role-playing at each other produces variable realism, and the student playing the user learns considerably less than the one playing the tech.
The sabotage lab
Take working machines, break them deliberately, and let students find out why. Unplug a drive cable, disable a network adapter, set a wrong DNS server, fill a disk. Students get the machine and a complaint, “it’s slow,” and have to work a real troubleshooting method instead of guessing.
This is the classic for a reason. It is also the format that eats prep time alive, because every machine has to be re-broken between classes, and one student with a phone camera can distribute your entire answer key by Tuesday. Virtual machines with snapshots soften the reset problem and are worth it if your hardware can run them; a home-lab style setup on a few spare boxes can carry a whole semester if you have the boxes and the patience.
The class helpdesk
Some programs run an internal helpdesk where students field real tickets from staff and other students. It is the most authentic option on this list and I admire every program that pulls it off. The tradeoffs are real, though: ticket flow is unpredictable, the interesting problems arrive during the wrong class period, and a student’s grade should probably not depend on whether the librarian’s printer happened to jam that week.
The simulated helpdesk
This is the format we build, so discount my enthusiasm accordingly, but the pitch is that it keeps what works from all three formats and drops the prep cost. Students work a live ticket queue with a working Active Directory, remote desktop, and machines that arrive pre-broken in ways that reset themselves. The frustrated caller is built in, answers questions, and never learns less than the person helping them, because it is software. You get a dashboard showing who resolved what instead of collecting screenshots.
The setup is one lesson: create a classroom, students join with a code in the browser, nothing installs. If your room runs Chromebooks, this is likely the only format on this list available to you at all.
Mix them
The honest recommendation is not one format, it is a floor: every week should include some activity where students do the work rather than read about it. Role-play costs nothing, start there tomorrow. Sabotage a machine when the topic deserves it. And if you want the daily ticket practice without the nightly reset ritual, the classroom version of the simulator comes with a 7-day classroom trial, offered with your quote, no card. Set up in one lesson, priced per student thereafter. Your evenings have better uses than unplugging drive cables.