I built a Windows domain, joined a Windows 11 client, and verified my first domain sign-in after troubleshooting DNS and time synchronization. Security monitoring is next.
Learning what happens behind a Windows login
After my Wazuh and Azure labs, I wanted to understand the accounts, permissions, and sign-ins behind security events. I’m building this lab myself with step-by-step guidance and documenting each stage.
Latest progress · November 19, 2026
- Joined the Windows client: I connected CLIENT01 to soclab.test and verified its domain membership in PowerShell.
- Verified my first domain sign-in: I created my Freddy Flores domain account, added it to GG_Lab_Employees, completed the required first password change, and confirmed the account was signed in on CLIENT01.
- Checked DNS discovery: I configured the client to use DC01 for DNS and verified it could find the domain controller.
- Resolved setup issues: I installed guest tools for clipboard sharing, renamed the client, and troubleshot a stopped Windows Time service until synchronization succeeded.
The foundation
I built a Windows Server 2025 domain controller and a Windows 11 Enterprise Evaluation client on Ubuntu using QEMU/KVM. I configured a stable server address, created soclab.test, and verified directory services, DNS records, shared domain folders, and external name resolution.
I organized separate directory areas for users, workstations, and groups, then created test identities and checked employee group membership. The server and client use the shared default NAT network with my existing lab VMs.
What I learned while troubleshooting
Domain membership and domain sign-in are different checks. After joining CLIENT01, PowerShell showed PartOfDomain: True, but whoami still showed the local administrator. I then signed in with my domain account and verified both the username and computer name.
DNS was another important piece: the client needed to use the domain controller’s DNS service to discover the domain. I also resolved the stopped Windows Time service and verified synchronization before joining. Post-join domain time checks are still on my list.
Why this matters for security
This work gives me practice with account provisioning, group membership, DNS troubleshooting, and verifying who is actually signed in. Those are useful foundations for investigating identity-related alerts. Security auditing, Wazuh collection, policy exercises, and detection results are still ahead.
What comes next
The client is joined and domain sign-in is verified. Next, I’ll check the client’s directory location and move it into SOCLab/Workstations, verify post-join time synchronization and client updates, and check deletion protection on the organizational units.
After those checks, I plan to configure security auditing and Wazuh collection, then generate controlled sign-in and account/group changes to investigate the resulting records.
The screenshots below highlight the main milestones. The full journal, exact settings, troubleshooting notes, and additional evidence are on GitHub.