This visual map organizes your 12 enterprise servers into 5 distinct architectural tiers.
Click on any server card below to view its functional role, network configuration, clustering state, and setup prerequisites.
Filter Tier:
Clustered / Sync Active Active/Passive Node Load Balanced Farm
Perimeter / Bastion ZoneExternal HTTPS & Administrative Entry Point
Breakdown of server roles and high-availability pairing across the environment.
Redundancy Guarantee:
Every tier features minimum N+1 redundancy. Storage uses 3-way mesh replication to protect against dual-node failure.
Connection Routing:
Clients connect exclusively through rdg.tgs.local. Direct RDP to internal session hosts or database nodes is strictly dropped by perimeter firewalls.
⚡
High Availability & Dynamic Failover Simulator
Test the environment's resilience! Toggle key nodes "OFFLINE" to observe how Network Load Balancing (NLB), DFS Referral Tracking, and Windows Server Failover Clustering (WSFC) automatically reroute operational traffic.
Simulate Server Outage
🚪 RD Gateway Entry VIP (rdg.tgs.local)
HEALTHY (100% Capacity)
Both Gateway nodes are actively responding to inbound SSL requests on Port 443. Load is evenly distributed across TGS-GW-01 and TGS-GW-02 via Network Load Balancing.
DFS Namespace referral target is actively directing user requests across all three full-mesh replication nodes. User profiles and FSLogix containers are completely synchronized.
🗄️ SQL Virtual Network Name (TGS-SQLCluster)
PRIMARY ONLINE (TGS-SQL-01)
SQL Server Failover Instance is running on primary node TGS-SQL-01. Synchronous data replication is maintaining zero data loss protection on TGS-SQL-02.
Dynamic Telemetry & Referral Log● LIVE
[SYSTEM INIT] Cluster health check passed. All 12 server endpoints responding.
Check Event Viewer under DFS Replication logs for Event ID 4602 and 4614.
Tier 2: DFS Shared Data Tier (`TGS-FS-01`, `TGS-FS-02`, `TGS-FS-03`)
The three file servers utilize a DFS Namespace backed by DFS Replication to provide fault tolerance and automatic referral failover for RDS profiles and company data.
Acts as the perimeter security barrier and strict administrative access layer.
RD Gateway Clustering (`TGS-GW-01` & `TGS-GW-02`)
Install Remote Desktop Gateway role on both nodes.
Import a unified SSL SAN / Wildcard certificate (e.g., *.tgs.local).
Configure Network Load Balancing (NLB) or DNS round-robin pointing rdg.tgs.local to both node IPs.
Configure identical RD CAP (Authorization) and RD RAP (Resource) policies across both gateways.
Management Jump Box Configuration (`TGS-JMP-01`)
Acts as the single administrative bastion host. Workstations are prohibited from connecting directly to internal server subnets. Admins must tunnel through RD Gateway to TGS-JMP-01 before launching administrative tools.
Viewing All Network Paths: HTTPS (443) traffic enters via the RD Gateway NLB cluster VIP. Gateways proxy RDP sessions (3389) to RDS hosts. RDS hosts mount profiles over SMB (445) from DFS storage targets and query database records from the SQL Failover Cluster Instance (1433).