DC01
AD DS + DNS + FSMO awareness
10.10.10.10/24
SCOPE 9 // PASS
Infrastructure case study Windows identity / Hyper-V
AD DS DNS GROUP POLICY POWERSHELL
A controlled Windows Server and Windows 11 homelab demonstrating identity, name resolution, workstation policy, least-privilege access, auditing, and reusable read-only administration.
adlab.testADLABDC01CLIENT0110.10.10.1/24
AD DS + DNS + FSMO awareness
10.10.10.10/24
Domain joined
10.10.10.20/24
DNS: 10.10.10.10
Domain boundary adlab.test
01 / Project overview
The project connects infrastructure setup, directory administration, security policy, access control, audit evidence, and PowerShell validation in one public-safe case study.
Objective
The environment runs on a Windows 11 Hyper-V host and uses a dedicated internal network. Each completed scope is documented with sanitized, recruiter-readable validation evidence.
02 / Architecture
CLIENT01 discovers and authenticates to the domain through DC01 across an isolated Hyper-V switch with no default gateway.
Host adapter 10.10.10.1/24
10.10.10.10/24adlab.test10.10.10.20/2410.10.10.10adlab.testadlab.test / ADLABDC01.adlab.test is writable and a Global Catalog.
LDAP SRV discovery uses _msdcs.adlab.test on TCP 389.
DFSR SYSVOL state 4 (Normal); all five FSMO roles are on DC01.
03 / Directory structure
The custom ADLAB hierarchy separates users, groups, computers, service accounts, and disabled objects into recruiter-readable administrative boundaries.
Daniel Weber · Sophia Klein
GG_IT_Users
Emma Fischer · Jonas Wagner
GG_HR_Users
Lukas Hoffmann · Hannah Becker
GG_Finance_Users
Naming convention
GG_<Department>_Users identifies department Global Security Groups.
Access is assigned to groups rather than directly to users.
04 / Domain services
adlab.test / ADLABWindows2025ForestWindows2025Domain_msdcsdc01.adlab.test / TCP 389Mail-related identity metadata
mailproxyAddressesSMTP: conventionThese values are native directory metadata only and do not provide mail delivery.
05 / Group Policy and account security
Workstation controls are applied through a dedicated GPO. Password and lockout settings remain distinct domain-level account policy.
ADLAB / effective security policy
VALIDATEDADLAB - Workstation Security Baseline
3 PASSBoundaryDefault Domain Policy was not modified for the dedicated workstation settings.
06 / File shares and permissions
Effective access is the most restrictive combination of SMB share and NTFS permissions. Department users were tested only against the three validated shares.
| Fictional test user | IT share | HR share | Finance share |
|---|---|---|---|
| Daniel Weber | ALLOWEDPASS | DENIED | DENIED |
| Emma Fischer | DENIED | ALLOWEDPASS | DENIED |
| Hannah Becker | DENIED | DENIED | ALLOWEDPASS |
Each fictional user accessed only their department share. No additional access tests are claimed.
07 / Auditing and Event Viewer
Aligned Security event ledgers connect failed authentication, account lockout, restoration, successful login, and logoff evidence.
08 / PowerShell administration
PowerShell Direct and reusable PSSessions validate DC01 and CLIENT01 without fabricating terminal output or changing configuration.
SCOPE_9_POWERSHELL_STATUS=PASS
09 / Troubleshooting
Only issues encountered during the documented homelab work are included.
Host RAM availability prevented the original DC01 startup allocation. Startup memory was adjusted while the validated Dynamic Memory range was preserved.
The isolated internal switch had no DHCP server. Static lab addresses replaced the initial APIPA assignments.
The DC01 Public firewall profile blocked inbound echo requests. The required built-in echo rule was enabled without disabling the firewall.
The LDAP SRV lookup was corrected to query the separate _msdcs.adlab.test zone.
Loop output was assigned to a variable before sorting or formatting.
Multi-part control flow was submitted together instead of as separate interactive commands.
Raw successful output confirmed the GPO when a filtered display appeared blank.
The active session inventory was enumerated and remaining PSSessions were closed.
10 / Validation evidence
Sanitized repository screenshots document completed validation from Scope 2 through Scope 9.
Scope 2
Validates DC01 domain services, DNS zones, records, and final service readiness.
Scope 3
Validates CLIENT01 membership, secure channel, authentication, and DNS registration.
Scope 4
Validates the ADLAB hierarchy for users, groups, computers, service accounts, and lifecycle states.
Scope 5
Validates native directory metadata for six fictional users and three department groups.
Scope 6
Validates the dedicated workstation GPO and its applied security controls.
Scope 7
Validates group-based share controls and the nine-point access matrix.
Scope 8
Validates account policy, controlled lockout, restoration, login, and Security events.
Scope 9
Validates reusable read-only checks across DC01 and CLIENT01.
11 / Production Mapping
Production considerations — not implemented in this homelab. These concepts require separate architecture, testing, security, operations, and recovery planning.
12 / Project outcome
The lab brings together AD DS, DNS, directory organization, workstation policy, least-privilege permissions, security auditing, troubleshooting, reusable PowerShell validation, and public-safe documentation.