Deploying Active Directory Federation Services (AD FS) & Web Application Proxy (WAP)

In this post I will show how to deploy AD FS farm in NLB cluster and then how to deploy highly available WAP in NLB cluster on Windows Server 2012 R2.

Overview of my lab setup

LAN – 192.168.1.0/24

  • DC – Active Directory Domain Controller, DNS
    • 192.168.1.1
    • 255.255.255.0
    • 192.168.1.254 (pfSense01)
  • ADFS01 – Active Directory Federation Services, primary server
    • 192.168.1.2
    • 255.255.255.0
    • 192.168.1.254 (pfSense01)
  • ADFS02 – Active Directory Federation Services, secondary server
    • 192.168.1.3
    • 255.255.255.0
    • 192.168.1.254 (pfSense01)
  • RSAT – Remote Server Administration Tools server
    • 192.168.1.4
    • 255.255.255.0
    • 192.168.1.254 (pfSense01)
  • PC01 – Windows 10
    • 192.168.1.5
    • 255.255.255.0
    • 192.168.1.254 (pfSense01)
  • pfSense01 – 192.168.1.254 – 192.168.2.254 (Router/Firewall)

DMZ – 192.168.2.0/24

  • WAP01 – Web Application Proxy
    • 192.168.2.1
    • 255.255.255.0
    • 192.168.2.253 (pfSense02)
  • WAP02 – Web Application Proxy
    • 192.168.2.2
    • 255.255.255.0
    • 192.168.2.253 (pfSense02)
  • PC02 – 192.168.2.3 (Windows 10)
    • 192.168.2.3
    • 255.255.255.0
    • 192.168.2.253 (pfSense02)
  • pfSense02 – 192.168.2.253 – 192.168.3.254 (Router/Firewall)

Internet – 192.168.3.0/24

  • PC03 — (Windows 10)
    • 192.168.3.1
    • 255.255.255.0
    • 192.168.3.254 (pfSense02)

Continue reading