Website under construction

Publishing Exchange Server 2013 
As noted earlier, the retirement of Forefront Threat Management Gateway left a number of Exchange 
administrators in a quandary about how to publish their Exchange server to the Internet. Although 
large organizations can generally take advantage of an existing hardware load balancer infrastructure 
to accomplish this task, small- and medium-sized businesses might not have the funds or expertise to 
manage a load balancer. This is where the Web Application Server role can be very useful. 
The basic principles for publishing Exchange 2013 Outlook Web App and the Exchange Admin Center 
through Web Application Proxy are outlined in detail at
 http://technet.microsoft.com/library/ 
dn635116(v=exchg.150).aspx
. However, to get a better understanding of some of the capabilities of 
Web Application Proxy on Windows Server 2016, consider the very simple scenario illustrated in 
Figure 2-76. 
Figure 2-76:
A scenario demonstrating Web Application Proxy on Windows Server 2016 
In this scenario, a user on a nondomain-joined machine named CLT01 will be connecting to Outlook 
Web App by using the URL https://mail.contoso.com/owa. The user’s request is sent over the external 
network to a Routing and Remote Access Server (RRAS01), which provides external DNS resolution for 
the zone contoso.com and routes traffic to the Contoso internal network for outside users. RRAS01 
routes the request for https://mail.contoso.com/owa into Contoso’s internal network to the Web 
Application Proxy server (WAP01), which is running Windows Server 2016. 
On WAP01, Outlook Web App has been published using AD FS preauthentication. In fact, a number of 
different Exchange services have been published using AD FS preauthentication or pass-through 
authentication, as demonstrated in Figure 2-77. 

---

77 
CHAPTER 2 | Software-defined datacenter