Daniel Łaszkowicz

Problem

Practice common identity and access tasks that appear in real support environments.

Implementation

A Windows Server domain with users, groups, DNS, shared resources, and basic Group Policy practice.

Technologies

Screenshots / artifacts

• Server Manager domain overview
• Active Directory Users and Computers structure
• Group Policy notes and screenshots

Lessons Learned

• Document each change so the lab reads like a real support handover.
• Practice least-privilege thinking before adding permissions.

Problem

Build confidence with the checks and tools used during first-line Windows troubleshooting.

Implementation

A repeatable Windows support checklist covering local accounts, services, updates, storage, and event logs.

Technologies

Screenshots / artifacts

• Event Viewer examples
• Windows services checks
• Troubleshooting checklist captures

Lessons Learned

• Start with repeatable checks before jumping to conclusions.
• Keep notes short enough to be useful during a support call.

Problem

Learn how to isolate basic connectivity, DNS, DHCP, and packet-level symptoms.

Implementation

A small troubleshooting notebook for IP configuration, DNS lookups, DHCP behavior, and packet captures.

Technologies

Screenshots / artifacts

• Packet capture examples
• Network notes
• Topology sketch

Lessons Learned

• Name the layer before troubleshooting the symptom.
• Use packet captures to confirm behavior instead of guessing.

Problem

Create a beginner SOC workflow for collecting logs, reading alerts, and writing simple investigations.

Implementation

Planned lab for Windows endpoint logs, Wazuh alerts, simple triage notes, and beginner investigation writeups.

Technologies

Screenshots / artifacts

• Planned dashboard
• Alert examples
• Triage notes

Lessons Learned

• Start with clear log sources before adding detection complexity.
• Write investigations so another junior analyst could follow them.