
Capstone 1: Technical Incident Investigation
Where you are: Module 14 — Case Studies and Final Assessment · Capstone 1: Technical Incident Investigation · Draws on Chapters 2–9 and 13 of Dr. Tahseen Al Doori's Troubleshooting Essentials.
What this capstone asks you to do
In this capstone you investigate a realistic incident from first report to final record, using the full seven-step methodology. You will not touch any real equipment: everything you need is in the incident brief and the evidence packet below. Your job is to reason from the evidence, decide what you would test and in what order, plan a safe fix, and produce the written record a professional would leave behind.
By the end you will have shown that you can:
- turn several confused user reports into one clear, testable problem statement;
- rank theories of probable cause and select tests that separate them efficiently;
- interpret real command output and event log entries;
- plan a change with a backup and rollback, and recognise the limits of your authority;
- verify a fix fully and document the incident so that the organisation learns from it.
Allow 4 to 6 hours. Work on your own unless your tutor says otherwise.
The incident brief
(Fictional scenario.) Westbrook Community Library is a small public library with eleven staff and volunteers. You work for the managed IT service provider that supports it, as a first-line support technician. Your remit covers Tier 1 and Tier 2 work: user support, desktops, printers and basic network checks. The provider's server team (Tier 3) owns the library's server and its configuration. The internet line belongs to the library's internet service provider (Tier 4).
The library's network (from the provider's documentation)
| Item | Detail |
|---|---|
| Internet router | 192.168.20.1 on the wired network; also runs the staff Wi-Fi network (192.168.30.0/24) with its own DHCP and DNS |
| Wired network | 192.168.20.0/24; DHCP disabled on the router for this network |
| Server LIB-SRV01 | 192.168.20.5, in the locked cupboard behind the issue desk. Provides DHCP and DNS for the wired network, the shared S: drive (\LIB-SRV01\Shared) and the print queue \LIB-SRV01\FrontDesk-MFP |
| UPS | A small uninterruptible power supply (UPS) in the cupboard powers LIB-SRV01 and the network switch |
| Wired desktops | LIB-REC01 (reception), LIB-CAT01 to LIB-CAT03 (public catalogue PCs, left switched on permanently and set to start automatically when mains power returns; not on the UPS), LIB-OFF01 and LIB-OFF02 (back office) |
| Laptops | Two staff laptops, normally on staff Wi-Fi |
| Printer | One multifunction printer (MFP) on the wired network, 192.168.20.30 |
The provider's runbook for this site says: first-line technicians may power on LIB-SRV01 using its front power button if it is found switched off, provided there is no smell of burning, no smoke, no unusual heat and no warning on the UPS display. Any change to the server's settings, firmware or UPS configuration must be raised with the server team.
Monday 16 November 2026, 09:05 — the tickets arrive
Within ten minutes of opening, the library manager, Ms Okafor, logs one ticket on behalf of everyone: "Nothing works. The internet is broken, printing is broken and the new reception computer is broken too. We open to the public at 10:00."
Evidence packet
Treat everything below as evidence collected for you by a colleague on site. Some of it matters a great deal; some of it does not matter at all. Part of your task is to tell the difference.
E1. User interview notes (colleague's notes, 09:10–09:25)
| Who | What they said |
|---|---|
| Ms Okafor, manager | "Everything was fine on Friday when we closed at 17:00. The security company texted me on Sunday to say there was a power cut overnight, but the power came back. Nobody has been in since Saturday afternoon." |
| Sam, volunteer | "I set up the new reception computer, LIB-REC01, at 08:15 this morning. I plugged it into the same cable as the old one. It says there's no internet and the network icon has a yellow warning sign." |
| Priya, catalogue assistant | "The three catalogue PCs are on, but the catalogue website won't open on any of them. They had a Windows update message on Friday afternoon, so maybe it's that." |
| Daniel, back office | "I can't print. The printer shows Offline in the print queue. And my S: drive has a red cross on it. Outlook just says it's trying to connect. Funny thing: the printer's own touchscreen says Ready, and the photocopier part works fine." |
| Mei, staff laptop on Wi-Fi | "My laptop is fine for the internet. But the S: drive won't open for me either, and printing just sits in the queue." |
| Priya (asked specifically) | "The server cupboard seems quieter than usual. I didn't open it. The little box on the floor with the screen was showing normal, I think." |
E2. Error text, copied exactly
- LIB-CAT01, web browser: "This site can't be reached. www.example.org's server IP address could not be found."
- LIB-OFF01, opening S: — "\LIB-SRV01\Shared is not accessible. You might not have permission to use this network resource. The network path was not found."
- LIB-OFF01, print queue window title: "FrontDesk-MFP on LIB-SRV01 — Offline"
- LIB-REC01, network icon tooltip: "No internet access"
E3. Command output from LIB-CAT01 (09:30, extract)
C:\> ipconfig /all
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : westbrook.lan
Description . . . . . . . . . . . : Intel(R) Ethernet Connection I219-LM
Physical Address. . . . . . . . . : 00-15-5D-0A-1B-21
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.20.112(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, 13 November 2026 08:41:07
Lease Expires . . . . . . . . . . : Saturday, 21 November 2026 08:41:07
Default Gateway . . . . . . . . . : 192.168.20.1
DHCP Server . . . . . . . . . . . : 192.168.20.5
DNS Servers . . . . . . . . . . . : 192.168.20.5
C:\> ping 127.0.0.1
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
C:\> ping 192.168.20.1
Pinging 192.168.20.1 with 32 bytes of data:
Reply from 192.168.20.1: bytes=32 time<1ms TTL=64
Reply from 192.168.20.1: bytes=32 time<1ms TTL=64
Reply from 192.168.20.1: bytes=32 time=1ms TTL=64
Reply from 192.168.20.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.20.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
C:\> ping 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=14ms TTL=117
Reply from 8.8.8.8: bytes=32 time=13ms TTL=117
Reply from 8.8.8.8: bytes=32 time=14ms TTL=117
Reply from 8.8.8.8: bytes=32 time=15ms TTL=117
Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
C:\> ping www.example.org
Ping request could not find host www.example.org. Please check the name and try again.
C:\> nslookup www.example.org
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.20.5
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
C:\> ping 192.168.20.5
Pinging 192.168.20.5 with 32 bytes of data:
Reply from 192.168.20.112: Destination host unreachable.
Reply from 192.168.20.112: Destination host unreachable.
Reply from 192.168.20.112: Destination host unreachable.
Reply from 192.168.20.112: Destination host unreachable.
Ping statistics for 192.168.20.5:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
C:\> ping 192.168.20.30
Pinging 192.168.20.30 with 32 bytes of data:
Reply from 192.168.20.30: bytes=32 time=2ms TTL=64
Reply from 192.168.20.30: bytes=32 time=1ms TTL=64
Reply from 192.168.20.30: bytes=32 time=1ms TTL=64
Reply from 192.168.20.30: bytes=32 time=1ms TTL=64
Note for the investigator: when Windows reports "Destination host unreachable" from its own address, it means the computer could not reach that host on the local network at all. The statistics line still counts these error replies as "received".
E4. Command output from LIB-REC01, the new reception PC (09:35, extract)
C:\> ipconfig /all
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
Physical Address. . . . . . . . . : 00-15-5D-0A-1B-40
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IPv4 Address. . : 169.254.112.40(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
C:\> ping 192.168.20.1
PING: transmit failed. General failure.
E5. Event log extracts
LIB-CAT01, Windows Logs > System:
| Date and time | Level | Source | Event ID | Message (abridged) |
|---|---|---|---|---|
| 13/11/2026 16:02:11 | Information | WindowsUpdateClient | 19 | Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus |
| 15/11/2026 02:51:40 | Critical | Kernel-Power | 41 | The system has rebooted without cleanly shutting down first. |
| 15/11/2026 02:51:52 | Error | EventLog | 6008 | The previous system shutdown at 02:10:19 on 15/11/2026 was unexpected. |
| 16/11/2026 09:12:03 | Warning | DNS Client Events | 1014 | Name resolution for the name www.example.org timed out after none of the configured DNS servers responded. |
| 16/11/2026 09:12:44 | Warning | DNS Client Events | 1014 | Name resolution for the name catalogue.westbrook.lan timed out after none of the configured DNS servers responded. |
LIB-REC01, Windows Logs > System:
| Date and time | Level | Source | Event ID | Message (abridged) |
|---|---|---|---|---|
| 16/11/2026 08:16:30 | Warning | Dhcp-Client | 1001 | Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 0x00155D0A1B40. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server. |
E6. Physical observations (colleague at the server cupboard, 09:40, door opened with the manager's key)
- LIB-SRV01: front power LED off; fans silent; case cool to the touch; no smell of burning; no visible damage.
- UPS display: "Online — Battery 100% — Load 12%". No warning or fault message.
- UPS event log (shown on its display): 15/11 02:10 On battery · 15/11 02:31 Low battery — shutdown signal sent · 15/11 02:50 Utility power restored · 15/11 05:10 Battery charged.
- Network switch (also on the UPS): power LED on; link lights flashing on the ports for the desktops and the MFP.
Your tasks
Work through the seven steps in order and produce the written outputs listed for each. Keep a running test log as you go: in a real incident you would be recording as you work, not afterwards.
Step 1 — Identify the problem
- Sort the reports in E1 and E2 into symptoms and user theories. Which statements are facts you can test, and which are guesses?
- Answer the 5W1H questions (What, When, Where, Who, Which, How) for the incident as a whole. For Which, list every change you can find in the evidence, including ones you think are irrelevant.
- Decide on scope. Which devices are affected, which are not, and in what way? Note what the Wi-Fi laptops and the printer's own status tell you.
- Write one problem statement using the template from Module 4: Since [when], [who] cannot [what] on [where]. It happens [always / intermittently] when [how]. The most recent change was [which]. The error shown is "[exact message]". You may need two sentences to cover the main symptoms.
- State whether any data is at risk and whether a backup is needed before you go further.
Step 2 — Establish theories of probable cause
- List at least four theories that could explain some or all of the symptoms. Include the users' own theories.
- Rank them, simplest and most likely first, and give a one-line reason for each rank. Name the theory you think explains all the symptoms with a single cause.
- Name one cognitive bias that could mislead an investigator here and how you will guard against it.
Step 3 — Test the theories
- For each of your top three theories, describe one small, safe test that would confirm or reject it, and state what result you would expect if the theory were true.
- Using the evidence packet, record the result of each test that the evidence already answers. Use the test log format below. Where the evidence does not answer a test, say what you would do next.
- Apply the five-step connectivity sequence to the output in E3. State which step fails first and what that tells you. Then explain why ping 8.8.8.8 succeeds while ping www.example.org fails.
- Explain the 169.254 address on LIB-REC01 (E4, E5) and why LIB-CAT01 still has a valid address. Is LIB-REC01 a separate fault?
- State the confirmed cause and the evidence that confirms it. Identify the most probable underlying reason the server did not come back after the power cut (E6), and say how that could be confirmed and by whom.
Test log format:
| # | Time | Theory tested | Test performed | Expected if true | Actual result | Confirmed / rejected |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 | ||||||
| 4 | ||||||
| 5 |
Step 4 — Establish a plan of action
- Write a plan in numbered steps that restores service before the library opens. For each step, state: what will change, who does it, what could go wrong, and how it will be undone (rollback).
- State what must be backed up or recorded before the change, and why (or why no backup is needed for a particular step).
- Identify which parts of the fix are within your authority under the runbook and which must be escalated, to whom, and with what urgency. Consider both the immediate restoration and any change to stop it happening again.
- Describe how you will communicate with Ms Okafor before, during and after the work, in plain language. Include a realistic time estimate.
Step 5 — Implement the solution or escalate
- Describe how you would carry out your plan one change at a time, testing after each. Include the order in which the affected devices should recover and anything you would need to do on LIB-REC01 and the catalogue PCs.
- Write the escalation note to the server team for the part of the problem that is beyond your authority (keep it brief here; Capstone 2 asks for a full six-part handover).
Step 6 — Verify full system functionality
- Write a verification checklist of at least eight checks that together prove the original problem is resolved and nothing else has broken. Cover every symptom group from Step 1, at least one check per affected device type, and user confirmation.
- Propose two preventive measures that would stop this incident recurring or shorten it next time, and justify each in one or two sentences.
Step 7 — Document findings, actions and outcomes
- Complete the problem log below (adapted from Appendix B of the book) for the whole incident.
| Field | Entry |
|---|---|
| Reference number | |
| Date and time reported | |
| Reported by / contact | |
| Device, system and location | |
| Problem statement | |
| Exact error message | |
| Recent changes | |
| Theories tested and results | |
| Root cause | |
| Solution applied | |
| Verified by (user) and date | |
| Preventive measures | |
| Time spent / escalated to |
- Write a reflection of 150 to 250 words: which piece of evidence was most decisive, which piece was a distraction, and what you would do differently next time.
Deliverables
Submit one document containing, in this order:
| # | Deliverable | Linked tasks |
|---|---|---|
| 1 | 5W1H table, scope summary and problem statement | 1–5 |
| 2 | Ranked theories with reasons, and the bias you will guard against | 6–8 |
| 3 | Test log and the confirmed cause with supporting evidence | 9–13 |
| 4 | Safe plan of action with backup, rollback, authority and escalation decisions, and communication plan | 14–17 |
| 5 | Implementation sequence and escalation note | 18–19 |
| 6 | Verification checklist and two preventive measures | 20–21 |
| 7 | Completed problem log | 22 |
| 8 | Reflection (150–250 words) | 23 |
Recommended length: 1,800 to 3,000 words, plus tables.
Assessment rubric
Your work is marked against six criteria. Each is scored at one of four levels; the weight shows how much the criterion contributes to the total of 100.
| Criterion (weight) | Excellent (4) | Proficient (3) | Developing (2) | Beginning (1) |
|---|---|---|---|---|
| 1. Problem definition (15) | Complete 5W1H with every relevant change listed; scope precisely separates affected and unaffected devices; problem statement follows the template, is factual and testable, and contains no unproven cause | 5W1H mostly complete; scope correct; statement specific with minor gaps | Several 5W1H gaps; scope partly wrong; statement vague or includes a guess as fact | No usable problem statement; symptoms and theories confused |
| 2. Theories and reasoning (15) | Four or more plausible theories, sensibly ranked with reasons; single-cause theory identified; user theories evaluated, not adopted; relevant bias named with a practical guard | Reasonable theories and ranking; minor reasoning gaps | Few theories or unexplained ranking; follows a user theory without testing | Jumps straight to a fix |
| 3. Testing and evidence interpretation (25) | Tests are small, safe and discriminating; command output and event logs read correctly (first failing step, DNS versus connectivity, 169.254, unreachable server); red herrings explicitly ruled out with evidence; confirmed cause and probable underlying reason correctly stated, with how to confirm the latter | Most evidence read correctly; cause confirmed; one minor misreading | Some correct interpretation but significant misreadings; cause asserted rather than demonstrated | Evidence ignored or misread throughout |
| 4. Plan, safety and authority (20) | Numbered plan with owner, risk and rollback for every step; correct backup and recording decisions; runbook conditions respected; server-side changes correctly escalated with urgency; clear, honest user communication | Sound plan with minor omissions in rollback or communication | Plan lacks rollback or exceeds authority in one respect | Unsafe or unauthorised actions; no rollback |
| 5. Verification and prevention (15) | Eight or more checks covering every symptom group and device type, including the user's confirmation; two well-justified preventive measures aimed at the cause | Checklist covers main symptoms; preventive measures sensible | Checklist incomplete or omits user confirmation; prevention generic | Little or no verification |
| 6. Documentation and professional writing (10) | Problem log complete, accurate and usable by a stranger; reflection is specific and self-critical; clear British English and professional tone throughout | Log mostly complete; reflection relevant | Log has gaps; reflection descriptive only | Log missing or unusable |
Scoring: for each criterion, multiply the level (1–4) by the weight and divide by 4. A total of 70 or above indicates the standard expected of a confident first-line technician.
Submission checklist
Before you submit, tick every line.
| ✓ | Check |
|---|---|
| ☐ | My problem statement uses the template and contains no unproven cause |
| ☐ | I have listed every change in the evidence under Which, including those I later ruled out |
| ☐ | I have at least four ranked theories with reasons |
| ☐ | Every test in my log has an expected result and an actual result |
| ☐ | I have explained the first failing step of the connectivity sequence |
| ☐ | I have explained both the 169.254 address and why LIB-CAT01 kept its address |
| ☐ | Every step of my plan has an owner, a risk and a rollback |
| ☐ | I have stayed within the runbook and escalated server-side changes |
| ☐ | My verification checklist includes user confirmation |
| ☐ | My two preventive measures address the cause, not just the symptom |
| ☐ | My problem log is complete |
| ☐ | I have not asked anyone for a password or suggested any destructive command |
| ☐ | I have proofread for clarity and British English spelling |
Safety and authority reminder. In a real incident, open locked cupboards only with permission, never open a server's or UPS's case, and stop immediately if you notice burning smells, smoke, unusual heat or a UPS fault warning. Changes to servers, firmware or UPS settings belong to the team that owns them.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026): §2.2–2.5 (principles and biases), §3.1–3.8 (seven steps), §4.1–4.6 (5W1H, evidence, problem statement), §6.1–6.7 (isolation), §7.2–7.3 (event logs, network commands, connectivity sequence), §9.1, §9.3–9.4 (one device or all, IP addressing, DNS), §13.1–13.5 (escalation, communication, documentation), Chapter 14 Case Study 1, Appendix B (problem log)
