Learning Hub · System Administrator

Windows Server enterprise architecture

A 12-week educational program for running a Windows Server environment the way an enterprise would: layered identity and operations, not extra roles on one machine.

Community learning track · not a commercial training product

This program is for learners, career-switchers, and lab members who want to understand enterprise Windows Server architecture by building a small, honest replica. PowerShell is the thread. Hyper-V is the classroom. Restore drills are the exam.

Plan on 10–12 weeks at 4–6 hours per week after you can survive on one Windows 11 box. Evaluation copies of Windows Server and Windows 11 are enough. Do not practice on a production domain.

12 weeks

Enterprise architecture track

4–6 hrs

Study and lab time each week

Hyper-V

Host for the scaled-down replica

Eval licenses

Windows Server + Windows 11

Path into the enterprise track

Skip foundations only if you already administer Windows without guessing. Otherwise start here, then join week 1 of the architecture program.

Foundations — own one Windows machine

Before the enterprise track: PowerShell, local security, and recovery on a single box.

  • Windows architecture: services, Event Viewer, Resource Monitor
  • PowerShell 7: files, users, services, Get-Help
  • Local users, groups, UAC, least privilege
  • NTFS permissions, shares, Windows Update, restore points
  • Firewall, RDP, WinRM

Harden a Windows 11 VM, split local admin, turn on the firewall, and recover from a checkpoint.

Operate a small Windows shop

One domain, one file share, Group Policy that actually applies.

  • Windows Server roles and features
  • Active Directory: domain, OUs, users, groups, computers
  • DNS and DHCP on Windows
  • Group Policy: password, software, mapped drives
  • File Server ACLs, quotas, shadow copies

DC plus one member PC. Create users, a working GPO, a file share with correct ACLs, and restore a deleted folder.

Enterprise architecture (this program)

A layered identity and operations platform — not extra roles stacked on one server.

  • Forest and site topology
  • Tiered administration and PKI
  • Virtualization, file platform, patch rings
  • Hybrid identity and disaster recovery
  • Incident notes and restore drills

Build the replica below, then run the 12-week sequence and the capstone outage drill.

Reference architecture

Enterprise Windows Server is a layered platform. The lab proves each layer at a smaller scale. It does not pretend a single VM is a data centre.

LayerWhat production looks likeWhat the lab can prove
IdentityOne forest, few domains; Entra ID for cloud apps; hybrid join1 forest, 1 domain, Entra Connect to a developer tenant
Directory HA2+ domain controllers per site, AD-integrated DNS, documented FSMO2 DCs; transfer and seize FSMO once in the lab
SitesAD sites match WAN/LAN; RODC at branches2 sites, 1 RODC, a site-linked GPO
PrivilegeTier 0/1/2, privileged access workstation, no daily Domain AdminSeparate admin OU, LAPS, a jump box
PKIOffline root plus issuing CA1 enterprise CA; HTTPS and LDAPS
ComputeHyper-V failover cluster or HCI2-node Hyper-V with live migration
FileDFS Namespace and replication, or a file clusterDFS-N, shadow copies, a tested restore
Patch / endpointIntune or MECM with ringed rolloutsWSUS rings: pilot, then broad
SecurityASR, Credential Guard, Defender XDR, SIEMAudit GPOs, event forwarding, attack-path discussion
Hybrid / DRAzure Arc, Site Recovery, 3-2-1 backup, written RPO/RTOBackup to a second disk; restore a DC and a file share
OpsChange records, runbooks, monitoring SLOsOne-page runbook and a “DC down” drill

Twelve weeks

Architecture discussion first, then a lab that matches the diagram, scaled down. Week 12 is a drill, not a slide recap.

  1. Week 1

    Forest design

    Domains versus OUs, UPN suffixes, and when not to create a second domain.

  2. Week 2

    DC topology

    Sites, subnets, replication, DNS aging and scavenging.

  3. Week 3

    Naming and IP

    AD-integrated DNS, split-brain, DHCP failover, the idea of IPAM.

  4. Week 4

    Tiered admin

    Privileged groups, Protected Users, LAPS, and a privileged access workstation.

  5. Week 5

    GPO at scale

    OU model, WMI filters, loopback processing, central store.

  6. Week 6

    PKI

    Auto-enrolment, LDAPS, web TLS, and what breaks when the CA dies.

  7. Week 7

    File platform

    DFS Namespace, quotas, access-based enumeration, backup versus checkpoints.

  8. Week 8

    Virtualization

    Cluster, CSV, quorum, and how to patch a host without a surprise outage.

  9. Week 9

    Identity hybrid

    Entra Connect, hybrid join, Conditional Access as a concept (lab tenant).

  10. Week 10

    Patch and config

    Update rings, WSUS or Intune, desired state with DSC or Ansible.

  11. Week 11

    Detect and recover

    Event IDs, non-authoritative DC restore, ransomware-aware backup.

  12. Week 12

    Capstone

    Draw the architecture, then a 30-minute incident: one DC and the file share are gone.

Minimum honest lab

Two domain controllers, two subnets, a file server, and a backup disk that you actually restore. Checkpoints are not backups.

PieceRole
HostWindows 11 Pro or Education with Hyper-V enabled
DC1First domain controller and DNS
DC2Second DC in the same domain
FILE1File server, DFS-N, shadow copies
HV-MGMTWindows Admin Center jump box
PC1Windows 11 domain member
RODCOptional branch read-only DC
NetworksTwo subnets = two AD sites
BackupSeparate VHDX; restore is the proof, not the job status

Non-negotiable rules

  • Domain controllers are Tier 0 — no extra software, no browsing, no daily login.
  • Do not put DC, Hyper-V, file, CA, and IIS on one server. That is a home-lab anti-pattern.
  • Every change has a backout: GPO, DNS, and replication included.
  • Backup is proven by restore, not by a green job.
  • Cloud identity does not replace on-prem AD until the organisation has chosen that; hybrid is the usual enterprise state.
  • Document the blast radius of FSMO roles, the CA, and the backup server.
Supporting Microsoft Learn links and evaluation downloads live in Resources. The Linux twin is here. Bring questions to Community lab hours.