Skip to content

HQ Example Overlay

This example captures the current lab state already approved for the first canonical deployment.

Customer profile

Key Value
CLIENT_CODE GEIL
SITE_CODE HQ
SITE_NAME Headquarters Lab
ENV_STAGE LAB
DOMAIN_FQDN corp.gntech.me
APPROVED_WIN11_EDITION Windows 11 Enterprise LTSC

Approved network values

VLAN Subnet Gateway Notes
20 172.20.20.0/24 172.20.20.1 Servers
30 172.20.30.0/24 172.20.30.1 Workstations
40 172.20.40.0/24 172.20.40.1 Printers
70 172.20.70.0/24 172.20.70.1 Guest
90 172.20.90.0/24 172.20.90.1 Backup
100 172.20.100.0/24 172.20.100.1 Hypervisor
110 172.20.110.0/24 172.20.110.1 Build only
120 172.20.120.0/24 172.20.120.1 RouterOS containers

Approved VM inventory

VMID Hostname Role VLAN Notes
4010 HQ-CHR01 Router Trunk Already deployed
4000 TPL-WS2025 Golden template 110 during build Windows Server 2025 Standard golden image
4011 HQ-DC01 AD DS, DNS, DHCP 20 First domain controller
4012 HQ-FS01 File server 20 SMB and backup staging
4001 TPL-W11E Golden template None after capture Windows 11 Enterprise LTSC workstation golden image
4030 TPL-W11E-BUILD Transient build VM 110 during build Generalized source VM used before cloning into 4001
4031 HQ-CL01 Client 30 Validation endpoint
4032 HQ-CL02 Client 30 Validation endpoint

Deviations from base blueprint

  • Proxmox is already in place before the start of this guide.
  • CHR deployment is treated as completed state; this guide begins with operational baseline validation.
  • HQ-CHR01 was deployed from RouterOS 7.21.5 Long-term on local-zfs.
  • TPL-WS2025 was built on VLAN 110 with temporary IP 172.20.110.10/24.
  • CHR must be registered with a trial license before throughput-sensitive validation.
  • cloudflared currently runs as a RouterOS container on 172.20.120.10/24.

Evidence index

Runbook Evidence location Status
P01-T02 To be captured during implementation Planned
P01-T03 To be captured during implementation Planned
P01-T04 To be captured during implementation Planned
P01-T05 To be captured during implementation Planned
P01-T06 To be captured during implementation Planned
P01-T07 To be captured during implementation Planned
P01-T08 To be captured during implementation Planned
P02-T01 To be captured during implementation Planned
P02-T02 To be captured during implementation Planned
P02-T03 To be captured during implementation Planned
P02-T04 To be captured during implementation Planned
P02-T05 To be captured during implementation Planned
P03-T01 To be captured during implementation Planned
P03-T02 To be captured during implementation Planned
P03-T03 To be captured during implementation Planned
P03-T04 To be captured during implementation Planned
P02-T07 To be captured during implementation Planned
P02-T08 To be captured during implementation Planned
P03-T06 To be captured during implementation Planned
P03-T07 To be captured during implementation Planned
P03-T08 To be captured during implementation Planned