karanth.ovh · virtualization & validation lab

Proxmox VE Lab Architecture & Topology

The articles, PowerShell modules, and Active Directory runbooks on this site are never hypothetical. Every script, GPO baseline, and Kerberos flow is exercised inside a private, hardware-isolated Proxmox VE 8.x testbed on a Dell OptiPlex platform, segmented via a multi-bridge pfSense virtual router with zero ingress exposure to the public internet.

LAB STATUS: ISOLATED PRIVATE ENVIRONMENT (ZERO INGRESS EXPOSURE)
HYPERVISOR: PVE 8.x · ROUTING: PFSENSE (4 BRIDGES) · STORAGE: DUAL TIER
Bare-Metal Hardware

Compute & Storage Plane

Dedicated Dell OptiPlex bare-metal host running Proxmox VE. Dual-tier storage configuration isolating hypervisor OS binaries from virtual machine disk datastores.

Hardware NodeDell OptiPlex Platform
HypervisorProxmox VE 8.x
Datastore TierDedicated VM Datastore + local-lvm
Disk InterfaceVirtIO-SCSI Single (qcow2)
CPU Policyx86-64-v2-AES (Hardware Virtualization)
Network & Security Boundary

pfSense Router & Bridges

Dedicated virtual pfSense appliance acting as the security perimeter, utilizing 4 distinct virtual network bridges to enforce strict zero-trust segmentation.

Gateway RouterpfSense CE Appliance
Uplink Segmentvmbr0 (Outbound NAT Only)
Identity Tiervmbr1 (Domain Controllers & PKI)
Management Tiervmbr2 (Admin Jumpbox & Endpoints)
Observability Tiervmbr3 (Prometheus & Workloads)
Identity & PKI Topology

Enterprise AD Environment

Production-representative multi-DC forest separating directory authentication, certificate services (AD CS), and dedicated administrative jumpboxes.

Primary DCDC-01 (FSMO Role Holder / PDCe)
Replica DCDC-02 (KCC Topology & DFSR Partner)
PKI / CADedicated Enterprise Subordinate CA
Admin JumpboxTier-1 Management Server (RSAT / JEA)
Validation ClientWindows 10/11 Enterprise Endpoint
Logical Workload Segmentation Matrix
Tier Workload Class Architectural Responsibility Virtual Network Bridge Access Policy
Perimeter Boundary Gateway pfSense Firewall & DNS Resolver vmbr0 / vmbr1 / vmbr2 / vmbr3 Strict Boundary
Tier 0 Primary Domain Controller PDC Emulator, RID Master, Kerberos KDC vmbr1 (Identity Mesh) Isolated
Tier 0 Replica Domain Controller AD Replication Partner, DFSR SYSVOL Sync vmbr1 (Identity Mesh) Isolated
Tier 0 Enterprise Certificate Authority AD CS, LDAPS, Kerberos PKINIT Issuance vmbr1 (Identity Mesh) Isolated
Tier 1 Management Server RSAT Console, PowerShell JEA Endpoint vmbr2 (Management) Admin Only
Tier 2 Windows Enterprise Client GPO Client-Side Extensions, Kerberos Testing vmbr2 (Endpoints) Segmented
Services Prometheus Observability Infrastructure Telemetry & Node Metrics vmbr3 (Monitoring) Internal Only
Services Automation Workers & APIs Automated Background Tasks & App Services vmbr3 (Workloads) Internal Only
Logical Network Segmentation & Routing Topology
[ Outbound NAT Gateway ] (Zero Inbound Exposure)
             │
             ▼
┌─────────────────────────────────────────────────────────────────────────────┐
│ Proxmox VE Hardware Node (Dell OptiPlex Platform · PVE 8.x)                 │
│                                                                             │
│   ┌─────────────────────────────────────────────────────────────────────┐   │
│   │ pfSense Boundary Appliance (4 Isolated Linux Virtual Bridges)       │   │
│   └──────┬──────────────────┬──────────────────┬──────────────────┬─────┘   │
│          │ (vmbr0: Uplink)  │ (vmbr1: Identity)│ (vmbr2: Mgmt/End)│ (vmbr3) │
│          │                  │                  │                  │         │
│          ▼                  ▼                  ▼                  ▼         │
│     [Outbound NAT]    ┌───────────┐      ┌───────────┐      ┌─────────────┐ │
│                       │ DC-01     │      │ Mgmt-Host │      │Prometheus   │ │
│                       │  (PDCe)   │      │ (Jumpbox) │      │  (Metrics)  │ │
│                       ├───────────┤      ├───────────┤      ├─────────────┤ │
│                       │ DC-02     │      │ Client    │      │Automation   │ │
│                       │  (DFSR)   │      │ (Windows) │      │  Workers    │ │
│                       ├───────────┤      └───────────┘      └─────────────┘ │
│                       │ CA Tier   │                                         │
│                       │ (AD CS)   │                                         │
│                       └───────────┘                                         │
│                             │                                               │
│                             └── Isolated Inter-DC Replication & LDAPS       │
└─────────────────────────────────────────────────────────────────────────────┘
    

Lab Design & Validation Principles

Operational Posture
PRINCIPLE 1: PROPER SEPARATION OF PKI AND DIRECTORY ROLES

Hosting Active Directory Certificate Services (AD CS) on a Domain Controller is an acknowledged enterprise security hazard. In this lab, the Certificate Authority is segregated from the Domain Controllers, enabling authentic testing of Enterprise Subordinate CAs, Kerberos PKINIT, and LDAPS without compromise.

PRINCIPLE 2: DUAL-DC REPLICATION & DFSR VALIDATION

Scripts authored on karanth.ovh are never run against a single isolated DC. Having both DC-01 and DC-02 ensures that KCC partner topology creation, metadata cleanup, and DFSR SYSVOL consistency are proven to function across real domain controller boundaries.

PRINCIPLE 3: HARDWARE-CONSTRAINED RIGOR

Running enterprise-grade identity topologies on a single Dell OptiPlex requires meticulous resource discipline—managing ballooning memory, VirtIO SCSI controllers, and CPU thread distribution. This operational constraint forces every PowerShell automation script to be lightweight, efficient, and leak-free.