Initial Infrastructure Setup

Network Configuration

  • Created VLAN 50 (10.x.50.0/24) for AD lab isolation
  • Configured on: UniFi SFP-X router, Cisco Business switch, 5-port UniFi switch, Proxmox proxmox-host
  • Gateway: 10.x.50.1 (UniFi router handles inter-VLAN routing)
  • Created vmbr1 bridge on proxmox-host with VLAN 50 tag

ISOs Downloaded

  • Windows Server 2025 Evaluation
  • Windows 11 Enterprise LTSC Evaluation
  • Ubuntu 24.04.3 LTS Server
  • VirtIO drivers (required for Windows VMs on Proxmox)

VMs Created (proxmox-host, local-storage storage)

VM IDNameOSRAMDiskIPStatus
1001DC01Server 20254GB60GB10.x.50.10Domain controller
1002DC02Server 20254GB60GB10.x.50.11Domain controller
1003FS01Server 20254GB60GB + 100GB10.x.50.20Joined
1004WS01Win11 LTSC4GB60GBDHCPJoined
1005WS02Win11 LTSC4GB60GBDHCPJoined
1006WS03Win11 LTSC4GB60GBDHCPJoined
1007LINUX01Ubuntu 24.042GB40GBDHCPDomain joined

Active Directory Configuration

  • Forest: lab.local
  • NetBIOS: LAB
  • Forest/Domain functional level: WinThreshold (2016+)
  • DC01: Primary DC, DNS, DHCP (scope 10.x.50.100-200)
  • DC02: Secondary DC, DNS
  • DNS configured for redundancy (DCs point to each other first, then localhost)

Notes

  • VirtIO drivers required during Windows install (load from D:\vioscsi\w11\amd64)
  • VirtIO network driver installed post-install (D:\NetKVM\w11\amd64)
  • QEMU guest agent: D:\guest-agent\qemu-ga-x86_64.msi
  • Windows 11 OOBE: Use “Domain join instead” to skip Microsoft account

Cleanup

  • Archived slurm cluster (VMs 200-202 deleted, ansible/k8s configs moved to archive)

Completed (Session 2)

  • DHCP failover between DC01 and DC02 configured
  • LINUX01 joined to domain using SSSD/realmd
  • RSAT tools installed on WS01

Lessons Learned

Follow the lesson plan checkpoints

  • Skipping nslookup verification step meant the DNS forwarder issue wasn’t caught until RSAT install failed
  • The lesson plan has verification steps for a reason - use them

DNS Forwarders are critical

  • VLAN 50 needed a DNS forwarder on the UniFi gateway (10.x.50.1)
  • Without forwarders, internal DNS worked but external resolution failed
  • Symptom: google.com resolved, microsoft.com didn’t (microsoft uses stricter DNS/cert validation)
  • Error 0x80072f8f on Windows Update = certificate/DNS issue, not actually time

DHCP Failover gotcha

  • Both DCs must be authorized in AD before failover will work
  • DHCP service must be running on partner before creating relationship
  • Get-DhcpServerInDC to verify authorization status

Linux AD join (Ubuntu 24.04)

  • Packages: sssd-ad sssd-tools realmd adcli krb5-user samba-common-bin
  • Kerberos realm must be UPPERCASE: LAB.LOCAL
  • Minimal Ubuntu installs need libpam-runtime for pam-auth-update
  • Enable home dirs: echo "session required pam_mkhomedir.so" >> /etc/pam.d/common-session

Proxmox/LVM limitations

  • local-storage (LVM) doesn’t support live snapshots - need LVM-thin or ZFS
  • Issue #170 created to investigate options

Windows 11 OOBE annoyances

  • Security questions required for local accounts (just put garbage answers)
  • “Domain join instead” skips Microsoft account requirement

Next Steps

  • Phase 3: OU structure, users, groups (#133-137)
  • Phase 4: Group Policy basics
  • Phase 5+: Security hardening, LAPS, file services