Deployment Guide-MS Exchange 2013
Deployment Guide-MS Exchange 2013
Deployment Guide
Copyright Notices
Copyright © 2002-2018 KEMP Technologies, Inc. All rights reserved. KEMP Technologies and the KEMP
Technologies logo are registered trademarks of KEMP Technologies, Inc.
KEMP Technologies, Inc. reserves all ownership rights for the LoadMaster and KEMP 360 product line
including software and documentation.
Used, under license, U.S. Patent Nos. 6,473,802, 6,374,300, 8,392,563, 8,103,770, 7,831,712, 7,606,912,
7,346,695, 7,287,084 and 6,970,933
Table of Contents
1 Introduction 5
1.2 Prerequisites 5
References 34
1 Introduction
The KEMP LoadMaster combines versatility with ease-of-use to speed deployment of the complete
portfolio of advanced messaging applications and protocols used by Exchange 2013, including Outlook
Web App (OWA), Outlook Anywhere (OA), Exchange ActiveSync (EAS), Simple Mail Transfer Protocol
(SMTP), Post Office Protocol version 3 (POP3) and Internet Message Access Protocol version 4 (IMAP4).
With built-in SSL acceleration and/or overlay, the LoadMaster offloads a key source of CPU drain to
improve the capacity of Client Access Servers (CASs). Layer 7 health checking at the LoadMaster ensures
that if one of the CASs becomes inaccessible, the load balancer will take that server offline, while
automatically re-routing and reconnecting users to other functioning servers.
The entire KEMP LoadMaster product family, including the Virtual LoadMaster (VLM) supports Microsoft
Exchange 2013.
KEMP’s LoadMaster family of products is available in various models to support networks of different
throughput requirements. Information in this manual applies to all LoadMaster models.
1.2 Prerequisites
It is assumed that the reader is a network administrator or a person otherwise familiar with networking
and general computer terminology. It is further assumed that the Exchange 2013 environment has been
set up and the KEMP LoadMaster has been installed.
l Installed the Microsoft Servers, Active Directories and followed other Microsoft requirements
Exchange 2013 includes the following solutions for switchover and failover redundancy:
High availability: Exchange 2013 uses Database Availability Groups (DAGs) to keep multiple copies of
your mailboxes on different servers synchronized. That way, if a mailbox database fails on one
server, users can connect to a synchronized copy of the database on another server.
Site resilience: You can deploy two Active Directory sites in separate geographic locations, keep the
mailbox data synchronized between the two, and have one of the sites take on the entire load if the
other fails.
Online mailbox moves: During an online mailbox move, email accounts are still accessible. Users are
only locked out for a brief period of time at the end of the process, when the final synchronization
occurs. Online mailbox moves can be performed across forests or in the same forest.
Shadow redundancy: Shadow redundancy protects the availability and recoverability of messages
while they are in transit. With shadow redundancy, the deletion of a message from the transport
databases is delayed until the transport server verifies that all the next hops for that message have
completed. If any of the next hops fail before reporting successful delivery, the message is
resubmitted for delivery to the hop that did not complete.
l The Mailbox Server which includes all of the functions to route mail, render web content and receive
voicemail
l The CAS which authenticates clients and routes requests to the correct mailbox server
The CAS now acts as a reverse proxy. The CAS no longer renders OWA when a user accesses it. The CAS
determines which mailbox database their mailbox is located on and provides the request to the back-end
mailbox server that hosts the database. The mailbox server then renders the OWA content, not the CAS.
Clients no longer interact with Exchange using RPC, it is all done over HTTPS. Outlook Anywhere is the
protocol that Outlook clients use to access their mailbox.
Exchange 2013 Service Pack 1 introduces new connectivity option MAPI/HTTP which is disabled by
default. It must be manually enabled by administrator and is only available as a connectivity option to
clients running Office 2013 Service Pack 1 or later. Older clients continue using RPC/HTTP.
Unlike previous versions of Exchange, Exchange 2013 no longer requires session affinity at the load
balancing layer. For more information, refer to the related article in The Exchange Team Blog: Load
Balancing in Exchange 2013.
Server load balancing serves two primary purposes. It reduces the impact of a single CAS failure within
one Active Directory site. In addition, server load balancing ensures that the load on the CAS and
Transport servers is optimally distributed.
Two key changes in Exchange 2013 make load balancing a lot simpler:
l HTTPS-only access from clients means that there is only one protocol to consider. The HTTP failure
states are well known and clients typically respond in a similar way.
l As OWA is rendered on the same server that is hosting the user’s mailbox database; if a client hits a
different CAS there is no performance degradation as the session rendering for that user is already
up and running.
Forms-based authentication has also been improved. The authentication cookie is provided to the user
after logon and it is encrypted using the CAS’s SSL certificate. This allows a logged in user to resume their
session on a different CAS without having to re-authenticate (if servers share the same SSL certificate).
For more information and steps on how to import and use templates, refer to the Virtual Services and
Templates, Feature Description.
For steps on how to manually add and configure the Virtual Services, refer to the sections below.
The Microsoft Exchange 2013 templates currently available are grouped in three downloadable files as
follows:
l Exchange2013Core
This file contains templates for non-SSL offloaded HTTPS, SSL offloaded HTTPS and SMTP Virtual
Services.
l Exchange2013ESP
This set contains individual templates for a HTTPS service with SSL offloading and an SMTP
service, both with ESP enabled.
These services are only necessary if you want to use ESP functionality.
l Exchange2013Additional
This set contains templates for IMAP, POP and SMTP services, including variants for STARTTLS
and SSL secured services.
If you create another Virtual Service using the same template, ensure to
change the Service Name to a unique name.
1. Select the Add New option within the Virtual Services section of the main menu tree.
2. Enter the IP address of the Virtual Service in the Virtual Address field.
4. Type a name, for example Exchange 2013 HTTPS in the Service Name field.
6. Click the Add this Virtual Service button to add the Virtual Service.
To add content rules to the VS, follow the steps in the Create Content Rules section.
Minor changes now need to be made to the redirect Virtual Service that was added:
2. Click Modify on the Redirect Virtual Service with the blank name which has the same IP
address as the Virtual Service that was just created.
3. Enter a recognizable Service Name, for example Exchange 2013 HTTP Redirect and click Set
Nickname.
Follow the instructions below to set up the parent HTTPS Virtual Service:
1. Select the Add New option within the Virtual Services section of the main menu tree.
2. Enter the IP address of the Virtual Service in the Virtual Address field.
4. Type a name, for example Exchange 2013 HTTPS in the Service Name field.
6. Click the Add this Virtual Service button to add the Virtual Service.
1. In the Real Servers section of the Virtual Services options page, click the Add SubVS button.
2. A message stating that the SubVS has been created appears, click OK.
The following steps deal with creating a SubVS for an Exchange service
such as owa.
3. In the SubVSs section of the SubVS options page, click the Modify button next to the SubVS
and select the following options:
4. Within the ESP Options section, ensure that the Enable ESP check box is not selected.
5. In the Real Servers section of the SubVS options page select the following options:
a) Enter /owa/healthcheck.htm in the URL field and click the Set URL button.
c) Ensure that the GET option is selected from the HTTP Method drop-down list.
6. When finished editing the SubVS, click Back. Now you can add other SubVSs to this Virtual
Service as needed.
Content Rules need to be created for the Virtual Services to function correctly.
To create a Modify URL rule for owa please complete the following steps:
1. Select the Rules & Checking > Content Rules menu option
3. Enter a relevant name, for example Redirect_Root in the Rule Name field
To create a Content Matching rule for owa please complete the following steps:
1. Select the Rules & Checking > Content Rules menu option.
3. Enter a relevant name, for example OWA in the Rule Name field.
4. Select the Content Matching option is selected in the Rule Type drop-down list.
5. Ensure the Regular Expression option is selected in the Match Type drop-down list.
Create additional Content Matching rules following steps 1 to 8 above but using the values as described
in the table below.
1. Select the Add New option within the Virtual Services section of the main menu tree.
4. Enter a recognizable Service Name, for example Exchange 2013 HTTPS Offloaded.
*If the Redirect Root content rule does not exist yet, refer to the Create Content Rules section to create
it.
8. A message stating that the SubVS has been created appears, click OK.
The following steps deal with creating a SubVS for an Exchange service
such as owa.
9. In the SubVSs section of the SubVS options page, click the Modify button next to the SubVS
and select the following options:
10. When finished editing the SubVS, click Back. Now you can add other SubVSs to this Virtual
Service as needed.
11. Configure each SubVS using the settings in the table below.
1. Select the Add New option within the Virtual Services section of the main menu tree.
4. Enter a Service Name, for example Exchange 2013 HTTPS Offloading with ESP.
*If the Redirect Root content rule does not exist yet, refer to the Create Content Rules section to create
it.
7. Now you need to add the SubVSs. To do this, expand the Real Servers section and click Add
SubVS. Then click the Modify button to configure it.
Details for each of the SubVSs that need to be created are below.
8. For each of the SubVSs created, ensure that in the ESP section, the Enable ESP checkbox is
selected, and select the following options:
a) Select the User Access, Security and Connection check boxes in ESP Logging.
c) Enter all of the allowed virtual hosts into the Allowed Virtual Hosts text box, for
example mail.example.com, and click the Set Allowed Virtual Hosts button.
Client
Allowed Virtual Pre-Authorization Excluded SSO Image SSO Greeting
SubVS Name Auth. Server Auth. mode
Directories Directories Set Message
mode
Please enter
Form your
ECP /ecp* .Form based Exchange
Based Exchange
credentials.
/microsoft-server- Basic
ActiveSync Basic Auth. n/a
activesync* Auth.
Please enter
Form your
OWA /owa* /owa/<guid@smtpdomain>*1 Form based Exchange
Based Exchange
credentials.
Please enter
Authentication Form your
/* Form based Exchange
Proxy Based Exchange
credentials.
you add a Real Server to the Authentication Proxy SubVS. For further
information on KCD, refer to the KCD, Feature Description
The SSO Greeting Message field accepts HTML code, so you can insert
your own image if required. However, there are several characters that
are not supported. These are the grave accent character ( ` ) and the
single quotes (’). If a grave accent character is used in the SSO Greeting
Message, the character will not display in the output, for example a`b`c
becomes abc. If a single quote is used, users will not be able to log in.
9. For each of the SubVSs created, configure the settings as shown in the following table:
10. After the SubVSs have been created, in the parent Virtual Service; enable Content Switching
by clicking the Enable button in the Advanced Properties section.
1. Select the Add New option within the Virtual Services section of the main menu tree.
2. Enter the IP address of the Virtual Service in the Virtual Address field.
4. Type a name, for example Exchange 2013 IMAP in the Service Name field.
6. Click the Add this Virtual Service button to add the Virtual Service.
1. Select the Add New option within the Virtual Services section of the main menu tree.
4. Enter a recognizable Service Name, for example Exchange 2013 IMAP with STARTTLS.
1. Select the Add New option within the Virtual Services section of the main menu tree.
1. Select the Add New option within the Virtual Services section of the main menu tree.
2. Enter the IP address of the Virtual Service in the Virtual Address field.
4. Enter a recognizable Service Name, for example Exchange 2013 IMAPS Offloaded.
1. Select the Add New option within the Virtual Services section of the main menu tree.
2. Enter the IP address of the Virtual Service in the Virtual Address field.
4. Type a name, for example Exchange 2013 POP in the Service Name field.
6. Click the Add this Virtual Service button to add the Virtual Service.
1. Select the Add New option within the Virtual Services section of the main menu tree.
4. Enter a recognizable Service Name, for example Exchange 2013 POP with STARTTLS.
1. Select the Add New option within the Virtual Services section of the main menu tree.
1. Select the Add New option within the Virtual Services section of the main menu tree.
4. Enter a recognizable Service Name, for example Exchange 2013 POPS Offloaded.
1. Select the Add New option within the Virtual Services section of the main menu tree.
2. Enter the IP address of the Virtual Service in the Virtual Address field.
4. Type a name, for example Exchange 2013 SMTP in the Service Name field.
6. Click the Add this Virtual Service button to add the Virtual Service.
1. In the main menu of the LoadMaster WUI, select Virtual Services and Add New.
1. In the main menu of the LoadMaster WUI, select Virtual Services and Add New.
4. Enter a recognizable Service Name, for example Exchange 2013 SMTP with STARTTLS.
1. In the main menu of the LoadMaster WUI, select Virtual Services and Add New.
4. Enter a recognizable Service Name, for example Exchange 2013 SMTP with ESP.
References
Unless otherwise specified, the documents below can be found at
http://kemptechnologies.com/documentation
http://blogs.technet.com/b/exchange/archive/2014/03/05/load-balancing-in-exchange-2013.aspx
https://technet.microsoft.com/en-us/library/dd298140(v=exchg.150).aspx