A+ home lab from spare parts: what to gather, what to break, what to write down

You cannot get the troubleshooting habit from a page that has the fault already solved.

Why a lab for A+

A+ is about setting up, maintaining and troubleshooting. Troubleshooting carries great weight in both exams, and performance-based questions test if you can act, not just recall. Keep at least a quarter of every week hands-on, and let the lab be where that quarter goes.

What to gather

• An old desktop or laptop you are allowed to open.
• A spare drive.
• Your home router.

If you have those, you already have most of what the plan needs. A family member's retired machine often works.

What to set up

1. Take the computer apart and rebuild it. Name every part as you remove it.
2. Install Windows and a Linux distribution in virtual machines. Use them to explore settings, tools and commands you would meet in support.
3. Set up a secure home Wi-Fi network. Change defaults, choose strong settings and note what each does.
4. Create faults on purpose. Then diagnose them using the method: identify the problem, establish and test a theory, plan and fix, verify and document.

Work only on equipment that belongs to you or that you have permission to change, and back up anything you care about first.

The fault log

Write each fault in one row. The row is a record, but it is also practice for the documentation step.

The last column matters. Verification is the step candidates skip, because the machine seems fine once it starts.

A first set of ten faults

You can start with these:

1. A cable removed from the drive.
2. A memory module half seated.
3. A wrong boot order.
4. A wrong DNS setting.
5. A service stopped.
6. A user with the wrong permissions.
7. A full disk.
8. A blocked port on the router.
9. A wrong Wi-Fi password.
10. A startup program that slows sign-in.

Do two a week, and fill the log as you go. After ten rows, you will notice you ask the same first question each time. That first question is the start of the troubleshooting habit.

How the lab protects that quarter

A short session, such as 45 minutes, is better than one long weekend, because the log forces you to recall what you did the last time.

Pair each fault with an objective

Add one more column and write the objective number beside each fault. Hardware and network faults tie to Core 1 troubleshooting, and software faults to Core 2. When two weeks of rows leave a domain empty, that domain is where your next faults should come from.

Use the log later

After you pass, pick two rows and turn them into short CV lines. A repaired fault with a verified fix says more to a support manager than a list of topics.