0.2Hardware: workstation, server, peripherals
The essentials in 30 seconds
- Workstation = 1 user; server = several, continuously and reliably — a server is designed for availability (redundancy, 24/7).
- CPU (processes), RAM (fast workspace), SSD/HDD storage (durable data): three roles not to be confused.
- Link the symptom to the right component: slow with several apps → RAM; slow to open files → SSD.
Running mini-case — Sofiane diagnoses the SME's workstations in Algiers
Sofiane, a support technician at the distribution SME in Algiers, receives two complaints the same morning. A salesperson complains that her workstation "crawls as soon as she opens several apps": Sofiane suspects a lack of RAM. A storekeeper finds that "files take forever to open": there, switching to an SSD will help. He also notes that the SME's file server must stay available continuously, with redundant power supplies and disks, because several services depend on it. He draws the reflex: link each symptom to the component responsible rather than changing everything.
Standalone case for this section: it returns in the course, the diagram, the script and the 48h challenge of section 0.2.
1. Workstation vs server
A workstation (desktop or laptop) serves a single user. A server provides a service to several users at once, continuously and reliably. This difference explains why a server is designed for availability: redundant power supplies and disks, 24/7 operation, because many depend on it simultaneously. Sofiane applies this distinction to every machine he encounters in the SME.
2. Components and peripherals
Every machine shares the same parts: processor (CPU), memory (RAM), storage (SSD/HDD), motherboard, sometimes a graphics card. Around them revolve the peripherals: input (keyboard, mouse, scanner), output (screen, printer), external storage. Sofiane can classify every device to locate a failure quickly.
3. Symptom → component
A useful reflex: a machine that is slow when many apps are open often lacks RAM; a machine sluggish at opening files benefits from switching to an SSD; random shutdowns suggest overheating or the power supply. Sofiane links the symptom to the component instead of "changing everything".
🔎 Concrete example — 🔎 Concrete example — RAM or SSD?
Sofiane listens to two complaints and pairs each with a component:
"It crawls as soon as I open several apps" → lack of RAM
"Files take forever to open" → switch to SSD
→ link the symptom to the component, don't change everything.Reading: RAM is the workspace (several apps); the SSD speeds up reading and writing files.
Lesson: diagnosis links a precise symptom to the right component, not to the whole machine.
Section vocabulary
- Workstation
- Computer (desktop or laptop) serving one user at a time.
Simple example: The salesperson's workstation, which Sofiane upgrades with RAM.
What it is not: the file server that serves the whole team.
Reflex: 1 user → workstation.
- Server
- A machine providing a service to several users, continuously and reliably.
Simple example: The SME's file server, available 24/7.
What it is not: an isolated PC used by a single person.
Reflex: several users + reliability → server.
- CPU / RAM / storage
- Processor (processes), memory (fast workspace), storage (durable data: SSD/HDD).
Simple example: Sofiane reads these three values to understand a slowdown.
What it is not: a single component summing up the whole machine.
Reflex: process / work / keep.
- Peripheral
- A device connected to the computer: input (keyboard), output (screen) or storage.
Simple example: Sofiane classifies printer, keyboard and external disk.
What it is not: an internal component of the motherboard.
Reflex: classify: input / output / storage.
- Redundancy
- Doubling critical elements (power supply, disks) so the service continues if one fails.
Simple example: Sofiane checks that the server has two power supplies.
What it is not: a single disk, a single point of failure.
Reflex: server → redundancy.
In practice — In practice — Taking inventory of a machine
- On a machine, note the CPU, the amount of RAM, the type and size of storage, like Sofiane.
- List the peripherals and classify each as input, output or storage.
- Indicate whether it is a workstation or a server, and why.
- Suggest the improvement that would speed up daily work the most.
Step-by-step script — diagnosing like Sofiane (5 min)
1) Note the exact symptom: slow with several apps, or when opening files? 2) Link it to a component: RAM or SSD. 3) Check whether the machine is a workstation (1 user) or a server (several, continuously). 4) Check the server's redundancy: doubled power supplies and disks. 5) Suggest the most useful improvement, without changing everything.
Good diagnosis always starts with a precise symptom, not with replacing hardware.
Copy-paste template — my hardware sheet
Running thread: Sofiane, support technician — distribution SME in Algiers.
Workstation = 1 user; Server = several, 24/7, reliable.
Components: CPU (processes) · RAM (work) · SSD/HDD (durable).
Symptom → component: several apps → RAM; files → SSD.
Server: think redundancy (power + disks).Workstation or server
Sofiane identifies whether the machine serves one user or the whole team.
Diagnosing a slowdown
Sofiane links a precise slowdown to the RAM or the SSD.
Peripheral inventory
Sofiane classifies each device as input, output or storage.
Server availability
Sofiane checks redundancy to avoid a single point of failure.
✓ Best practices
- Link each symptom to the right component.
- Server = think availability (redundancy, 24/7).
- Distinguish input / output / storage to locate a failure.
✗ Common pitfalls
- Confusing RAM (work) and storage (durable data).
- "Changing everything" instead of targeting the component.
- Believing a server is just a big PC.
Key takeaways
- Workstation = 1 user; server = several, continuously, reliably.
- CPU (processes), RAM (fast work), SSD/HDD storage (durable data).
- Peripherals: input, output or storage.
- Slow with many apps → RAM; slow to open files → SSD.
48h challenge — apply it tomorrow
Like Sofiane, take inventory of a machine: note its CPU, RAM and storage, classify two peripherals (input / output / storage), and match a slowdown symptom to the component that best explains it.
- I distinguish workstation and server and I understand why a server aims for availability.
- I name CPU, RAM and storage (SSD/HDD) and their roles.
- I link a slowdown symptom to the right component.
Frequently asked questions
What is the real difference between RAM and storage?
RAM is the fast, volatile workspace (cleared at shutdown); storage keeps data durably but more slowly. Too little RAM = slowdown; an HDD instead of an SSD = slow opening.
Does a small organisation necessarily need an on-site server?
Often not: the cloud (messaging, files, SaaS apps) is enough, with no server to maintain. The concept remains useful — a cloud service is, at bottom, someone else's very reliable server, as Sofiane points out.
What is the fundamental difference between a workstation and a server?