Академический Документы
Профессиональный Документы
Культура Документы
Why F5?
F5 offers a complete suite of application delivery technologies designed to provide a highly scalable, secure, and responsive Exchange
deployment.
• Terminating
HTTPS connections at the BIG-IP LTM reduces CPU and memory load on Client Access Servers, and simplifies TLS/
SSL certificate management for Exchange 2010 and Exchange 2013 SP1.
• T
he BIG-IP LTM can balance load and ensure high-availability across multiple Client Access servers using a variety of load-
balancing methods and priority rules.
• T
he BIG-IP LTM TCP Express feature set ensures optimal network performance for all clients and servers, regardless of operating
system and version.
• The LTM provides content compression features which improve client performance.
• T
he BIG-IP Access Policy Manager (APM), F5's high-performance access and security solution, can provide pre-authentication
and secure remote access to Exchange HTTP-based Client Access services.
Product Version
Microsoft Exchange Server 2010, 2010 SP1, SP2, and SP3; 2013, 2013 CU1, 2013 CU2, 2013 CU3, 2013 SP1
BIG-IP system 11.0, 11.0.1, 11.1, 11.2.x, 11.3, 11.4, 11.4.1, 11.5, 11.5.1
Deployment Guide version 2.4 (see Document Revision History on page 112)
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Contents
Introduction 3
What is F5 iApp? 3
Deployment Scenarios 6
This BIG-IP LTM will load balance and optimize Client Access Server traffic 6
This BIG-IP LTM will receive HTTP-based Client Access traffic forwarded by a BIG-IP APM 6
Preparation worksheets 8
Configuring the BIG-IP iApp for Microsoft Exchange Server 2010 and 2013 11
Getting started with the Exchange iApp template 11
Configuring the BIG-IP LTM to load balance and optimize Client Access Server traffic 13
Configuring the LTM to receive HTTP-based Client Access traffic forwarded by a BIG-IP APM 31
Configuring the BIG-IP APM to provide secure remote access to Client Access Servers 43
Optional: Configuring the BIG-IP system to support MAPI over HTTP in Exchange 2013 SP1 49
Next steps 51
Troubleshooting 53
Appendix E: Active Directory and Exchange Server configuration for NTLM 104
2
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Introduction
This document provides guidance for using the updated, downloadable BIG-IP iApp Template to configure the Client Access server role
of Microsoft Exchange Server, as well as instructions on how to configure the BIG-IP system manually. This iApp template was developed
for use with both Exchange Server 2013 and 2010.
By using the iApp template, you can configure the BIG-IP system to support any combination of the following services supported by Client
Access servers: Outlook Web App (which includes the HTTP resources for Exchange Control Panel), Exchange Web Services, Outlook
Anywhere (RPC over HTTP, including the Offline Address Book), ActiveSync, Autodiscover, RPC Client Access (MAPI) for Exchange 2010
only, POP3 and IMAP4. This guide also contains manual configuration instructions for users familiar with F5 devices.
You can also visit the Microsoft page of F5’s online developer community, DevCentral, for Microsoft forums, solutions, blogs and more:
http://devcentral.f5.com/Microsoft/.
ake sure you are using the most recent version of this deployment guide, available at
Important: M
http://www.f5.com/pdf/deployment-guides/microsoft-exchange-2010-2013-iapp-dg.pdf
To provide feedback on this deployment guide or other F5 solution documents, contact us at solutionsfeedback@f5.com.
What is F5 iApp?
New to BIG-IP version 11, F5 iApp is a powerful set of features in the BIG-IP system that provides a new way to architect application
delivery in the data center. iApp includes a holistic, application-centric view of how applications are managed and delivered inside, outside,
and beyond the data center. The iApp template for Microsoft Exchange Server acts as the single-point interface for building, managing, and
monitoring the Exchange 2010 and 2013 Client Access role.
For more information on iApp, see the White Paper F5 iApp: Moving Application Delivery Beyond the Network:
http://www.f5.com/pdf/white-papers/f5-iapp-wp.pdf.
hh This
document provides guidance on using the downloadable iApp for Microsoft Exchange 2010 and 2013 available via
http://support.f5.com/kb/en-us/solutions/public/13000/400/sol13497.html, and not the iApp found by default in BIG-IP version 11.
You must use this downloadable iApp for BIG-IP versions 11.0 and later (we strongly recommend version 11.3 or later) as
it contains a number of fixes and enhancements not found in the default iApp, or other downloadable versions.
Note that the way we are versioning the downloadable iApp templates has changed. Previous versions of the downloadable
templates included the date (04_06 and 06_08). Beginning with this version of the template, we are using a numbering system (this
version is v1.2.0). The first number represents a major version, the second number a minor version, and the third number is used
for important fixes to a previous version.
For users familiar with the BIG-IP system, there are manual configuration tables at the end of this guide. Because of the complexity
of this configuration, we strongly recommend using the iApp to configure the BIG-IP system.
hh If you have an existing Exchange application service from a previous version of the downloadable iApp, see Upgrading from a
previous version of the iApp template on page 10 for instructions on how to upgrade the configuration.
hh T
he overwhelming majority of the configuration guidance in this document is performed on F5 devices. We provide a summary
of Exchange configuration steps for reference only; for complete information on how to deploy or configure the components of
Microsoft Exchange Server, consult the appropriate Microsoft documentation. F5 cannot provide support for Microsoft products.
3
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
hh F
or this deployment guide, the BIG-IP LTM system must be running version 11.0 or later. If you are using a previous version of the
BIG-IP LTM, see the Deployment Guide index on F5.com. The configuration in this guide does not apply to previous versions.
! Warning
To run the Microsoft Exchange iApp template, you must be logged into the BIG-IP system as a user that is
assigned the admin role. For more information on roles on the BIG-IP system, see the BIG-IP User Accounts
chapter of the BIG-IP TMOS: Concepts guide.
hh If you are using the BIG-IP system to offload SSL (Exchange 2010 and Exchange 2013 SP1 and later only) or for SSL Bridging, we
assume you have already obtained an SSL certificate and key, and it is installed on the BIG-IP LTM system. To configure your Client
Access servers to support SSL offloading, you must first follow the Microsoft documentation. See
http://social.technet.microsoft.com/wiki/contents/articles/how-to-configure-ssl-offloading-in-exchange-2010.aspx.
Make sure you follow the correct steps for the version of Exchange Server that you are using.
hh New While SSL offload was not supported in the RTM version of Exchange Server 2013, it is now supported in 2013 SP1
(http://social.technet.microsoft.com/wiki/contents/articles/15946.how-to-configure-ssl-offloading-in-exchange-2013.aspx).
If you using Exchange 2013 and are not yet on SP1, you must change the default setting for Outlook Anywhere on each Client
Access Server so that SSL offloading is not configured.
hh New Exchange 2013 SP1 introduces the MAPI over HTTP transport protocol
(http://technet.microsoft.com/en-us/library/dn635177(v=exchg.150).aspx). The iApp template does not yet support this new
protocol. See Optional: Configuring the BIG-IP system to support MAPI over HTTP in Exchange 2013 SP1 on page 49 for
instructions on configuring the BIG-IP system for MAPI over HTTP.
hh If deploying BIG-IP APM features, including Edge Gateway, you must fully license and provision APM before starting the iApp
template. For the remainder of this guide, we refer to BIG-IP APM and Edge Gateway collectively as BIG-IP APM.
hh F
or Exchange Server 2010 and 2013 SP1 only: We generally recommend that you do not re-encrypt traffic between your BIG-IP
APM and BIG-IP LTM because both BIG-IP systems must process the SSL transactions. However, if you choose to re-encrypt,
we strongly recommend you use a valid certificate (usually SAN-enabled) rather than the default, self-signed certificate for the
Client SSL profile on your BIG-IP LTM system. If not re-encrypting traffic, you do not need a certificate on your BIG-IP LTM.
hh T
his template currently only supports the use of a single DNS name and corresponding certificate and key for all services, or
multiple DNS names using a SAN-enabled certificate and key. Support for multiple names, each with separate corresponding
certificates and keys, will be in a future release.
hh If you have existing, manually created Node objects on the BIG-IP system and given these nodes a name, you cannot use the
IP addresses for those nodes when configuring the iApp. You must first manually delete those nodes and re-add them without a
name, or delete the nodes and let the iApp automatically create them.
hh If using a single virtual server for all HTTP-based Client Access services as recommended, you must obtain the Subject
Alternative Name (SAN) certificate and key from a 3rd party certificate authority that supports SAN certificates, and then import it
onto the BIG-IP system. In versions prior to 11.1, the BIG-IP system does not display SAN values in the web-based
Configuration utility, but uses these certificates correctly.
Note
For more information on SAN certificates, see Subject Alternative Name (SAN) SSL Certificates on page 103.
hh F
5’s advanced monitors for Autodiscover, Exchange Web Services, and Outlook Anywhere support Basic and NTLMv1
authentication only. See Troubleshooting on page 53 for more information.
hh If using BIG-IP APM, the following table shows the Exchange Server (Client Access Server) settings:
4
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
In our example, we use the following conventions. In your configuration, you may have the same FQDN for Outlook Anywhere, OWA, and
RPC Client Access (Exchange 2010 only), and/or use split DNS to direct internal and external clients to different virtual servers:
Your network topology may differ considerably from the example shown.
Note
You may choose to use separate names for all four HTTP services and the RPC Client Access service
(Client Access Array - Exchange 2010 only)
DNS Settings
This table contains information on DNS settings (and our example settings) for this deployment.
If the SRV record listed below is not used, you must also have at If the SRV record listed below is not used and you don’t want to use the SCP, you
least one of these, set to the same IP as your OWA FQDN: must also have at least one of these, set to the same IP as your OWA FQDN:
To prevent internal users from receiving a password prompt, internal DNS must not
have an A record for the FQDN for Outlook Anywhere.
_autodiscover._tcp.example.com: port 443, host ‘owa.example.com’
SRV Records _autodiscover._tcp.example.com: port 443, host ‘owa.example.com’
(optional; Outlook can use SCP instead. See note above and Further Reading below)
Exchange Server 2010 only. Exchange 2013 does not use RPC.
1
Further reading:
• Summary of SRV records on Wikipedia: http://en.wikipedia.org/wiki/SRV_record
• Specification for SRV records (RFC2782): http://tools.ietf.org/html/rfc2782
• Microsoft KB article on SRV records and the Autodiscover service: http://support.microsoft.com/kb/940881
• ‘Understanding the Autodiscover Service’ (including SCP information): http://technet.microsoft.com/en-us/library/bb124251.aspx
5
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Deployment Scenarios
The iApp greatly simplifies configuring the BIG-IP system for Microsoft Exchange 2010 and 2013 Client Access Server roles. Before
beginning the Application template, you must make a decision about the scenario in which you are using BIG-IP system for this
deployment. The iApp presents the following three deployment options. You will choose one of these options when you begin configuring
the iApp.
This BIG-IP LTM will load balance and optimize Client Access Server traffic
You can select this scenario to manage, secure, and optimize client-generated Client Access Server traffic using the BIG-IP system. This is
the traditional role of the BIG-IP LTM and should be used in scenarios where you are not deploying BIG-IP Access Policy Manager (APM) on
a separate BIG-IP system. In this scenario, you have the option of configuring the BIG-IP APM to secure HTTP-based virtual servers on this
system.
You would not select this option if you intend to deploy a separate BIG-IP APM that will provide secure remote access to Exchange CAS
HTTP services.
2. Y
ou can optionally use the BIG-IP APM module to provide secure access and proxied authentication (pre-authentication) for
HTTP-based Client Access services: Outlook Web App, Outlook Anywhere, ActiveSync, and Autodiscover). The BIG-IP APM
presents a login page to end users that takes the place of the forms-based login page normally presented by Outlook Web App.
Users provide credentials through the BIG-IP APM form; the BIG-IP APM then authenticates the user to Active Directory.
3. T
he BIG-IP LTM load balances and optimizes the traffic to the Client Access Servers, including the services which are not HTTP-
based: RPC Client Access (MAPI), POP3, and IMAP4.
This BIG-IP LTM will receive HTTP-based Client Access traffic forwarded by a BIG-IP APM
You can select this scenario to configure BIG-IP LTM with a single virtual server that receives Exchange Client Access HTTP-based traffic
that has been forwarded by a separate BIG-IP APM. The virtual server can also accommodate direct traffic, e.g. internal clients that do not
use the BIG-IP APM, and non-HTTP traffic that is not handled by BIG-IP APM such as POP3 and IMAP4.
This scenario would be used together with the following scenario, in which you configure a separate BIG-IP APM to send traffic to this
BIG-IP LTM device.
Internal clients
2. The BIG-IP LTM receives HTTP-based Client Access traffic from a separate BIG-IP APM, or directly received the non HTTP-based
traffic.
3. If you have internal Exchange clients, all Client Access Server traffic from the internal clients goes directly to the BIG-IP LTM.
4. T
he BIG-IP LTM load balances and optimizes the traffic to the Client Access Servers, including the services which are not
HTTP-based: RPC Client Access (MAPI), POP3, and IMAP4.
6
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Note
hile this scenario can accommodate internal clients, we do not recommend using this virtual server in that way. We
W
strongly recommend creating a second instance of the iApp on this BIG-IP LTM for the direct traffic/internal users.
You must use a unique virtual server IP address; all of the other settings can be identical. Once both iApps have been
created, you would configure Split DNS (use the same domain name, but different zones and IP addresses for internal
and external clients). For more information about Split DNS, refer to your DNS documentation.
Internal clients
1. HTTP-based Client Access traffic goes to the BIG-IP APM, which provides proxy authentication and secure remote access.
Note
If you want to allow RPC Client Access, POP3 or IMAP4 access from external users, you must separately
configure your BIG-IP system by re-running the iApp, selecting the first scenario ("This BIG-IP LTM will load
balance and optimize Client Access Server traffic"), choosing which of those protocols you wish to allow, and then
configuring your Client Access servers as pool members.
2. After authentication, the BIG-IP APM sends the traffic to a separate BIG-IP LTM for intelligent traffic management.
7
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Preparation worksheets
For each section of the iApp Template, you need to gather some information, such as Client Access server IP addresses and domain
information. The worksheets do not contain every question in the template, but rather include the information that is helpful to have in
advance. Use the worksheet(s) applicable to your configuration. More information on specific template questions can be found on the
individual pages. You might find it useful to print these tables and then enter the information.
Key:
Same Subnet Different Subnets
If the maximum number of expected concurrent users per Client If the Client Access Servers are a different subnet from the BIG-IP
Access Server is more than 6,000, you need one IP address for virtual servers, and do not use the BIG-IP as their default gateway:
BIG-IP virtual servers and each 6,000 users or fraction thereof:
Client Access Servers will If the maximum number of expected concurrent users per Client
be on: Access Server is more than 6,000, you need one IP address for
each 6,000 users or fraction thereof:
IMAP4:
Outlook Web App URI If you are deploying Outlook Web App, what is the URI for reaching OWA if different than the default (http(s)://<fqdn>/owa/):
If you are deploying RPC Client Access (MAPI), and do not want to use the default Dynamic port range, specify a port for:
RPC Client Access ports MAPI:
(Exchange 2010 only)
Address Book:
8
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
If deploying Autodiscover, email address for monitoring: Second mailbox for monitoring (recommended):
If deploying Autodiscover, 2nd email address for monitoring:
Advanced Monitor Mailbox account name in Active Directory for the monitors:
configuration 2nd mailbox account name in Active Directory for the monitors:
Associated password:
Associated password for this account:
Domain name (can be FQDN or NETBIOS) of the user account
used for monitors: 2nd domain name (can be FQDN or NetBIOS) of the user account
used for monitors:
Important: Advanced monitors for Autodiscover, EWS, and Outlook
Anywhere support Basic and NTLMv1 authentication only.
If deploying Outlook Web App, which authentication method have you configured:
Outlook Web App
Forms-Based Authentication (default) Important: If you are deploying BIG-IP APM, you must use Forms-Based.
authentication method
Basic or Windows Integrated authentication
Same FQDN Different FQDNs
FQDN for all HTTP-based Client Access services: You need a FQDN for each HTTP-based Client Access services
you are deploying:
Same FQDN for all HTTP-
based Client Access services Outlook Web App:
or different FQDNs
Outlook Anywhere:
ActiveSync:
Autodiscover:
Outlook Web App FQDN If you are deploying BIG-IP APM and Outlook Web App, you need the FQDN this is used to access OWA (such as owa.example.com):
What are the Active Directory FQDNs and IP address that this BIG-IP system can contact (use FQDN and not NETBIOS name):
Active Directory FQDNs and
1. 2.
IP addresses that the BIG-iP
3. 4.
system can contact
5. 6.
Active Directory Domain
What is the Active Directory Domain name (must be in FQDN format):
name for Exchange users
If Anonymous Binding is not allowed in your Active Directory implementation, you need an Active Directory account with administrative
Active Directory permissions:
Anonymous binding User name:
Password:
If deploying the "BIG-IP APM will provide secure remote access to CAS" scenario
BIG-IP APM virtual server What is the IP address you want to use for your BIG-IP APM virtual server:
SSL Certificate:
SSL Certificate and Key
Key:
Re-encrypt the traffic to the You must know if the remote BIG-IP LTM that will receive traffic from this BIG-IP APM is using a self-signed/default certificate and key
BIG-IP virtual server or a certificate signed by a Certificate Authority.
What is the virtual server address on the remote BIG-IP LTM to which this BIG-IP APM will forward traffic:
Remote LTM virtual server
9
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
2. Follow the instructions to download the Microsoft Exchange iApp to a location accessible from your BIG-IP system.
i Important
You must download the file, and not copy and paste the contents. F5 has discovered the copy paste operation
does not work reliably.
7. Click the Browse button, and then browse to the location you saved the iApp file.
8. Click the Upload button. The iApp is now available for use.
1. From the Main tab of the BIG-IP Configuration utility, expand iApp and then click Application Services.
2. Click the name of your existing Microsoft Exchange application service from the list.
4. At the top of the page, in the Template row, click the Change button to the right of the list.
6. R
eview the questions in the new template, making any necessary modifications. Use the iApp walkthrough section of this guide for
information on specific questions.
If you used a previous version of the iApp to deploy BIG-IP APM, you must add the FQDN and IP address for each Active Directory
server in your domain that the BIG-IP system can contact. The iApp now creates a pool for the Active Directory servers (even for only
one server), where in previous versions of the template you could only specify a single Active Directory server.
7. Click Finished.
10
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Configuring the BIG-IP iApp for Microsoft Exchange Server 2010 and 2013
Use the following guidance to configure the BIG-IP system for Microsoft Exchange Server Client Access Role using the iApp template.
2. On the Main tab, expand iApp, and then click Application Services.
5. F
rom the Template list, select f5.microsoft_exchange_2010_2013_cas.v1.2.0.
The new Microsoft Exchange template opens.
Advanced options
If you select Advanced from the Template Selection list at the very top of the template, you see Device and Traffic Group options for
the application. This feature, new to v11, is a part of the Device Management configuration. This functionality extends the existing High
Availability infrastructure and allows for clustering, granular control of configuration synchronization and granular control of failover. To use
the Device and Traffic Group features, you must have already configured Device and Traffic Groups before running the iApp. For more
information on Device Management, see the product documentation.
1. Device Group
To select a specific Device Group, clear the Device Group check box and then select the appropriate Device Group from the list.
raffic Group
2. T
To select a specific Traffic Group, clear the Traffic Group check box and then select the appropriate Traffic Group from the list.
Inline help
At the bottom of the Welcome section, the iApp template asks about inline help text.
1. Do
you want to see inline help?
Select whether you want to see informational and help messages inline throughout the template, or if you would rather hide this inline
help. If you are unsure, we recommend having the iApp display all inline help.
Important and critical notes are always shown, no matter which selection you make.
ff Y
es, show inline help text
Select this option to see all available inline help text.
ff N
o, do not show inline help
If you are familiar with this iApp template, or with the BIG-IP system in general, select this option to hide the inline help text.
Deployment Scenario
Choose the option that best describes how you plan to use the BIG-IP system you are currently configuring. The scenario you select from
the list determines the questions that appear in the rest of the iApp. The scenarios were described in Deployment Scenarios on page 6.
1. Which scenario describes how you will use the BIG-IP system?
Choose the scenario that best describes the way you plan to use this BIG-IP system. Guidance for each scenario is contained in a
separate section of this deployment guide. Click the link to go to the relevant section of the guide for the scenario you plan to deploy.
11
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
ff B
IG-IP LTM will load balance and optimize CAS traffic
Select this scenario to manage, secure, and optimize client-generated Client Access Server traffic using the BIG-IP system. This
is the traditional role of the BIG-IP LTM and should be used when you are not deploying APM on a separate BIG-IP system.
In this scenario, if you have fully licensed and provisioned BIG-IP APM you have the option of configuring it to provide proxy
authentication for HTTP-based services on this system.
Do not select this option if you intend to deploy a separate BIG-IP APM that will provide secure remote access to Exchange
CAS HTTP-based services.
For this role, go to Configuring the BIG-IP LTM to load balance and optimize Client Access Server traffic on page 13.
ff B
IG-IP LTM will receive HTTP-based CAS traffic forwarded by a BIG-IP APM
Select this scenario to configure BIG-IP LTM with a single virtual server that receives Exchange Client Access HTTP-based traffic
that has been forwarded by an BIG-IP APM. The virtual server can also accommodate direct traffic, for example internal clients
that do not use the BIG-IP APM, and non-HTTP traffic that is not handled by BIG-IP APM such as POP3 and IMAP4.
For this role, go to Configuring the LTM to receive HTTP-based Client Access traffic forwarded by a BIG-IP APM on page 31.
ff B
IG-IP APM will provide secure remote access to CAS
Select this role to configure the BIG-IP system as a BIG-IP APM that will use a single HTTPS (port 443) virtual server to provide
proxy authentication and secure remote access to Exchange HTTP-based Client Access services without requiring the use of
an F5 Edge Client. The traffic will be forwarded to another BIG-IP running LTM which will provide advanced load balancing,
persistence, monitoring and optimizations for those services.
For this role, go to Configuring the BIG-IP APM to provide secure remote access to Client Access Servers on page 43.
12
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Configuring the BIG-IP LTM to load balance and optimize Client Access Server traffic
If you chose the first scenario, LTM will load balance and optimize CAS traffic, use this section for guidance on configuring the iApp. Again,
do not chose this option if you will deploy a separate BIG-IP APM to provide secure remote access to HTTP-based Client Access services.
Analytics
This section of the template asks questions about Analytics. The Application Visibility Reporting (AVR) module allows you to view statistics
specific to your Microsoft Exchange implementation. AVR is available on all BIG-IP systems v11 and later, however you must have the AVR
provisioned for this option to appear. Note that this is only for application visibility reporting, you can view object-level statistics from the
BIG-IP without provisioning AVR.
i Important
Enabling Analytics may adversely affect overall system performance. If you choose to enable Analytics, we recommend
gathering statistics for a set time period, such as one week, and then re-entering this template and disabling Analytics
while you process the data.
If you plan on using AVR for analytics, we recommend creating a custom Analytics profile. To create a new profile, from the Main tab, select
Profiles and then click Analytics. Click New and then configure the profile as applicable for your configuration. See the online help or
product documentation for specific instructions. To select the new profile, you need to restart or reconfigure the iApp template.
1. Do
you want to enable Analytics for application statistics?
Select whether you want to enable AVR for Analytics for HTTP-based services. Note that Analytics does not always properly report
the HTTP methods of Outlook Anywhere.
ff N
o, do not enable Analytics
If you do not want to enable Analytics, leave this list set to No, and continue with the next section.
ff Y
es, enable Analytics using AVR
If you choose to enable Analytics, select Yes from the list, and then answer the following questions.
a. U
se the default Analytics profile or select a custom profile?
If you decide to use AVR, you must decide whether to use the default Analytics profile, or create a new one. As mentioned
previously, we recommend creating a new profile to get the most flexibility and functionality out of AVR. If you have already
started the iApp template configuration and then decide to create a new Analytics profile, you must exit the iApp, create the
profile, and then restart the iApp template.
`` S
elect a custom Analytics profile
Select this option if you have already created a custom Analytics profile for Exchange Server.
i). W
hich Analytics profile do you want to use?
From the list, select the appropriate Analytics profile.
`` U
se default profile
Select this option if you have not yet created a custom Analytics profile for Microsoft Exchange. We do not
recommend using the default profile.
13
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
`` U
se a simple ICMP monitor for the Active Directory pool
Select this option if you only want a simple ICMP monitor for the Active Directory pool. This monitor sends a ping to
the servers and marks the server UP if the ping is successful.
Continue with the next section.
`` C
reate a new LDAP monitor for the Active Directory pool
Select this option if you want the template to create a new LDAP monitor for the Active Directory pool. You must
answer the following questions:
i). W
hich Active Directory user name should the monitor use?
Specify an Active Directory user name for the monitor to use when attempting to log on as a part of the health
check. This should be a user account created specifically for this health monitor, and must be set to never
expire.
ii). What is the associated password?
Specify the password associated with the Active Directory user name.
14
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
ff Encrypted
If you chose Encrypted in the previous question, additional questions appear.
a. Do you want to re-encrypt this traffic to your Client Access Servers?
If you are using Exchange 2010 or Exchange 2013 SP1 and later, and want the BIG-IP system to offload SSL processing
from the Client Access Servers, select Do not re-encrypt (SSL Offload) from the list. Offloading SSL on the BIG-IP
system can extend Exchange Server server capacity.
i Important
If you are deploying Exchange Server 2013 and have not installed SP1 or later, you must choose
Re-encrypt (SSL Bridging).
`` Do not re-encrypt (SSL Offload)
Select this option if you want to offload SSL processing onto the BIG-IP system. If you choose SSL Offload, you must
have followed the instructions described in the prerequisites for configuring the Exchange Server:
http://social.technet.microsoft.com/wiki/contents/articles/how-to-configure-ssl-offloading-in-exchange-2010.aspx.
i). W
hich Client SSL profile do you want to use?
The iApp can create a new Client SSL profile, or if you have created a Client SSL profile which contains the
appropriate SSL certificate and key for your Exchange implementation, you can select it from the list.
15
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
• Select the Client SSL profile you created from the list
If you manually created a Client SSL profile, select it from the list, and then continue with #2.
• Create a new Client SSL profile
Select this option if you want the iApp to create a new Client SSL profile.
1). W
hich SSL certificate do you want to use?
Select the SSL certificate you imported onto the BIG-IP system for decrypting client connections.
If you have not yet imported a certificate, you can leave the default selections and reconfigure this iApp
after obtaining the certificates. The deployment will not function correctly until you have selected the
correct certificates here.
Note
Any certificate that you obtain with multiple names must be in SAN (Subject
Alternative Name) format, not SNI (Server Name Indication) format. For more
information on SAN certificates, see Subject Alternative Name (SAN) SSL Certificates
on page 103.
2). W
hich SSL key do you want to use?
Select the associated key from the list.
If you have not yet imported a certificate, you can leave the default selections and reconfigure this
iApp after obtaining the certificates. The deployment will not function correctly until you have selected
the correct certificates here.
Note
Any certificate that you obtain with multiple names must be in SAN (Subject
Alternative Name) format, not SNI (Server Name Indication) format. For more
information on SAN certificates, see Subject Alternative Name (SAN) SSL Certificates
on page 103.
2). W
hich SSL key do you want to use?
Select the associated key from the list.
16
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
The default, F5 recommended Server SSL profile uses the serverssl parent profile. For information about
the ciphers used in the Server SSL profile, see
http://support.f5.com/kb/en-us/solutions/public/8000/800/sol8802.html.
ff Unencrypted
Select this option if Client Access traffic is arriving at this BIG-IP system unencrypted (typically because you configured to
offload SSL/TLS traffic at the BIG-IP APM that is sending Client Access traffic to this device).
a. D
o you want to encrypt the traffic to your Client Access Servers?
If you are using Exchange 2010 and want the BIG-IP system to offload SSL processing from the Client Access Servers,
select Do not re-encrypt (SSL Offload) from the list. Offloading SSL on the BIG-IP system can extend Exchange Server
2010 server capacity.
i Important
If you are deploying Exchange Server 2013, you must choose Encrypt (SSL Bridging).
2. W
ill clients be connecting to this BIG-IP virtual server primarily over a LAN or a WAN?
Select whether most clients are connecting over a WAN or LAN. The iApp uses your selection to configure the proper TCP
optimization settings.
ff WAN
Select this option if most Exchange server clients are coming into your Exchange environment over a Wide Area Network.
ff LAN
Select this option if most Exchange server clients are coming into your Exchange environment over a Local Area Network.
3. Where
will your BIG-IP virtual servers be in relation to your Client Access Servers?
Select whether your BIG-IP virtual servers are on the same subnet as your Client Access Servers, or on different subnets. This setting
is used to determine the SNAT (secure NAT) and routing configuration.
ff S
ame subnet for BIG-IP virtual servers and Client Access Servers
Select this option if the BIG-IP virtual servers and the Client Access Servers are on the same subnet. In this case SNAT is
configured on the BIG-IP virtual server and you must specify the number of concurrent connections.
a. What is the maximum number of concurrent users you expect per Client Access Server?
Select whether you expect more or fewer than 6,000 concurrent users to each Client Access Server. This answer is used
17
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
to determine what type of SNAT (secure network address translation) that system uses. A SNAT is an object that maps the
source client IP address in a request to a translation address defined on the BIG-IP device.
Note
For specific information on SNAT Pools, including why we chose 6,000 concurrent users per Client
Access Server, see Maximum number of concurrent users: SNAT Pool guidance on page 103.
`` F
ewer than 6000
Select this option if you expect fewer than 6,000 concurrent users per Client Access Server. With this option, the
system applies SNAT Auto Map, which doesn’t require any additional IP addresses, as the system uses an existing self
IP address for translation.
`` M
ore than 6000
Select this option if you expect more than 6,000 users at one time to each server. With this option, the iApp creates a
SNAT Pool, for which you need one IP address for each 6,000 users you expect.
i). W
hich IP addresses do you want to use for the SNAT pool?
Specify one otherwise unused IP address for every 6,000 concurrent connections, or fraction thereof. Click
Add for additional rows.
i Important
If you choose more than 6,000 users, but do not specify enough SNAT pool addresses, after
the maximum connection limit of 6,000 concurrent users per server is reached, new requests
fail.
ff D
ifferent subnet for BIG-IP virtual servers and Client Access Servers
If the BIG-IP virtual servers and Web Interface servers are on different subnets, the following question appears asking how
routing is configured.
a. H
ow have you configured routing on your Client Access Servers?
Select whether the Client Access Servers use this BIG-IP system’s Self IP address as their default gateway.
`` C
lient Access Servers do NOT use BIG-IP as their default gateway
Select this option if the Client Access Servers do not use the BIG-IP system as their default gateway. If the Client
Access Servers do not use the BIG-IP as their default gateway, SNAT is configured on the BIG-IP virtual server and
you must select the expected number of concurrent users in the next question.
i). What is the maximum number of concurrent users you expect per Client Access Server?
Select whether you expect more or fewer than 6,000 concurrent users to each Client Access Server. This
answer is used to determine what type of SNAT that system uses. A SNAT is an object that maps the source
client IP address in a request to a translation address defined on the BIG-IP device.
Note
For specific information on SNAT Pools, including why we chose 6,000 concurrent users per
Client Access Server, see Maximum number of concurrent users: SNAT Pool guidance on page
103.
• F
ewer than 6000
Select this option if you expect fewer than 6,000 concurrent users per Client Access Server. With this
option, the system applies SNAT Auto Map, which doesn’t require any additional IP addresses, as the
system uses an existing self IP address for translation.
• M
ore than 6000
Select this option if you expect more than 6,000 users at one time to each server. With this option, the
iApp creates a SNAT Pool, for which you need one IP address for each 6000 users you expect.
1). W
hich IP addresses do you want to use for the SNAT pool?
Specify one otherwise unused IP address for every 6000 concurrent connections, or fraction thereof.
Click Add for additional rows.
18
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
i Important
If you choose more than 6,000 users, but do not specify enough SNAT pool addresses,
after the maximum connection limit of 6,000 concurrent users per server is reached, new
requests fail.
4. Will you use a single IP address for all CAS connections, or will you have separate IP addresses?
Select whether you want to use a single IP address for all Client Access connections, or separate IP addresses for the different
services. If you chose a single IP address, the iApp creates a single virtual server for all of the Client Access services. If you choose
different addresses, the BIG-IP creates individual virtual servers for each service. There are advantages to each method:
ff S
ingle IP address
With a single IP address, you can combine multiple functions on the same virtual server; for instance, you may wish to have a
single fully-qualified domain name (FQDN) and associated SSL certificate for all HTTP-based Client Access methods. You only
need to provision a single IP address for the virtual server. If you want the services to have unique DNS names despite sharing
an IP address, you need to obtain an SSL certificate that supports Subject Alternative Names. For detailed information on SAN
certificates, see Subject Alternative Name (SAN) SSL Certificates on page 103.
ff D
ifferent IP addresses for different services
By maintaining a separate virtual server for each component, you can manage each service independently from one another.
For instance, you may wish to have different pool membership, load balancing methods, or custom monitors for Outlook
Web App and Outlook Anywhere. If each of those services are associated with a different virtual server, granular management
becomes easier. You need to provision an available IP address for each virtual server, and obtain a valid SSL certificate with a
unique subject name for each service.
5. H
ow are you distributing the CAS protocols between servers?
Select whether all your Client Access services are handled by the same Client Access Servers, or if each service is handled by a
unique set of Client Access Servers.
This iApp creates separate pools and monitors for each service regardless of this setting. However, if you use the same set of servers
for all services, you only have to specify the server IP addresses once.
ff A
ll services will be handled by the same set of Client Access Servers
Choose this option if you are using the same Client Access Servers for all of your Exchange Client Access services.
ff E
ach service will be handled by a unique set of Client Access Servers
Choose this option if you are using different sets of Client Access Servers for each Client Access service.
1. D
o you want to customize the server pool settings?
Select whether you want to customize the BIG-IP load balancing pools for Client Access services, or use the F5 recommended
settings.
ff U
se settings recommended by F5
If you don't have a specific reason to customize the pool settings, leave this question set to this setting and continue with #2.
ff C
ustomize pool settings
If you need to modify individual pool options, select Customize pool settings and answer the following options that appear:
19
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
a. W
hich load balancing method do you want to use?
Select the load balancing method you want to use. We recommend the default, Least Connections (member). See the
BIG-IP documentation for a description of each method. If you chose a node-based load balancing method, such as Ratio
(Node), and use a Ratio or Connection Limit (both optional), you must see Adding Ratio or Connection Limit information to
the nodes if using a node-based load balancing method on page 52 after completing the template.
b. Do you want to give priority to specific groups of servers?
Select whether you want to enable Priority Group Activation to send traffic first to groups of servers you specify. The BIG-IP
system load balances traffic according to the priority number you assign to each server.
`` Do not use Priority Group Activation
Select this option if you do not want to enable Priority Group Activation.
`` Use Priority Group Activation
Select this option if you want to enable Priority Group Activation. You will need to add a priority number in the Priority
box to each server . A higher number indicates higher priority. Traffic is only sent to the servers with the highest priority,
unless the number of available servers in that priority group falls below the value you specify as the minimum in the
following question. The BIG-IP system then sends traffic to the group of servers with the next highest priority, and so
on. See the BIG-IP documentation for more details.
i). What is the minimum number of active members in a group?
Specify the minimum number of servers that must be active to continue sending traffic to the priority group. If
the number of active servers falls below this minimum, traffic will be sent to the group of servers with the next
highest priority group number.
c. D
o you want the BIG-IP system to queue TCP requests?
Select whether you want the BIG-IP system to queue TCP requests. TCP request queuing provides the ability to
queue connection requests that exceed the capacity of connections for a pool, as determined by the connection limit.
Consequently, instead of dropping connection requests that exceed the capacity of a pool, TCP request queuing enables
those connection requests to reside within a queue according to defined conditions until capacity becomes available. For
more information on TCP Request Queuing, see the Preventing TCP Connection Requests From Being Dropped chapter in
the BIG-IP Local Traffic Manager: Implementations guide, available on AskF5.
i Important
TCP Request Queuing is an advanced feature and should be used only if you understand how it will
affect your deployment, including application behavior and BIG-IP performance.
If you enable TCP Request Queuing, you must have a Connection Limit set on at least one of the nodes
when configuring the Address/Port for the Client Access Server nodes.
20
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
3. D
o you want to add any iRules to this combined virtual server?
If you chose to customize pool settings, you have the option of adding existing iRules to the virtual server. iRules allow an
administrator to instruct the system to intercept, inspect, transform, direct and track inbound or outbound application traffic. For more
information on iRules, see https://devcentral.f5.com/HotTopics/iRules/tabid/1082202/Default.aspx.
i Important
Improper use or misconfiguration of an iRule can result in unwanted application behavior and poor performance
of your BIG-IP system. We recommended you verify the impact of an iRule prior to deployment in a production
environment.
If you want to add iRules, from the Options box, select the iRule(s) you want to include, and then click the Add (<<) button.
4. A
re you deploying Outlook Web App (includes ECP)?
Select whether you are deploying Outlook Web App at this time. This includes the Exchange Control Panel (ECP).
ff No
Select this option if you are not deploying OWA at this time. You can always reconfigure the template later to add OWA.
ff Yes
Select this option if you are deploying OWA at this time.
a. Do you want to restrict Exchange Administration Center access by IP address or network? Exchange 2013 only
This question only appears if you selected Exchange 2013 as your version of Exchange.
Select whether you want the BIG-IP LTM to restrict Exchange Administration Center (EAC) access by IP address or
network. In Microsoft Exchange Server 2013, Exchange administration is now performed via the EAC, a web-based
console. You configure the iApp to control access to the EAC, allowing connections only from approved IP addresses or
networks.
`` No, allow EAC access from all client IP addresses
Select this option to allow EAC access from all client IP addresses and networks. In this case, the system does not
restrict EAC access to specific IP addresses or networks, however, if you are deploying BIG-IP APM, you can still
restrict access to EAC by Organizational Management group in question b.
`` Yes, restrict EAC access to specific client IP addresses or networks
Select this option if you want to restrict EAC access to specific client IP addresses or networks. This adds an extra
layer of security to your Exchange deployment. The system creates a data group with the IP addresses or networks
you specify, and then uses an iRule to enforce the restrictions.
i). What IP or network addresses should be allowed EAC access?
Specify the IP addresses or networks should be allowed access to EAC. Click Add to include additional
addresses or networks.
i Important
If you are not deploying BIG-IP APM, the iApp currently does not attach the proper data group
and iRule. See Creating the Data Group and iRule for securing EAC access if not using BIG-IP
APM on page 57 for information on how to configure these objects.
b. S
hould BIG-IP APM restrict EAC access to members of the Exchange Organization Management Security Group?
Exchange 2013 only
This question only appears if you selected Exchange 2013 as your version of Exchange and selected to provide secure
authentication with BIG-IP APM.
Select whether you want the BIG-IP APM to restrict Exchange Administration Center (EAC) access to members of
Exchange 2013's Organizational Management group. The BIG-IP APM module queries Active Directory group membership
for the user making the request to EAC. If the user is not a member of the Organization Management group, the BIG-IP
APM policy denies access.
`` No, do not restrict EAC access by group membership
Select this option and the BIG-IP APM will not restrict access to the EAC by group membership.
21
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
c. What IP address do you want to use for the OWA virtual server?
This question only appears if you selected Different IP addresses for different services in the previous section.
Specify the IP address the system will use for the Outlook Web App virtual server. Clients will use this IP address to access
Outlook Web App.
d. D
o you want to add custom iRules to this virtual server?
This question only appears if you selected Different IP addresses for different services in the previous section.
If you chose to customize pool settings, you have the option of adding existing iRules to this OWA virtual server. iRules
allow an administrator to instruct the system to intercept, inspect, transform, direct and track inbound or outbound
application traffic. For more information on iRules, see
https://devcentral.f5.com/HotTopics/iRules/tabid/1082202/Default.aspx.
If you want to add iRules, from the Options box, select the iRule(s) you want to include, and then click the Add (<<) button.
Improper use or misconfiguration of an iRule can result in unwanted application behavior and poor performance of your
BIG-IP system. We recommended you verify the impact of an iRule prior to deployment in a production environment.
e. What are the IP addresses of your OWA servers?
This question only appears if you selected Each service will be handled by a unique set of Client Access Servers in
the previous section.
Specify the IP addresses of your Outlook Web App servers. Click Add to include additional servers. If you chose to have
the BIG-IP system queue TCP requests, you must specify a Connection Limit. If you chose to enable Priority Group
Activation, you must specify a Priority.
2. A
re you deploying Outlook Anywhere, EWS and OAB (or EWS only)?
Select whether you are deploying Outlook Anywhere, Exchange Web Services (EWS), and Offline Address Book (OAB), or EWS only
at this time.
ff No, not deploying Outlook Anywhere, EWS, or OAB
Select this option if you are not deploying Outlook Anywhere at this time. You can always reconfigure the template at another
time to add Outlook Anywhere to the configuration.
ff Yes, deploying EWS only
Select this option if you are only deploying Exchange Web Services at this time, and not Outlook Anywhere or Offline Address
Book. In this case, the BIG-IP system sends any Offline Address Book traffic to the Exchange Web Services pool.
a. What IP address do you want to use for the Exchange Web Services virtual server?
This question only appears if you selected Different IP addresses for different services in the previous section.
Specify the IP address the system will use for the Exchange Web Services virtual server.
b. D
o you want to add custom iRules to this virtual server?
This question only appears if you selected Different IP addresses for different services in the previous section.
If you chose to customize pool settings, you have the option of adding existing iRules to this Exchange Web Services virtual
server. iRules allow an administrator to instruct the system to intercept, inspect, transform, direct and track inbound or
outbound application traffic. For more information on iRules, see
https://devcentral.f5.com/HotTopics/iRules/tabid/1082202/Default.aspx.
If you want to add iRules, from the Options box, select the iRule(s) you want to include, and then click the Add (<<) button.
Improper use or misconfiguration of an iRule can result in unwanted application behavior and poor performance of your
BIG-IP system. We recommended you verify the impact of an iRule prior to deployment in a production environment.
c. What are the IP addresses of your EWS servers?
This question only appears if you selected Each service will be handled by a unique set of Client Access Servers in
the previous section.
22
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Specify the IP addresses of your Exchange Web Services servers. Click Add to include additional servers. If you chose to
have the BIG-IP system queue TCP requests, you must specify a Connection Limit. If you chose to enable Priority Group
Activation, you must specify a Priority.
i Important
In Microsoft Exchange 2010, you must enable Outlook Anywhere on each of your Exchange Client Access
Servers before that service will be available. Outlook Anywhere is not enabled by default on Exchange Client
Access Servers. See the Microsoft documentation for specific instructions.
To prevent internal users from receiving a password prompt, your internal DNS must not have an 'A' record for the
FQDN for Outlook Anywhere.
a. What IP address do you want to use for the Outlook Anywhere virtual server?
This question only appears if you selected Different IP addresses for different services in the previous section.
Specify the IP address the system will use for the Outlook Anywhere virtual server.
b. D
o you want to add custom iRules to this virtual server?
This question only appears if you selected Different IP addresses for different services in the previous section.
If you chose to customize pool settings, you have the option of adding existing iRules to this Outlook Anywhere virtual
server. iRules allow an administrator to instruct the system to intercept, inspect, transform, direct and track inbound or
outbound application traffic. For more information on iRules, see
https://devcentral.f5.com/HotTopics/iRules/tabid/1082202/Default.aspx.
If you want to add iRules, from the Options box, select the iRule(s) you want to include, and then click the Add (<<) button.
Improper use or misconfiguration of an iRule can result in unwanted application behavior and poor performance of your
BIG-IP system. We recommended you verify the impact of an iRule prior to deployment in a production environment.
c. What are the IP addresses of your Outlook Anywhere servers?
This question only appears if you selected Each service will be handled by a unique set of Client Access Servers in
the previous section.
Specify the IP addresses of your Outlook Anywhere servers. Click Add to include additional servers. If you chose to
have the BIG-IP system queue TCP requests, you must specify a Connection Limit. If you chose to enable Priority Group
Activation, you must specify a Priority.
i Important
Before completing this section, you must create a user account in the same domain that has been
properly configured for Kerberos delegation. You must create an NTLM Machine Account object
on the BIG-IP system to join this system to the Active Directory domain. See Creating an NTLM
Machine Account on page 61.
23
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
i). Which NTLM machine account should be used for Kerberos delegation?
Select the NTLM Machine Account you created to join the BIG-IP system to the Active Directory domain. If you
have not already created an NTLM Machine Account on the BIG-IP system, see Creating an NTLM Machine
Account on page 61. You must either exit the template now and start over once you have created the NTLM
Machine Account, or choose Outlook Anywhere Clients use Basic Authentication from the previous question,
and then re-enter the template at a later time.
ii). What is the Kerberos Key Distribution Center IP or FQDN?
Specify the IP address or fully qualified domain name of the Kerberos Key Distribution Center (KDC). If you type
an FQDN, the BIG-IP system must be able to resolve the address. Otherwise, use the IP address.
iii). What is the name of the Kerberos Realm?
Specify the name of the Kerberos Realm. While this name should be in all capital letters, the iApp automatically
turns any lower case letters to capital.
iv). What is the user name for the Active Directory delegation account you created?
Specify the user name for the Active Directory delegation account you created. This account must be correctly
configured in Active Directory for Kerberos delegation. See Appendix E: Active Directory and Exchange Server
configuration for NTLM on page 105 details.
v). What is the associated password?
Specify the password associated with the account.
vi). How do you want to construct the Kerberos ticket request?
Select whether you want to use DNS reverse lookups or the Outlook Anywhere Host header to construct the
ticket request.
• Use DNS reverse lookups
Select this option to use DNS reverse lookups to build the Kerberos ticket request. Note that you must
configure a reverse lookup zone containing a PTR record for each Client Access Server on a DNS server
that is accessible from this BIG-IP system. Consult your DNS documentation for specific instructions.
• Use the Outlook Anywhere host header
Select this option to use the Outlook Anywhere Host header to construct the ticket request. To use the
host header value, you must configure IIS Application Pools for Outlook Anywhere, Autodiscover, and
Exchange Web Services to run using the previously created Active Directory user account for Kerberos
delegation. See Appendix E: Active Directory and Exchange Server configuration for NTLM on page 105.
6. A
re you deploying ActiveSync?
Select whether you are deploying ActiveSync at this time.
ff No
Select this option if you are not deploying ActiveSync at this time. You can always reconfigure the template at another time to
add ActiveSync to the configuration.
ff Yes
Select this option if you are deploying ActiveSync at this time. See iPhones and other iOS devices are displaying invalid
certificate messages after deploying the iApp for ActiveSync on page 58 for important information.
a. What IP address do you want to use for the ActiveSync virtual server?
This question only appears if you selected Different IP addresses for different services in the previous section.
Specify the IP address the system will use for the ActiveSync virtual server. Be sure to see ActiveSync and/or Autodiscover
aren't working after deploying the iApp for separate virtual servers and using APM on page 55
b. D
o you want to add custom iRules to this virtual server?
This question only appears if you selected Different IP addresses for different services in the previous section.
If you chose to customize pool settings, you have the option of adding existing iRules to this ActiveSync virtual server.
iRules allow an administrator to instruct the system to intercept, inspect, transform, direct and track inbound or outbound
application traffic. For information on iRules, see https://devcentral.f5.com/HotTopics/iRules/tabid/1082202/Default.aspx.
If you want to add iRules, from the Options box, select the iRule(s) you want to include, and then click the Add (<<) button.
Improper use or misconfiguration of an iRule can result in unwanted application behavior and poor performance of your
BIG-IP system. We recommended you verify the impact of an iRule prior to deployment in a production environment.
24
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
7. A
re you deploying Autodiscover?
Select whether you are deploying Autodiscover at this time.
ff No
Select this option if you are not deploying Autodiscover at this time. You can always reconfigure the template at another time to
add Autodiscover to the configuration.
ff Yes
Select this option if you are deploying Autodiscover at this time.
! Warning
To deploy Autodiscover, you must either create an 'SRV' record in DNS or create 'A' records in order for
external clients to be able to make use of Autodiscover. If you do not want to use an 'SRV' record, then you
must have 'A' records for either 'autodiscover.<yourdomain>' or '<yourdomain>' that resolve to the IP address
you have designated for your Autodiscover virtual server.
a. What IP address do you want to use for the Autodiscover virtual server?
This question only appears if you selected Different IP addresses for different services in the previous section.
Specify the IP address the system will use for the Autodiscover virtual server. Be sure to see ActiveSync and/or
Autodiscover aren't working after deploying the iApp for separate virtual servers and using APM on page 55.
b. D
o you want to add custom iRules to this virtual server?
This question only appears if you selected Different IP addresses for different services in the previous section.
If you chose to customize pool settings, you have the option of adding existing iRules to this Autodiscover virtual server.
iRules allow an administrator to instruct the system to intercept, inspect, transform, direct and track inbound or outbound
application traffic. For iRule information, see https://devcentral.f5.com/HotTopics/iRules/tabid/1082202/Default.aspx.
If you want to add iRules, from the Options box, select the iRule(s) you want to include, and then click the Add (<<) button.
Improper use or misconfiguration of an iRule can result in unwanted application behavior and poor performance of your
BIG-IP system. We recommended you verify the impact of an iRule prior to deployment in a production environment.
c. What are the IP addresses of your Autodiscover servers?
This question only appears if you selected Each service will be handled by a unique set of Client Access Servers in
the previous section.
Specify the IP addresses of your Autodiscover servers. Click Add to include additional servers. If you chose to have the
BIG-IP system queue TCP requests, you must specify a Connection Limit. If you chose to enable Priority Group Activation,
you must specify a Priority.
8. A
re you deploying RPC Client Access (MAPI)? Exchange 2010 only
This question does not appear if you are deploying the template for Exchange 2013. Exchange Server 2013 Client Access Servers do
not offer MAPI as a connection option.
Select whether you are deploying RPC Client Access (MAPI) for your Exchange 2010 deployment at this time.
ff No
Select this option if you are not deploying RPC Client Access at this time. You can always reconfigure the template at another
time to add it to the configuration.
ff Yes
Select this option if you are deploying RPC Client Access at this time.
25
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
! Warning
You must enable and configure a Client Access Array in your Exchange Server site before RPC Client Access will
function. See Creating a new Client Access Array on page 104 for more information.
If deploying RPC Client Access, you must also deploy Outlook Anywhere, to properly handle EWS (Exchange
Web Services) traffic.
a. U
se the default dynamic range of ports for RPC Client Access traffic or set static ports?
Select whether you want to use the default dynamic range of ports for RPC Client Access, or if you have configured your
Client Access servers to use specific ports outside the default range.
`` Use the default dynamic port range
Select this option to configure the iApp to use the default port range. If you choose the default dynamic range of ports,
no additional information is necessary, continue with the next question.
`` Set static ports
Select this option if you want to set static ports for RPC Client Access.
i Important
You must make sure each of your Client Access Servers is configured to use the static ports you
specified here. See http://social.technet.microsoft.com/wiki/contents/articles/configure-static-rpc-
ports-on-an-exchange-2010-client-access-server.aspx for more information.
b. What IP address do you want to use for the RPC Client Access virtual server?
This question only appears if you selected Different IP addresses for different services in the previous section.
Specify the IP address the system will use for the RPC Client Access virtual server.
c. What are the IP addresses of your RPC Client Access servers?
This question only appears if you selected Each service will be handled by a unique set of Client Access Servers in
the previous section.
Specify the IP addresses of your RPC Client Access servers. Click Add to include additional servers. If you chose to
have the BIG-IP system queue TCP requests, you must specify a Connection Limit. If you chose to enable Priority Group
Activation, you must specify a Priority.
9. A
re you deploying POP3?
Select whether you are deploying POP3 at this time.
ff No
Select this option if you are not deploying POP3 at this time. You can always reconfigure the template at another time to add
POP3 to the configuration.
ff Yes
Select this option if you are deploying POP3 at this time.
i Important
You must enable POP3 on each of your Exchange Client Access Servers before that service will be
available. POP3 is not enabled by default on Exchange Client Access Servers.
If you are offloading SSL, you must configure the Authentication properties for POP3 on each of your
Exchange Client Access Servers to allow logins using plain text. By default, POP3 is configured to only allow
secure (encrypted) logins.
26
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
a. What IP address do you want to use for the POP3 virtual server?
This question only appears if you selected Different IP addresses for different services in the previous section.
Specify the IP address the system will use for the POP3 virtual server.
b. What are the IP addresses of your POP3 servers?
This question only appears if you selected Each service will be handled by a unique set of Client Access
Servers in the previous section.
Specify the IP addresses of your POP3 servers. Click Add to include additional servers. If you chose to have the BIG-
IP system queue TCP requests, you must specify a Connection Limit. If you chose to enable Priority Group Activation,
you must specify a Priority.
10. A
re you deploying IMAP4?
Select whether you are deploying IMAP4 at this time.
ff No
Select this option if you are not deploying IMAP4 at this time. You can always reconfigure the template at another time to
add IMAP4 to the configuration.
ff Yes
Select this option if you are deploying IMAP4 at this time.
i Important
You must enable IMAP4 on each of your Exchange Client Access Servers before that service will be
available. IMAP4 is not enabled by default on Exchange Client Access Servers.
If you are offloading SSL, you must configure the Authentication properties for IMAP4 on each of your
Exchange Client Access Servers to allow logins using plain text. By default, IMAP4 is configured to only
allow secure (encrypted) logins.
c. What IP address do you want to use for the IMAP4 virtual server?
This question only appears if you selected Different IP addresses for different services in the previous section.
Specify the IP address the system will use for the IMAP4 virtual server.
d. What are the IP addresses of your IMAP4 servers?
This question only appears if you selected Each service will be handled by a unique set of Client Access
Servers in the previous section.
Specify the IP addresses of your IMAP4 servers. Click Add to include additional servers. If you chose to have the
BIG-IP system queue TCP requests, you must specify a Connection Limit. If you chose to enable Priority Group
Activation, you must specify a Priority.
1. D
o you want to use advanced or simple server health monitors?
Choose whether you want to use advanced or simple health monitors to check the availability of the Client Access Servers:
27
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
ff U
se simple monitors
Simple monitors check network connectivity but do not perform actual logins. If you use simple monitors, the BIG-IP LTM may
not be able to completely determine status of Client Access services. In this case, the monitor interval is set to 10 seconds
automatically, no matter what number is in the previous question.
ff U
se advanced monitors
If you choose advanced monitors, the BIG-IP system performs logins to most of the Client Access services (all except RPC/
MAPI in Exchange 2010 and Forms-based Outlook Web App) and checks for valid content in the response. Because these
monitors attempt to access a specific mailbox, they can more accurately determine the actual health of Client Access services.
However, account maintenance and Mailbox status must become a part of your monitoring strategy. For example, if an account
used for monitoring is locked or deleted, the monitor will mark the services down for all users.
i Important
5’s advanced monitors for Autodiscover, Exchange Web Services, and Outlook Anywhere support Basic and
F
NTLMv1 authentication only. See Advanced monitors for Autodiscover, EWS, and Outlook Anywhere only support
Basic and NTLMv1 authentication on page 56 for more information.
We strongly recommend creating a mailbox account(s) specifically for use in the monitor(s). The accounts for those mailboxes
should have no other privileges in the domain and should be configured with passwords that do not expire.
a. W
hat email address do you want to use for the advanced monitors?
This question only appears if you specified you are deploying Autodiscover and/or Exchange Web Services .
Type the email address associated with the account you are going to monitor (and that you specify in the following
question).
b. W
hich mailbox account should be used for the monitors?
Type a mailbox account for use in the advanced monitors. This name corresponds to the account name field in Active
Directory (rather than the email address).
c. What is the password for that mailbox account?
Type the associated password.
d. W
hat is the domain name of the user account for the monitors?
Type the Domain name for the user account. This domain can be entered in either FQDN (mydomain.example.com) or
NetBIOS (MYDOMAIN) format.
e. D
o you want to monitor a second mailbox?
Choose whether you want to monitor a second mailbox. We strongly recommend configuring a second mailbox account to
be used by a second set of monitors, using a mailbox that is configured to reside on a different Mailbox server. The BIG-IP
LTM will only mark a Client Access service on a specific server down if both sets of credentials fail. This provides resiliency
to accommodate configuration errors with a single account, mailbox, or Mailbox server.
`` Monitor only one mailbox
Select this option if you do not want the BIG-IP system to monitor a second mailbox. Continue with #3.
`` Monitor a second mailbox (recommended)
Select this option if you want the BIG-IP system to monitor a second mailbox. You must answer the following:
i). Which email address do you want to use for the second advanced monitor?
This question only appears if you specified you are deploying Autodiscover and/or Exchange Web Services .
Type the email address associated with the account you are going to monitor (and that you specify in the
following question).
ii). Which mailbox account should be used for the second monitor?
Type a mailbox account for use in the second monitors. Again, this name corresponds to the account name
field in Active Directory (rather than the email address).
iii). What is the password for that mailbox account?
Type the associated password.
28
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
iv). What is the domain name of the user account for the second monitors?
Type the Domain name for the second user account. This domain can be entered in either FQDN (mydomain.
example.com) or NetBIOS (MYDOMAIN) format.
i Important
If you are using APM in this scenario, you must choose Forms-Based. If you are using Forms-Based
authentication for OWA, you must change the credential format required for OWA on each Exchange Client
Access Server from the default domain\username format to just username.
ff O
WA uses the default Forms-Based authentication
Select this option if you are using Forms-based authentication.
If you chose Forms-based authentication, the BIG-IP system does not perform an actual login to the service, but checks the
availability of the forms-based authentication page.
ff O
WA uses Basic or Windows Integrated authentication
Select this option if you are using Basic/Windows Integrated authentication.
3. H
ow many seconds should pass between health checks?
Specifies how often the system checks the health of the servers. We recommend the default of 30 seconds. The maximum value for
the interval is 28,799 seconds.
4. A
re you using the same FQDN for all HTTP-based services?
This question only appears if you specified you are using a single IP address for all CAS connections. If you selected Different IP
addresses for different services, continue with #5.
Select whether you are using one FQDN for all HTTP-based services or separate FQDNs for each service. These values are used for
HTTP 1.1-based health monitors.
ff O
ne FQDN for all HTTP services
Select this option if you are using a single FQDN for all HTTP-based Client Access services.
a. What is the FQDN that you use for your HTTP-based services?
Specify the fully qualified domain name you are using for all of the HTTP-based CAS services.
ff D
ifferent FQDNs for each HTTP service
Select this option if you are using separate FQDNs for each HTTP-based CAS service. Additional questions appear. When you
are finished adding the FQDNs, continue with Additional Steps.
a. What FQDN do you use for the OWA service?
This question only appears if you specified you are deploying Outlook Web App.
Specify the fully qualified domain name you use for your Outlook Web App service.
b. What FQDN do you use for the Outlook Anywhere service?
This question only appears if you specified you are deploying Outlook Anywhere.
Specify the fully qualified domain name you use for your Outlook Anywhere service.
c. What FQDN do you use for the ActiveSync service?
This question only appears if you specified you are deploying ActiveSync.
Specify the fully qualified domain name you use for your ActiveSync service.
29
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Additional Steps
Review the information in the Additional steps section, and take appropriate action if necessary. All of the notes in Additional Steps are
found in the relevant section of this deployment guide.
Finished
Review your answers to the questions. When you are satisfied, click the Finished button. The BIG-IP system creates the relevant objects.
Continue with Next steps on page 51.
30
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Configuring the LTM to receive HTTP-based Client Access traffic forwarded by a BIG-IP APM
If you chose the second scenario, LTM will receive HTTP-based CAS traffic forwarded by a BIG-IP APM, use this section for guidance on
configuring the iApp. This selection configures BIG-IP LTM with a single virtual server that receives Exchange Client Access HTTP-based
traffic that has been forwarded by a separate BIG-IP APM. The BIG-IP system can also accommodate non-HTTP traffic that is not handled
by BIG-IP APM such as POP3 and IMAP4.
While this virtual server can be used for direct traffic (for example, internal clients that do not use the BIG-IP APM), we do not recommend
using this virtual server in that way. For direct traffic, we strongly recommend creating a second instance of the iApp on this BIG-IP LTM for
the direct traffic/internal users. You must use a unique virtual server IP address, all of the other settings can be identical. Once both iApps
have been created, you would configure Split DNS (use the same domain name, but different zones and IP addresses for internal and
external clients). For more information about Split DNS, refer to your DNS documentation.
Analytics
This section of the template asks questions about Analytics. The Application Visibility Reporting (AVR) module allows you to view statistics
specific to your Microsoft Exchange implementation. AVR is available on all BIG-IP systems v11 and later, however you must have the AVR
provisioned for this option to appear. Note that this is only for application visibility reporting, you can view object-level statistics from the
BIG-IP without provisioning AVR.
i Important
Enabling Analytics may adversely affect overall system performance. If you choose to enable Analytics, we recommend
gathering statistics for a set time period, such as one week, and then re-entering this template and disabling Analytics
while you process the data.
If you plan on using AVR for analytics, we recommend creating a custom Analytics profile. To create a new profile, from the Main tab, select
Profiles and then click Analytics. Click New and then configure the profile as applicable for your configuration. See the online help or
product documentation for specific instructions. To select the new profile, you need to restart or reconfigure the iApp template.
1. Do
you want to enable Analytics for application statistics?
Choose whether you want to enable AVR for Analytics.
ff N
o, do not enable Analytics
If you do not want to enable Analytics, leave this list set to No, and continue with the next section.
ff Y
es, enable Analytics using AVR
If you choose to enable Analytics, select Yes from the list, and then answer the following questions.
a. U
se the default Analytics profile or select a custom profile?
If you decide to use AVR, you must decide whether to use the default Analytics profile, or create a new one. As mentioned
previously, we recommend creating a new profile to get the most flexibility and functionality out of AVR. If you have already
started the iApp template configuration and then decide to create a new Analytics profile, you must exit the iApp, create the
profile, and then restart the iApp template.
`` S
elect a custom Analytics profile
Select this option if you have already created a custom Analytics profile for Exchange Server.
i). W
hich Analytics profile do you want to use?
From the list, select the appropriate Analytics profile.
`` U
se default profile
Select this option if you have not yet created a custom Analytics profile for Microsoft Exchange. We do not recommend
using the default profile.
31
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
ff Encrypted
If you chose Encrypted in the previous question, additional questions appear.
a. Do you want to re-encrypt this traffic to your Client Access Servers?
If you are using Exchange 2010 or Exchange 2013 SP1 and later, and want the BIG-IP system to offload SSL processing
from the Client Access Servers, select Do not re-encrypt (SSL Offload) from the list. Offloading SSL on the BIG-IP
system can extend Exchange Server server capacity.
i Important
If you are deploying Exchange Server 2013 and have not installed SP1 or later, you must choose
Re-encrypt (SSL Bridging).
If you have not yet imported a certificate, you can leave the default selections and reconfigure this iApp
after obtaining the certificates. The deployment will not function correctly until you have selected the
correct certificates here.
Note
Any certificate that you obtain with multiple names must be in SAN (Subject
Alternative Name) format, not SNI (Server Name Indication) format. For more
information on SAN certificates, see Subject Alternative Name (SAN) SSL Certificates
on page 103.
2). W
hich SSL key do you want to use?
Select the associated key from the list.
32
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
• Select the Client SSL profile you created from the list
If you manually created a Client SSL profile, select it from the list, and then continue with #2.
• Create a new Client SSL profile
Select this option if you want the iApp to create a new Client SSL profile.
1). W
hich SSL certificate do you want to use?
Select the SSL certificate you imported onto the BIG-IP system for decrypting client connections.
If you have not yet imported a certificate, you can leave the default selections and reconfigure this
iApp after obtaining the certificates. The deployment will not function correctly until you have selected
the correct certificates here.
Note
Any certificate that you obtain with multiple names must be in SAN (Subject
Alternative Name) format, not SNI (Server Name Indication) format. For more
information on SAN certificates, see Subject Alternative Name (SAN) SSL Certificates
on page 103.
2). W
hich SSL key do you want to use?
Select the associated key from the list.
ff Unencrypted
Select this option if Client Access traffic is arriving at this BIG-IP system unencrypted (typically because you configured to
offload SSL/TLS traffic at the BIG-IP APM that is sending Client Access traffic to this device).
a. D
o you want to encrypt the traffic to your Client Access Servers?
If you are using Exchange 2010 or Exchange 2013 SP1 and later, and want the BIG-IP system to offload SSL processing
from the Client Access Servers, select Do not re-encrypt (SSL Offload) from the list. Offloading SSL on the BIG-IP
system can extend Exchange Server server capacity.
i Important
If you are deploying Exchange Server 2013 and have not installed SP1 or later, you must choose
Re-encrypt (SSL Bridging).
33
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
• Select the Server SSL profile you created from the list
If you have previously created a Server SSL profile for your Exchange implementation, from the list, select
the existing Server SSL profile you created.
• Create a new Server SSL profile
Select this option if you want the iApp to create a new Server SSL profile.
The default, F5 recommended Server SSL profile uses the serverssl parent profile. For information about
the ciphers used in the Server SSL profile, see
http://support.f5.com/kb/en-us/solutions/public/8000/800/sol8802.html.
2. Where
will your BIG-IP virtual servers be in relation to your Client Access Servers?
Select whether your BIG-IP virtual servers are on the same subnet as your Client Access Servers, or on different subnets. This setting
is used to determine the SNAT (secure NAT) and routing configuration.
ff S
ame subnet for BIG-IP virtual servers and Client Access Servers
Select this option if the BIG-IP virtual servers and the Client Access Servers are on the same subnet. In this case SNAT is
configured on the BIG-IP virtual server and you must specify the number of concurrent connections.
a. What is the maximum number of concurrent users you expect per Client Access Server?
Select whether you expect more or fewer than 6,000 concurrent users to each Client Access Server. This answer is used
to determine what type of SNAT that system uses. A SNAT is an object that maps the source client IP address in a request
to a translation address defined on the BIG-IP device.
Note
For specific information on SNAT Pools, including why we chose 6,000 concurrent users per Client
Access Server, see Maximum number of concurrent users: SNAT Pool guidance on page 103.
`` F
ewer than 6000
Select this option if you expect fewer than 6000 concurrent users per Client Access Server. With this option, the
system applies SNAT Auto Map, which doesn’t require any additional IP addresses, as the system uses an existing self
IP address for translation.
`` M
ore than 6000
Select this option if you expect more than 6000 users at one time to each server. With this option, the iApp creates a
SNAT Pool, for which you need one IP address for each 6000 users you expect.
i). W
hich IP addresses do you want to use for the SNAT pool?
Specify one otherwise unused IP address for every 6000 concurrent connections, or fraction thereof. Click Add
for additional rows.
i Important
If you choose more than 6000 users, but do not specify enough SNAT pool addresses, after the
maximum connection limit of 6000 concurrent users per server is reached, new requests fail.
ff D
ifferent subnet for BIG-IP virtual servers and Client Access Servers
If the BIG-IP virtual servers and Web Interface servers are on different subnets, the following question appears asking how
routing is configured.
a. H
ow have you configured routing on your Client Access Servers?
Select whether the Client Access Servers use this BIG-IP system’s Self IP address as their default gateway.
`` C
lient Access Servers do NOT use BIG-IP as their default gateway
Select this option if the Client Access Servers do not use the BIG-IP system as their default gateway. If the Client
Access Servers do not use the BIG-IP as their default gateway, SNAT is configured on the BIG-IP virtual server and
you must select the expected number of concurrent users in the next question.
i). What is the maximum number of concurrent users you expect per Client Access Server?
Select whether you expect more or fewer than 6,000 concurrent users to each Client Access Server. This
34
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
answer is used to determine what type of SNAT that system uses. A SNAT is an object that maps the source
client IP address in a request to a translation address defined on the BIG-IP device.
Note
For specific information on SNAT Pools, including why we chose 6,000 concurrent users per
Client Access Server, see Maximum number of concurrent users: SNAT Pool guidance on page
103.
• F
ewer than 6000
Select this option if you expect fewer than 6000 concurrent users per Client Access Server. With this
option, the system applies SNAT Auto Map, which doesn’t require any additional IP addresses, as the
system uses an existing self IP address for translation.
• M
ore than 6000
Select this option if you expect more than 6000 users at one time to each server. With this option, the iApp
creates a SNAT Pool, for which you need one IP address for each 6000 users you expect.
1). W
hich IP addresses do you want to use for the SNAT pool?
Specify one otherwise unused IP address for every 6000 concurrent connections, or fraction thereof.
Click Add for additional rows.
i Important
If you choose more than 6000 users, but do not specify enough SNAT pool addresses,
after the maximum connection limit of 6000 concurrent users per server is reached, new
requests fail.
1. W
ould you like to customize the server pool settings?
Select whether you want to customize the BIG-IP load balancing pools for Client Access services, or use the F5 recommended
settings.
ff U
se settings recommended by F5
If you don't have a specific reason to customize the pool settings, leave this question at Use settings recommended by F5 and
continue with #2.
ff C
ustomize pool settings
If you have need to modify individual pool options, select Customize pool settings and answer the following options:
35
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
a. W
hich load balancing method do you want to use?
Select the load balancing method you want to use. We recommend the default, Least Connections (member). See the
BIG-IP documentation for a description of each method. If you chose a node-based load balancing method (such as Ratio
(node)), and use a Ratio or Connection Limit (both optional), you must see Adding Ratio or Connection Limit information to
the nodes if using a node-based load balancing method on page 52 after completing the template.
b. Do you want to give priority to specific groups of servers?
Select whether you want to enable Priority Group Activation to send traffic first to groups of servers you specify. The BIG-IP
system load balances traffic according to the priority number you assign to each server.
`` Do not use Priority Group Activation
Select this option if you do not want to enable Priority Group Activation.
`` Use Priority Group Activation
Select this option if you want to enable Priority Group Activation. You will need to add a priority number in the Priority
box to each server . A higher number indicates higher priority. Traffic is only sent to the servers with the highest priority,
unless the number of available servers in that priority group falls below the value you specify as the minimum in the
following question. The BIG-IP system then sends traffic to the group of servers with the next highest priority, and so
on. See the BIG-IP documentation for more details.
i). What is the minimum number of active members in a group?
Specify the minimum number of servers that must be active to continue sending traffic to the priority group. If
the number of active servers falls below this minimum, traffic will be sent to the group of servers with the next-
highest priority group number.
c. D
o you want the BIG-IP system to queue TCP requests?
Select whether you want the BIG-IP system to queue TCP requests. TCP request queuing provides the ability to
queue connection requests that exceed the capacity of connections for a pool, as determined by the connection limit.
Consequently, instead of dropping connection requests that exceed the capacity of a pool, TCP request queuing enables
those connection requests to reside within a queue according to defined conditions until capacity becomes available. For
more information on TCP Request Queuing, see the Preventing TCP Connection Requests From Being Dropped chapter in
the BIG-IP Local Traffic Manager: Implementations guide, available on AskF5.
i Important
TCP Request Queuing is an advanced feature and should be used only if you understand how it will
affect your deployment, including application behavior and BIG-IP performance.
If you enable TCP Request Queuing, you must have a Connection Limit set on at least one of the nodes
when configuring the Address/Port for the Client Access Server nodes.
3. D
o you want to add any iRules to this combined virtual server?
If you chose to customize pool settings, you have the option of adding existing iRules to the virtual server. iRules allow an
36
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
administrator to instruct the system to intercept, inspect, transform, direct and track inbound or outbound application traffic. For more
information on iRules, see https://devcentral.f5.com/HotTopics/iRules/tabid/1082202/Default.aspx.
i Important
Improper use or misconfiguration of an iRule can result in unwanted application behavior and poor performance
of your BIG-IP system. We recommended you verify the impact of an iRule prior to deployment in a production
environment.
If you want to add iRules, from the Options box, select the iRule(s) you want to include, and then click the Add (<<) button.
4. A
re you deploying Outlook Web App (includes ECP)?
Select whether you are deploying Outlook Web App at this time. This includes the Exchange Control Panel (ECP).
ff No
Select this option if you are not deploying OWA at this time. You can reconfigure the template at another time to add OWA.
ff Yes
Select this option if you are deploying Outlook Web Access at this time.
a. What are the IP addresses of your OWA servers?
This question only appears if you selected Each service will be handled by a unique set of Client Access Servers in
the previous section.
Specify the IP addresses of your Outlook Web App servers. Click Add to include additional servers. If you chose to have
the BIG-IP system queue TCP requests, you must specify a Connection Limit. If you chose to enable Priority Group
Activation, you must specify a Priority.
5. A
re you deploying Outlook Anywhere, EWS and OAB (or EWS only)?
Select whether you are deploying Outlook Anywhere, Exchange Web Services (EWS), Offline Address Book (OAB), or EWS only.
ff No, not deploying Outlook Anywhere, EWS, or OAB
Select this option if you are not deploying Outlook Anywhere at this time. You can always reconfigure the template at another
time to add Outlook Anywhere to the configuration.
ff Yes, deploying EWS only
Select this option if you are only deploying Exchange Web Services at this time, and not Outlook Anywhere or Offline Address
Book. In this case, the BIG-IP system sends any Offline Address Book traffic to the Exchange Web Services pool.
a. What are the IP addresses of your EWS servers?
This question only appears if you selected Each service will be handled by a unique set of Client Access Servers in
the previous section.
Specify the IP addresses of your Exchange Web Services servers. Click Add to include additional servers. If you chose to
have the BIG-IP system queue TCP requests, you must specify a Connection Limit. If you chose to enable Priority Group
Activation, you must specify a Priority.
i Important
You must enable Outlook Anywhere on each of your Exchange Client Access Servers before that service
will be available. Outlook Anywhere is not enabled by default on Exchange Client Access Servers. See the
Microsoft documentation for specific instructions.
To prevent internal users from receiving a password prompt, your internal DNS must not have an 'A' record
for the FQDN for Outlook Anywhere.
a. What are the IP addresses of your Outlook Anywhere servers?
This question only appears if you selected Each service will be handled by a unique set of Client Access Servers in
the previous section.
37
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Specify the IP addresses of your Outlook Anywhere servers. Click Add to include additional servers. If you chose to
have the BIG-IP system queue TCP requests, you must specify a Connection Limit. If you chose to enable Priority Group
Activation, you must specify a Priority.
6. A
re you deploying ActiveSync?
Select whether you are deploying ActiveSync at this time.
ff No
Select this option if you are not deploying ActiveSync at this time. You can always reconfigure the template at another time to
add ActiveSync to the configuration.
ff Yes
Select this option if you are deploying ActiveSync at this time. Be sure to see ActiveSync and/or Autodiscover aren't working
after deploying the iApp for separate virtual servers and using APM on page 55, and iPhones and other iOS devices are
displaying invalid certificate messages after deploying the iApp for ActiveSync on page 58 for important information.
a. What are the IP addresses of your ActiveSync servers?
This question only appears if you selected Each service will be handled by a unique set of Client Access Servers in
the previous section.
Specify the IP addresses of your Outlook Anywhere servers. Click Add to include additional servers. If you chose to
have the BIG-IP system queue TCP requests, you must specify a Connection Limit. If you chose to enable Priority Group
Activation, you must specify a Priority.
7. A
re you deploying Autodiscover?
Select whether you are deploying Autodiscover at this time.
ff No
Select this option if you are not deploying Autodiscover at this time. You can always reconfigure the template at another time to
add Autodiscover to the configuration.
ff Yes
Select this option if you are deploying Autodiscover at this time. Be sure to see ActiveSync and/or Autodiscover aren't working
after deploying the iApp for separate virtual servers and using APM on page 55.
! Warning
To deploy Autodiscover, you must either create an 'SRV' record in DNS or create 'A' records in order for
external clients to be able to make use of Autodiscover. If you do not want to use an 'SRV' record, then
you must have 'A' records for either 'autodiscover.<yourdomain>' or '<yourdomain>' that resolve to the IP
address you have designated for your Autodiscover virtual server.
8. A
re you deploying RPC Client Access (MAPI)? Exchange 2010 only
This question does not appear if you are deploying the template for Exchange 2013. Exchange Server 2013 Client Access Servers do
not offer MAPI as a connection option.
Select whether you are deploying RPC Client Access (MAPI) for your Exchange 2010 deployment at this time.
ff No
Select this option if you are not deploying RPC Client Access at this time. You can always reconfigure the template at another
time to add it to the configuration.
ff Yes
Select this option if you are deploying RPC Client Access at this time.
38
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
! Warning
You must enable and configure a Client Access Array in your Exchange Server site before RPC Client Access will
function. See Creating a new Client Access Array on page 104 for more information.
If deploying RPC Client Access, you must also deploy Outlook Anywhere, to properly handle EWS (Exchange
Web Services) traffic.
a. U
se the default dynamic range of ports for RPC Client Access traffic or set static ports?
Select whether you want to use the default dynamic range of ports for RPC Client Access, or if you have configured your
Client Access servers to use specific ports outside the default range.
`` Use the default dynamic port range
Select this option to configure the iApp to use the default port range. If you choose the default dynamic range of ports,
no additional information is necessary, continue with the next question.
`` Set static ports
Select this option if you want to set static ports for RPC Client Access.
i Important
You must make sure each of your Client Access Servers is configured to use the static ports you
specified here. See http://social.technet.microsoft.com/wiki/contents/articles/configure-static-rpc-
ports-on-an-exchange-2010-client-access-server.aspx for more information.
9. A
re you deploying POP3?
Select whether you are deploying POP3 at this time.
ff No
Select this option if you are not deploying POP3 at this time. You can always reconfigure the template at another time to add
POP3 to the configuration.
ff Yes
Select this option if you are deploying POP3 at this time.
i Important
You must enable POP3 on each of your Exchange Client Access Servers before that service will be
available. POP3 is not enabled by default on Exchange Client Access Servers.
If you are offloading SSL, you must configure the Authentication properties for POP3 on each of your
Exchange Client Access Servers to allow logins using plain text. By default, POP3 is configured to only allow
secure (encrypted) logins.
39
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Specify the IP addresses of your POP3 servers. Click Add to include additional servers. If you chose to have the BIG-IP
system queue TCP requests, you must specify a Connection Limit. If you chose to enable Priority Group Activation, you
must specify a Priority.
10. A
re you deploying IMAP4?
Select whether you are deploying IMAP4 at this time.
ff No
Select this option if you are not deploying IMAP4 at this time. You can always reconfigure the template at another time to add
IMAP4 to the configuration.
ff Yes
Select this option if you are deploying IMAP4 at this time.
i Important
You must enable IMAP4 on each of your Exchange Client Access Servers before that service will be
available. IMAP4 is not enabled by default on Exchange Client Access Servers.
If you are offloading SSL, you must configure the Authentication properties for IMAP4 on each of your
Exchange Client Access Servers to allow logins using plain text. By default, IMAP4 is configured to only
allow secure (encrypted) logins.
a. What are the IP addresses of your IMAP4 servers?
This question only appears if you selected Each service will be handled by a unique set of Client Access Servers in
the previous section.
Specify the IP addresses of your IMAP4 servers. Click Add to include additional servers. If you chose to have the BIG-IP
system queue TCP requests, you must specify a Connection Limit. If you chose to enable Priority Group Activation, you
must specify a Priority.
1. D
o you want to use advanced or simple server health monitors?
Choose whether you want to use advanced or simple health monitors:
ff U
se simple monitors
Simple monitors check network connectivity but do not perform actual logins. If you use simple monitors, the BIG-IP LTM may
not be able to completely determine status of Client Access services. In this case, the monitor interval is set to 10 seconds
automatically, no matter what number is in the previous question.
ff U
se advanced monitors
If you choose advanced monitors, the BIG-IP system performs logins to most of the Client Access services (all except RPC/
MAPI in Exchange 2010, and Forms-based Outlook Web App) and checks for valid content in the response. Because these
monitors attempt to access a specific mailbox, they can more accurately determine the actual health of Client Access services.
However, account maintenance and Mailbox status must become a part of your monitoring strategy. For example, if an account
used for monitoring is locked or deleted, the monitor will mark the services down for all users.
40
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
i Important
5’s advanced monitors for Autodiscover, Exchange Web Services, and Outlook Anywhere support Basic and
F
NTLMv1 authentication only. See Advanced monitors for Autodiscover, EWS, and Outlook Anywhere only support
Basic and NTLMv1 authentication on page 56.
We strongly recommend creating a mailbox account(s) specifically for use in the monitor(s). The accounts for those mailboxes
should have no other privileges in the domain and should be configured with passwords that do not expire.
a. W
hat email address do you want to use for the advanced monitors?
This question only appears if you specified you are deploying Autodiscover and/or Exchange Web Services .
Type the email address associated with the account you are going to monitor (and that you specify in the following
question).
b. W
hich mailbox account should be used for the monitors?
Type a mailbox account for use in the advanced monitors. This name corresponds to the account name field in Active
Directory (rather than the email address).
c. What is the password for that mailbox account?
Type the associated password. Note that credentials are stored in plain text on this BIG-IP system.
d. W
hat is the domain name of the user account for the monitors?
Type the Domain name for the user account. This domain can be entered in either FQDN (mydomain.example.com) or
NetBIOS (MYDOMAIN) format.
e. D
o you want to monitor a second mailbox?
Choose whether you want to monitor a second mailbox. We strongly recommend configuring a second mailbox account
to be used by a second set of monitors, using a mailbox that is configured to reside on a different Mailbox server. The
BIG-IP LTM will only mark a Client Access service on a specific server down if both sets of credentials fail. This provides
resiliency to accommodate configuration errors with a single account, mailbox, or Mailbox server.
`` No
Select this option if you do not want the BIG-IP system to monitor a second mailbox. Continue with #2.
`` Yes
Select this option if you want the BIG-IP system to monitor a second mailbox.
i). W
hat email address do you want to use for the advanced monitors?
This question only appears if you specified you are deploying Autodiscover and/or Exchange Web Services .
Type the email address associated with the account you are going to monitor (and that you specify in the
following question).
ii). Which mailbox account should be used for the second monitor?
Type a mailbox account for use in the second monitors. Again, this name corresponds to the account name
field in Active Directory (rather than the email address).
iii). What is the password for that mailbox account?
Type the associated password.
iv). What is the domain name of the user account for the second monitors?
Type the Domain name for the second user account. This domain can be entered in either FQDN (mydomain.
example.com) or NetBIOS (MYDOMAIN) format.
If you are using APM in this scenario, you must choose Forms-Based. If you are using Forms-Based
authentication for OWA, you must change the credential format required for OWA on each Exchange Client
Access Server from the default domain\username format to just username.
41
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
ff O
WA uses the default Forms-Based authentication
Select this option if you are using Forms-based authentication, which is the default authentication mechanism for OWA.
If you chose Forms-based authentication, the BIG-IP system does not perform an actual login to the service, but checks the
availability of the forms-based authentication page.
ff O
WA uses Basic or Windows Integrated authentication
Select this option if you are using Basic/Windows Integrated authentication.
3. H
ow many seconds should pass between health checks?
Specifies how often the system checks the health of the servers. We recommend the default of 30 seconds. The maximum value for
the interval is 28,799 seconds.
Additional Steps
Review the information in the Additional steps section, and take appropriate action if necessary. All of the notes in Additional Steps are
found in the relevant section of this deployment guide.
Finished
Review your answers to the questions. When you are satisfied, click the Finished button. The BIG-IP system creates the relevant objects.
Continue with Next steps on page 51.
42
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Configuring the BIG-IP APM to provide secure remote access to Client Access Servers
If you chose BIG-IP APM will provide secure remote access to CAS, use this section for guidance on configuring the iApp. In this scenario,
the BIG-IP will be configured as a BIG-IP APM that will use a single virtual server to provide proxy authentication and secure remote access
to all Exchange HTTP-based Client Access services (Outlook Web App (including ECP), Outlook Anywhere (including EWS and OAB),
ActiveSync, and Autodiscover) without requiring the use of the F5 Edge Client. The traffic will be forwarded to separate BIG-IP running LTM
which will provide advanced load balancing, persistence, monitoring and optimizations for those services.
As mentioned in the prerequisites, because you are deploying BIG-IP APM, you must have configured the BIG-IP system for DNS and NTP.
See Configuring DNS and NTP settings on page 60 for instructions.
Analytics
This section of the template asks questions about Analytics. The Application Visibility Reporting (AVR) module allows you to view statistics
specific to your Microsoft Exchange implementation. AVR is available on all BIG-IP systems v11 and later, however you must have the AVR
provisioned for this option to appear. Note that this is only for application visibility reporting, you can view object-level statistics from the
BIG-IP without provisioning AVR.
i Important
Enabling Analytics may adversely affect overall system performance. If you choose to enable Analytics, we recommend
gathering statistics for a set time period, such as one week, and then re-entering this template and disabling Analytics
while you process the data.
If you plan on using AVR for analytics, we recommend creating a custom Analytics profile. To create a new profile, from the Main tab, select
Profiles and then click Analytics. Click New and then configure the profile as applicable for your configuration. See the online help or
product documentation for specific instructions. To select the new profile, you need to restart or reconfigure the iApp template.
1. Do
you want to enable Analytics for application statistics?
Choose whether you want to enable AVR for Analytics.
ff N
o, do not enable Analytics
If you do not want to enable Analytics, leave this list set to No, and continue with the next section.
ff Y
es, enable Analytics using AVR
If you choose to enable Analytics, select Yes from the list, and then answer the following questions.
a. U
se the default Analytics profile or select a custom profile?
If you decide to use AVR, you must decide whether to use the default Analytics profile, or create a new one. As mentioned
previously, we recommend creating a new profile to get the most flexibility and functionality out of AVR. If you have already
started the iApp template configuration and then decide to create a new Analytics profile, you must exit the iApp, create the
profile, and then restart the iApp template.
`` S
elect a custom Analytics profile
Select this option if you have already created a custom Analytics profile for Exchange Server.
i). W
hich Analytics profile do you want to use?
From the list, select the appropriate Analytics profile.
`` U
se default profile
Select this option if you have not yet created a custom Analytics profile for Microsoft Exchange. We do not
recommend using the default profile.
43
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
1. Which Active Directory servers in your domain can this BIG-IP system contact?
Specify both the FQDN and IP address of each Active Directory server you want the BIG-IP APM to use for servicing authentication
requests. Click Add to include additional servers.
2. What is the FQDN of your Active Directory domain for your Exchange users?
Specify the FQDN of the Active Directory deployment for your Exchange users. This is the FQDN for your entire domain, such as
example.com, rather than the FQDN for any specific host.
3. D
oes your Active Directory domain allow anonymous binding?
Select whether anonymous binding is allowed in your Active Directory environment.
ff Y
es, anonymous binding is allowed
Select this option if anonymous binding is allowed. No further information is required.
ff N
o, credentials are required for binding
If credentials are required for binding, you must specify an Active Directory user name and password for use in the AAA Server.
a. W
hich Active Directory user with administrative permissions do you want to use?
Type a user name with administrative permissions.
b. W
hat is the password associated with that account?
Type the associated password.
`` C
reate a new LDAP monitor for the Active Directory pool
Select this option if you want the template to create a new LDAP monitor for the Active Directory pool. You must
answer the following questions:
i). W
hich Active Directory user name should the monitor use?
Specify an Active Directory user name for the monitor to use when attempting to log on as a part of the health
check. This should be a user account created specifically for this health monitor, and must be set to never
expire.
ii). What is the associated password?
Specify the password associated with the Active Directory user name.
iii). What is the LDAP tree for this user account?
Specify the LDAP tree for the user account. As noted in the inline help, ADSI editor, an tool for Active Directory
LDAP administration, is useful for determining the correct LDAP tree value. For example, if the user name is
44
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
‘user1’ which is in the organizational unit ‘Exchange Users’ and is in the domain ‘exchange.example.com’, the
LDAP tree would be: ou=Exchange Users, dc=Exchange, dc=example, dc=com.
iv). Does your Active Directory domain require a secure protocol for communication?
Specify whether your Active Directory implementation requires SSL or TLS for communication, or does not
require a secure protocol. This determines the port the health monitor uses.
• No, a secure protocol is not required
Select this option if your Active Directory domain does not require a secure protocol.
• Yes, SSL communication is required
Select this option if your Active Directory domain requires SSL communication. The health check uses port
636 as the Alias Service Port.
• Yes, TLS communication is required
Select this option if your Active Directory domain requires TLS communication. The health check uses port
389 as the Alias Service Port.
1. W
hat IP address do you want to use for the BIG-IP APM virtual server?
Specify the IP address you want to use for the BIG-IP Access Policy Manager virtual server. This is the address clients will use to
access the HTTP-based Client Access services.
2. Do you want to re-encrypt the traffic that will be forwarded to your BIG-IP LTM?
Select whether you want the system to re-encrypt traffic that will be sent from this BIG-IP APM to the BIG-IP LTM.
We generally recommend you do not re-encrypt traffic between your BIG-IP APM and BIG-IP LTM because both BIG-IP systems must
process the SSL transactions. However, if you do choose to re-encrypt, we strongly recommend you use a valid certificate (usually
SAN-enabled) rather than the default, self-signed certificate for the Client SSL profile on your BIG-IP LTM system. If not re-encrypting
traffic, you do not need a certificate on your BIG-IP LTM.
ff Re-encrypt (SSL Bridging)
Select this option if your implementation requires encrypted traffic to the Client Access Servers, or you are using Exchange 2013
and do not have SP1 or later. The BIG-IP system unencrypts, then re-encrypts the traffic headed for the Client Access Servers.
a. Which Client SSL profile do you want to use?
The iApp can create a new Client SSL profile, or if you have created a Client SSL profile which contains the appropriate
SSL certificate and key for your Exchange implementation, you can select it from the list.
`` Select the Client SSL profile you created from the list
If you manually created a Client SSL profile, select it from the list, and then continue with #2.
`` Create a new Client SSL profile
Select this option if you want the iApp to create a new Client SSL profile.
i). W
hich SSL certificate do you want to use?
Select the SSL certificate you imported onto the BIG-IP system for decrypting client connections.
If you have not yet imported a certificate, you can leave the default selections and reconfigure this iApp after
obtaining the certificates. The deployment will not function correctly until you have selected the correct
certificates here.
Note
Any certificate that you obtain with multiple names must be in SAN (Subject Alternative Name)
format, not SNI (Server Name Indication) format. For more information on SAN certificates,
see Subject Alternative Name (SAN) SSL Certificates on page 103.
45
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
2). W
hich SSL key do you want to use?
Select the associated key from the list.
iii). Is the remote BIG-IP LTM receiving this traffic using a self-signed or default certificate for decryption, or is the
certificate signed by a CA?
Select whether the remote BIG-IP LTM receiving the traffic is using a self-signed (or default) certificate for
decrypting the traffic from this system, or if the certificate is signed by a Certificate Authority. Your answer
determines the Secure Renegotiation setting on the Server SSL profile. This BIG-IP system will not trust the
remote BIG-IP default or a self-signed certificate unless specifically configured to do so in this question.
i Important
This question pertains to the certificate used by the remote BIG-IP LTM, NOT the certificates
present and assigned on the local BIG-IP system you are configuring.
Any certificate that you obtain with multiple names must be in SAN (Subject Alternative Name)
format, not SNI (Server Name Indication) format. For more information on SAN certificates,
see Subject Alternative Name (SAN) SSL Certificates on page 103.
46
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
3. W
hat is the virtual IP address on the remote BIG-IP system to which you will forward traffic?
Type the IP address of the virtual server on the remote BIG-IP LTM to which you will be forwarding Client Access traffic from this
BIG-IP device. This BIG-IP APM sends traffic to this address after performing authentication.
4. W
ill clients be connecting to this BIG-IP virtual server primarily over a LAN or a WAN?
Select whether most clients are connecting over a WAN or LAN. The system uses your selection to configure the proper TCP
optimization settings.
ff WAN
Select this option if most clients are coming over a WAN.
ff LAN
Select this option if most clients are coming over a LAN.
5. Do you want to restrict Exchange Administration Center access by IP address or network? Exchange 2013 only
This question only appears if you selected Exchange 2013 as your version of Exchange.
Select whether you want the BIG-IP LTM to restrict Exchange Administration Center (EAC) access by IP address or network. In
Microsoft Exchange Server 2013, Exchange administration is now performed via the EAC, a web-based console. You configure the
iApp to control access to the EAC, allowing connections only from approved IP addresses or networks.
ff No, allow EAC access from all client IP addresses
Select this option to allow EAC access from all client IP addresses and networks. In this case, the system does not restrict EAC
access to specific IP addresses or networks, however, if you are deploying BIG-IP APM, you can still restrict access to EAC by
Organizational Management group in question b.
ff Yes, restrict EAC access to specific client IP addresses or networks
Select this option if you want to restrict EAC access to specific client IP addresses or networks. This adds an extra layer of
security to your Exchange deployment. The system creates a data group with the IP addresses or networks you specify, and
then uses an iRule to enforce the restrictions.
a. What IP or network addresses should be allowed EAC access?
Specify the IP addresses or networks should be allowed access to EAC. Click Add to include additional addresses or
networks.
i Important
If you are not deploying BIG-IP APM, the iApp currently does not attach the proper data group and
iRule. See Creating the Data Group and iRule for securing EAC access if not using BIG-IP APM on page
57 for information on how to configure these objects.
2. S
hould BIG-IP APM restrict EAC access to members of the Exchange Organization Management Security Group?
Exchange 2013 only
This question only appears if you selected Exchange 2013 as your version of Exchange and selected to provide secure
authentication with BIG-IP APM.
Select whether you want the BIG-IP APM to restrict Exchange Administration Center (EAC) access to members of Exchange 2013's
Organizational Management group. The BIG-IP APM module queries Active Directory group membership for the user making the
request to EAC. If the user is not a member of the Organization Management group, the BIG-IP APM policy denies access.
ff No, do not restrict EAC access by group membership
Select this option and the BIG-IP APM will not restrict access to the EAC by group membership.
ff Yes, restrict EAC access by group membership
Select this option if you want to restrict EAC access to the Organization Management group. This adds an additional layer
of security to your Exchange deployment, as the system denies access to the EAC from anyone who is not a member of the
Organization Management group.
47
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
i Important
Before completing this section, you must create a user account in the same domain that has been properly
configured for NTLM delegation. You must create an NTLM Machine Account object on the BIG-IP system to
join this system to the Active Directory domain. See Creating an NTLM Machine Account on page 61.
i Important
Improper use or misconfiguration of an iRule can result in unwanted application behavior and poor performance
of your BIG-IP system. We recommended you verify the impact of an iRule prior to deployment in production.
If you want to add iRules, from the Options box, select the iRule(s) you want to include, and then click the Add (<<) button.
Additional Steps
Review the information in the Additional steps section, and take appropriate action if necessary. All of the notes in Additional Steps are
found in the relevant section of this deployment guide.
Finished
Review your answers to the questions. When you are satisfied, click the Finished button. The BIG-IP system creates the relevant objects.
48
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Optional: Configuring the BIG-IP system to support MAPI over HTTP in Exchange 2013 SP1
Introduced in Exchange 2013 SP1, the new MAPI over HTTP transport protocol is for Outlook clients running Office 2013 SP1 and later
(only). This new service is not yet included in the iApp template, so you must manually configure the BIG-IP system to support it.
If you are using Microsoft Exchange 2013 SP1 or later and using the new MAPI over HTTP transport protocol, use the following guidance to
create the objects necessary to support MAPI over HTTP. If you configured the iApp template to use a combined virtual server, you create
a health monitor, pool, and an iRule. Because BIG-IP APM is not yet supported for MAPI over HTTP, the iRule includes a line (commented
out by default) to disable Access Policy processing for this new protocol only. If you configured the iApp to use separate virtual servers, you
create the monitor, pool, and a virtual server. The iRule is not necessary at all in this case.
Use the following table to create the objects on the BIG-IP LTM. Unless otherwise specified, settings not mentioned in the table can be
configured as applicable for your configuration. For instructions on configuring individual objects, see the online help or product manuals.
Simple Monitor
Name Type a unique name
Type HTTP (if using SSL offload) or HTTPS (if using SSL bridging)
Interval 30 (recommended)
Health Monitors Timeout 91 (recommended)
(Main tab-->Local Traffic-->Monitors) Send String GET /mapi/healthcheck.htm HTTP/1.1\r\nHost: mapi.example.local\r\nConnection: Close\r\n\r\n
Receive String 200 OK
Advanced Monitor
The advanced monitor for MAPI over HTTP uses the same monitor as the advanced monitor for the EWS service. You simply add
the EWS monitor to the pool in the next section and set the Availability Requirement to All as described.
Name Type a unique name
Health Monitor Select the monitor you created above. If you are using the advanced monitor, add both the
advanced and simple monitor you created.
Pools Availability Requirement If using the advanced monitor (only), select All
(Main tab-->Local Traffic -->Pools) Load Balancing Method Least Connections (Member)
Address Type the IP Address of your SharePoint server
Service Port 80 (if using SSL offload) or 443 (if using SSL bridging)
Click Add to repeat Address and Service Port for all nodes
Parent Profile http
HTTP
Redirect Rewrite Matching
TCP WAN2 Parent Profile tcp-wan-optimized
TCP LAN2 Parent Profile tcp-lan-optimized
49
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
1 when HTTP_REQUEST {
2 switch -glob -- [string tolower [HTTP::path]] {
3 "/mapi*" {
4 ###uncomment the following line to bypass APM for MAPI-over-HTTP
5 #ACCESS::disable
6 pool mapi_http_pool
7 COMPRESS::disable
8 CACHE::disable
9 return
10 }
11 }
12 }
1. From the Main tab of the BIG-IP Configuration utility, expand iApp and then click Application Services.
2. Click the name of your existing Microsoft Exchange application service from the list.
3. On the Menu bar, click Reconfigure.
4. If necessary, from the Do you want to customize your server pool settings? question, select Customize pool settings.
5. From the Do you want to add any iRules to this combined virtual server? question, select the iRule you just created and then
click the Add (<<) button to move it to the Selected list.
6. Click Finished.
50
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Next steps
After completing the iApp Template, the BIG-IP Application Services page opens for the Exchange application service you just created. To
see the list of all the configuration objects created to support Microsoft Exchange, on the Menu bar, click Components. The complete list
of all Exchange related objects opens. You can click individual objects to see the settings.
Once the objects have been created, you are ready to use the new deployment.
1. On the Main tab, expand iApp and then click Application Services.
2. Click the name of your Exchange Application service from the list.
i Important
To restart bigd
Viewing statistics
You can easily view a number of different statistics on the BIG-IP system related to the Exchange configuration objects created by the iApp
template. You can get statistics specific to the Application Service if you have provisioned AVR. Otherwise, you can always get object-level
statistics.
51
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
AVR statistics
If you have provisioned AVR, you can get application-level statistics for your Exchange application service.
1. On the Main tab, expand iApp and then click Application Services.
2. From the Application Service List, click the Exchange 2010 service you just created.
4. Use the tabs and the Menu bar to view different statistics for your Exchange iApp.
Object-level statistics
If you haven’t provisioned AVR, or want to view object-level statistics, use the following procedure.
2. From the Statistics Type menu, you can select Virtual Servers to see statistics related to the virtual servers.
3. You can also choose Pools or Nodes to get a closer look at the traffic.
For more information on viewing statistics on the BIG-IP system, see the online help or product documentation.
Adding Ratio or Connection Limit information to the nodes if using a node-based load balancing method
If you chose to customize the server pool settings, changed the load balancing method from the default to a node-based method (such
as Ratio (node) or Least Connections (node)), and configured a Ratio or Connection Limit, the iApp applies the ratio or connection limit
to the load balancing pool member, and not to the node itself. In this case, you must manually modify each node to include any Ratio or
Connection Limit settings you want to configure.
1. On the Main tab, expand Local Traffic and then click Nodes.
2. From the Node table, click a Client Access Server node you entered in the iApp template.
4. In the Connection Limit box, type the appropriate connection limit, if applicable.
5. Click Update.
6. Repeat this procedure for each node that is a part of your Exchange deployment.
52
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Troubleshooting
This section contains common issues and troubleshooting steps
hh Advanced health checks are fail when using Windows Integrated Authentication (NTLM provider)
If you are using Windows Integrated Authentication (NTLM provider) only, the BIG-IP health checks using a valid account may
fail, as the BIG-IP system fails to correctly form the authentication request headers.
If you are using Windows Authentication with NTLM and you have disabled Basic authentication for the Exchange service you
are monitoring, you must manually delete the \r\n at the end of the Send String, and the <domain>\ information from the User
Name field.
.
i Important
F5 monitors support NTLMv1 authentication. You must ensure that the LmCompatibilityLevel setting in Group
Policy for the domain used by the monitor credential is configured to support NTLMv1
hh Modifying the IIS authentication token timeout value
The iApp template configures most Exchange monitors to check service health every 30 seconds. However, to reduce traffic
between the Exchange server and domain controllers, IIS virtual directories configured to use Basic authentication cache
authentication tokens for up to 15 minutes before re-authenticating the user with Active Directory. This may result in the BIG-IP
pool members for these services being marked UP incorrectly while Basic authentication tokens are cached.
You can decrease the length of or disable this token caching period by editing the registry on the Exchange server. The length
of time configured for the token cache combined with the timeout value of the monitor will determine how long it will take until a
resource is marked down. For example, setting a token cache period of 60 seconds, combined with a monitor using a timeout
value of 91 seconds, will result in a resource being marked down after 151 seconds.
For instructions on modifying the registry, see the following Microsoft article (while this article says IIS 6.0, we tested it on IIS 7.5
with no modifications):
Critical: Use extreme caution any time you are editing the registry. Contact Microsoft for specific instructions and/or help editing
the registry values. http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/6b2e7fcd-5fad-
4ac8-ac0a-dcfbe771e9e1.mspx
hh Microsoft Exchange Remote Connectivity Analyzer fails to successfully run the FolderSync command
If you deployed the BIG-IP system for ActiveSync, either using the iApp template or manually, and attempt to run the Microsoft
Exchange Remote Connectivity Analyzer (ExRCA) against an Exchange mailbox, you may receive the following error:
This behavior affects versions of BIG-IP earlier than 11.4.0. To work around this error, you must create an iRule, and then use
the iApp template to apply the iRule to the combined Exchange BIG-IP virtual server (or attach the iRule manually if you used the
manual configuration tables).
3. I n the Definition section, copy and paste one of the following iRules, omitting the line numbers, depending on whether you
configured the system for a combined virtual server, or a separate virtual server for ActiveSync.
53
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
4. Click Finished.
The next task is to attach the iRule to the virtual server. This depends on whether you configured the BIG-IP system using the
iApp template or manually.
Attaching the iRule if you used the iApp template to configure the BIG-IP system
Use the following procedure if you used the iApp template to configure the BIG-IP system.
6. Click Finished.
hh iApp gives an error when using Analytics and deploying POP3 and IMAP4
If you are enabled Analytics in the iApp template and chose to deploy POP3 and IMAP4, you may see an error similar to the
following:
010713d3:3: Virtual server /Common/exchange_test.app/exchange_test_pop3: AVR profile requires an HTTP profile.
This occurs because using Analytics requires an HTTP profile, and because POP3 and IMAP4 are not HTTP, the template
correctly does not attach an HTTP profile to these virtual servers. This conflict causes the template to display the error.
Remember that enabling Analytics may adversely affect overall system performance. If you choose to enable Analytics, we
recommend gathering statistics for a set time period, such as one week, and then re-entering this template and disabling
Analytics while you process the data.
54
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Use the following guidance to work around this error until an updated iApp template is released:
Run a separate instance of the iApp template for POP3 and IMAP4 only
The first time you run the Exchange iApp template, complete the iApp as applicable for your environment, however select No to
the questions asking if you are deploying POP3 and IMAP4.
After completing the first instance of the iApp template, run the template again selecting No to the Analytics question, as well
as all of the questions about deploying Exchange services. Select Yes to one or both of the questions for POP3 and IMAP4.
Answer the other questions as applicable for your configuration.
After completing the second instance of the iApp, the configuration will then function as designed.
hh ActiveSync and/or Autodiscover aren't working after deploying the iApp for separate virtual servers and using APM
If you are having trouble with ActiveSync and/or Autodiscover after running the template, and the all of the following conditions
are true:
»» You are using a BIG-IP version between 11.0 and 11.3.x and,
»» You chose "Use different IP address for the difference [CAS] services" when configuring the iApp and,
»» You chose to deploy the iApp template for ActiveSync and/or Autodiscover and,
»» You chose to deploy BIG-IP APM
you may be receiving error messages in your log files due to the template attaching a legacy iRule to the ActiveSync virtual
server. Use the following guidance to work around this issue:
Modifying the existing iApp template configuration
1. Re-enter the iApp template (on the Main tab, click iApp > Application Services > [name of your Exchange application
service] and then from the Menu bar, click Reconfigure).
2. If you also deployed the iApp for Autodiscover:
In the Tell us which services you are deploying section, from the "Do you want to customize your server pool settings"
question, select Customize pool settings. Under the Autodiscover IP address question, from the "Do you want to add any
custom iRules to this virtual server?" question, enable either the built-in _sys_APM_ExchangeSupport_OA_BasicAuth or
sys_APM_ExchangeSupport_OA_NTLMAuth Rule as depending on your auth method.
3. From the "Are you deploying ActiveSync?" question, select No.
4. Click Finished.
hh Clients receiving error message when using BIG-IP APM with OWA 2013 and IE10 or Google Chrome
If you are using BIG-IP APM and Outlook Web App 2013, and have clients using Internet Explorer 10 or Google Chrome, clients
may receive the following error message from the BIG-IP APM: Access policy evaluation is already in progress for your current
session. If clients are receiving this error, you must apply the an iRule to the virtual server(s) used for OWA 2013.
To create the iRule and add it to the OWA 2013 virtual server
1. On the Main tab, expand Local Traffic and then click iRules.
2. Click Create.
3. In the Name box, type a unique name for this iRule.
4. In the Definition section, copy and paste the following iRule, omitting the line numbers.
55
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
1 when HTTP_REQUEST {
2 if { [HTTP::cookie exists "IsClientAppCacheEnabled"] } {
3 HTTP::cookie "IsClientAppCacheEnabled" False
4 }
5 }
hh Experiencing issues with iOS devices and ActiveSync when the BIG-IP system is behind a device performing NAT
If the BIG-IP system is located behind a device that performs network address translation (NAT), and you are experiencing issues
with iOS devices and ActiveSync, we recommend you modify the appropriate persistence iRule to include a wildcard character.
If you deployed BIG-IP APM and a combined virtual server, this iRule is [name of your Exchange application service]_apm_
combined_pool_irule[random number]. If you deployed APM and separate IP addresses for separate services, the iRule is
[name of your Exchange application service]_combined_persist_irule[random number]. If you did not deploy BIG-IP APM, the
iRule is [name of your Exchange application service]_oa_persist_irule for both combined and separate IP addresses.
hh Advanced monitors for Autodiscover, EWS, and Outlook Anywhere only support Basic and NTLMv1 authentication
The advanced monitors for Autodiscover, Exchange Web Services, and Outlook Anywhere support Basic and NTLMv1
authentication only. If you have configured your domain to use NTLMv2 only, you must modify the health monitors to remove the
--ntlm option from the curl statement used in the Autodiscover, EWS, and Outlook Anywhere external monitors (if you deployed
the template for these services) using the guidance in this section.
Additionally, you will need to enable Basic authentication for the EWS virtual directory using the IIS Manager snap-in on each
Exchange Client Access Server. Consult the Microsoft documentation for instructions.
i Important
This is only necessary if you have configured your domain to use NTLMv2.
56
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
c. L
ocate the line that begins with curl and remove the --ntlm portion only. When you are finished, this line should look
similar to the following:
curl -g -s -k -X POST -H 'Content-Type: text/xml; charset=utf-8' -d "${XMLFULL}" -u
${DOMAIN}\\${USER}:${PASSWORD} https://${NODE}${ADSURI} | grep -i "${RECV}" 2>&1 > /dev/null
d. Click Update.
e. If you deployed other applicable services, repeat steps b - e for any to remove --ntlm from that file.
Important: If you re-enter the iApp template and modify the configuration using the Reconfigure option, you must make
these changes again, as the iApp will overwrite the modifications.
hh Creating the Data Group and iRule for securing EAC access if not using BIG-IP APM
The iApp template currently does not attach the necessary Data Group and iRule to the configuration if you are not deploying
BIG-IP APM. In order for this feature to function as designed, you must manually create these objects. This is only necessary if
you are not deploying APM.
To create the Data Group and iRule and attach the iRule to the virtual server
a. T
o configure the Data Group and iRule, see the procedures in Optional: Securing Access to the Exchange 2013
Administration Center on page 92, and then return to this section for instructions on attaching the iRule.
b. R
e-enter the iApp template (on the Main tab, click iApp > Application Services > [name of your Exchange application
service] and then from the Menu bar, click Reconfigure).
c. In the Tell us which services you are deploying section, from the "Do you want to customize your server pool settings"
question, select Customize pool settings.
d. E
ither in the "Do you want to add any custom iRules to this combined virtual server?" (if you used a single IP address) or
in the "Do you want to add any custom iRules to this virtual server?" question under the IP address for OWA question (if
you used different IP addresses), enable the iRule you just created.
e. Click Update.
hh Guest accounts on the BIG-IP system can view the persistence table
Since the Exchange iApp uses the Basic authorization header for ActiveSync and Outlook Anywhere session persistence, BIG-IP
guest accounts that have been explicitly granted access to the Traffic Management Shell (tmsh) are able to view encoded user
credential and password information. It is possible an attacker logging in to BIG-IP as a guest could decode these credentials.
F5 recommends disabling tmsh access for any BIG-IP guest accounts by clicking System>Users>User List>Terminal
Access>Disabled>Finished.
Alternately, you may edit the iRule(s) created by the iApp template to obfuscate the encoded credentials. These changes are not
necessary if you have used the iApp template to deploy F5’s Access Policy Manager module. Replace all instances of:
persist uie [HTTP::header "Authorization"] 7200 with:
set <service>_key [sha256 [HTTP::header "Authorization"]]
persist uie $<service>_key 7200
Where <service> indicates either ActiveSync or Outlook Anywhere. For example:
set oa_key [sha256 [HTTP::header "Authorization"]]
persist uie $oa_key 7200
57
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
hh E
xperiencing authentication issues when deploying the iApp using BIG-IP APM for client-side NTLM for Outlook
Anywhere
If you deployed the template to use BIG-IP APM, and selected Outlook Anywhere clients use NTLM authentication, you may
experience authentication issues because the iApp creates an improperly configured Exchange profile.
To work around this issue, you must modify the Autodiscover, EWS, and OAB Front End Authentication type. Additionally, If you
deployed the template for separate IP addresses for the Client Access services, you must change the Exchange profile’s default
NTLM configuration.
hh iPhones and other iOS devices are displaying invalid certificate messages after deploying the iApp for ActiveSync
If you deployed the iApp template for ActiveSync (or manually configured the BIG-IP system) and iOS devices started showing
invalid certificate messages even though the certificates were issued by an appropriate authority, you must manually create
an Client SSL profile that uses a Chain certificate. Intermediate certificates, also called intermediate certificate chains or chain
certificates, are used to help systems which depend on SSL certificates for peer identification.
Use the guidance in this solution to create a Client SSL profile that uses an intermediate certificate chain:
http://support.f5.com/kb/en-us/solutions/public/13000/300/sol13302.html.
Be sure Secure Renegotiation is set to Require (the default) on the Client SSL profile.
If you manually configured the system, add the Client SSL profile to your virtual server.
If you used the iApp, use this procedure:
a. R
e-enter the iApp template (on the Main tab, click iApp > Application Services > [name of your Exchange application
service] and then from the Menu bar, click Reconfigure).
b. In the Tell us about your deployment section, from the " Do you want to create a new client SSL profile or use and
existing one?" question, select the profile you just created that uses the Chain certificate.
c. Click Update.
58
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
hh U
sers experiencing slow response times when using calender functionality or reduced responsiveness when using
RPC client Access in Exchange 2010 when us
This slowness or reduced responsiveness can be caused by a setting in the WAN-optimized TCP profile. You may experience
this issue if:
»» Y
ou configured the BIG-IP system using the iApp template, and
- You specified most clients are connecting to the BIG-IP virtual server primarily over a WAN, and
- You are deploying Outlook Anywhere and/or RPC Client Access
»» Y
ou configured the system manually, and
- You used a TCP profile based on the default tcp-wan-optimized parent for the combined virtual server, Outlook
Anywhere and/or RPC Client Access (2010 only).
This issue can be solved by either assigning a TCP profile to the virtual server that does not use Nagle's algorithm (such as
tcp-lan-optimized, or the default tcp profile), or disabling Nagle's algorithm on the TCP profile. Use the appropriate procedure,
depending on whether you used the iApp template to configure the BIG-IP system, or configured the BIG-IP system manually.
4. In the Nagle's Algorithm row, click the Custom box on the right if necessary, and then clear the check from the Enabled box
to disable Nagle's Algorithm.
5. Click the Update button. Repeat for RPC Client Access if necessary.
Remember, if you use the Reconfigure option to make changes to the iApp, you need to make any of these manual changes
again.
3. In the Nagle's Algorithm row, click the Custom box on the right if necessary, and then clear the check from the Enabled box
to disable Nagle's Algorithm.
4. Click the Update button. Repeat for RPC Client Access if necessary.
59
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Note
DNS lookups go out over one of the interfaces configured on the BIG-IP system, not the management interface.
The management interface has its own, separate DNS settings.
i Important
The BIG-IP system must have a self IP address in the same local subnet and VLAN as the DNS server, or a
route to the DNS server if located on a different subnet. The route configuration is found on the Main tab by
expanding Network and then clicking Routes. For specific instructions on configuring a route on the BIG-IP
system, see the online help or the product documentation.
4. Click Update.
3. I n the Address box, type the fully-qualified domain name (or the IP address) of the time server that you want to add to the Address
List.
5. Click Update.
To verify the NTP setting configuration, you can use the ntpq utility. From the command line, run ntpq -np.
See http://support.f5.com/kb/en-us/solutions/public/10000/200/sol10240.html for more information on this command.
60
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
1. On the Main tab, expand Access Policy, and then click Access Profiles.
2. On the Menu bar, from the NTLM menu, click Machine Account List.
4. In the Name box, type a name for the BIG-IP Machine Account object.
5. In the Machine Account Name box, type the name of the computer account that will be created in the domain after clicking Join.
6. In the Domain FQDN box, type the fully qualified domain name of the domain that you want the machine account to join.
7. I n the Domain Controller FQDN box, if the machine account should have access to one domain only, type the FQDN for the
domain controller for that domain.
8. In the Admin User box, type the name of a user with administrative privileges.
61
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
1. From your Windows Server 2008 or Windows Server 2008 R2 device, open Server Manager.
4. Under Health and Diagnostics, check the box for Custom Logging, and then click Next.
6. After the service has successfully installed, click the Close button.
1. From your Windows Server 2008 or Windows Server 2008 R2 device, open the Internet Information Services (IIS) Manager.
2. F
rom the Connections navigation pane, click the appropriate server, web site, or directory on which you are configuring Advanced
Logging. The Home page appears in the main panel.
4. From the Actions pane on the right, click Edit Logging Fields.
5. From the Edit Logging Fields dialog box, click the Add Field button, and then complete the following:
a. In the Field ID box, type X-Forwarded-For.
62
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
6. C
lick a Log Definition to select it. By default, there is only one: %COMPUTERNAME%-Server. The log definition you select must have
a status of Enabled.
7. From the Actions pane on the right, click Edit Log Definition.
8. Click the Select Fields button, and then check the box for the X-Forwarded-For logging field.
Now, when you look at the logs, the client IP address is included.
63
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Autodiscover
Type External
Interval 30 (recommended)
Timeout 91 (recommended)
External Program See Importing the monitor script files on page 73 for the EAV script
Variables
Name Value
USER The account name associated with a mailbox.
PASSWORD The password for the account
DOMAIN The Windows domain for the account
EMAIL The email address for the user mailbox (such as j.smith@example.com)
1
For Advanced Monitors only. Simple monitors only require the Type, Interval, and Timeout. Replace red text with your FQDN. It must be on a single line.
This response string is part of a Cookie header that OWA returns. Although you may elect to use another string on the page, it must be on the first 5,120 bytes of the received
2
data (including headers and payload). Strings found near the end of the HTTP response from OWA will not be properly detected. See
http://support.f5.com/kb/en-us/solutions/public/3000/400/sol3451.html for more details.
3
You must only include a single \r\n at the end of the string.
64
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Port 443 iRules Add the Append and Persistence iRules. If using APM, enable the built-in
Virtual Servers _sys_APM_ExchangeSupport_OA_BasicAuth Rule (or if using 11.3.x and NTLM,
(Local Traffic--> _sys_APM_ExchangeSupport_OA_NTLMAuth).
Virtual Servers) Important: The Append iRule must be listed first
Default Pool Do not select a default pool for this virtual
Port 80 Destination Address IP address for the virtual server (Service Port 80)
(optional, for redirect Profiles HTTP profile only
purposes only) iRule _sys_https_redirect
1
The optimized TCP profiles are optional. If not creating the optimized profiles, create a TCP profile with the base TCP parent
2
Server SSL profile is only necessary if configuring SSL Bridging.
3
If you expect more than 6,000 concurrent users per Client Access Server, create a SNAT Pool instead of using Auto Map. You must also create the iRule in Creating an iRule when
using a SNAT pool on page 79. See the BIG-IP documentation for creating SNAT Pools. This field is called "Secure Address Translation in version" 11.3 and later.
65
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Configuration table if using separate virtual servers for Exchange HTTP-based services
Outlook Web App configuration table - includes the Exchange Control Panel (ECP)
BIG-IP object Non-default settings/Notes
Type HTTP (SSL offload), HTTPS (SSL Bridging). If using Exchange 2013, you must use HTTPS.
Interval 30 (recommended)
Timeout 91 (recommended)
Send String 1 If using the default forms-based authentication for OWA
iRules OWA Redirect iRule Create the Redirect iRule, using the Definition found on page 74
(Local Traffic-->iRules) Persistence iRule Create the Persistence iRule, using the Definition found on page 74
66
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Outlook Anywhere configuration table (for separate virtual servers) - includes EWS (Exchange Web Services) and OAB (Offline Address Book)
BIG-IP object Non-default settings/Notes
Type External
Interval 30 (recommended)
Timeout 91 (recommended)
TCP LAN 2
Parent Profile tcp-lan-optimized
Profiles Add each of the profiles you created above from the appropriate list
Destination Address IP address for the virtual server (Service Port 80)
Port 80
(optional, for redirect Profiles HTTP profile only
purposes only)
iRule _sys_https_redirect
Active Sync manual configuration table (for separate virtual server configuration)
BIG-IP object Non-default settings/Notes
Type HTTP (SSL offload), HTTPS (SSL Bridging). If using Exchange 2013, you must use HTTPS.
Interval 30 (recommended)
Timeout 91 (recommended)
Health Monitors Send String 1
OPTIONS /Microsoft-Server-ActiveSync/ HTTP/1.1\r\nHost: mail.example.com\r\n
(Local Traffic-->
Monitors) Receive String MS-ASProtocolCommands: Sync,SendMail,SmartForward,SmartReply,GetAttachment,GetHierar
chy,CreateCollection,DeleteCollection,MoveCollection,FolderSync
User Name Type the appropriate user name of a valid mailbox account.
Service Port 80 (443 if configuring SSL Bridging) Repeat Address and Port for all members
HTTP Parent Profile http
TCP WAN 2
Parent Profile tcp-wan-optimized
iRules If you are using Exchange 2010, create the Persistence iRule for ActiveSync, using the Definition found on page
ActiveSync Persist
(Local Traffic-->iRules) 74. This iRule is optional.
Destination Address IP address for the virtual server (Service Port 443)
Profiles Add each of the profiles you created above from the appropriate list
Port 80 Destination Address IP address for the virtual server (Service Port 80)
(optional, for redirect Profiles HTTP profile only
purposes only) iRule _sys_https_redirect
1
For Advanced Monitors only. Simple monitors only require the Type, Interval, and Timeout. Replace red text with your FQDN. It must be on a single line with a slingle \r\n.
2
The optimized TCP profiles are optional. If not creating the optimized profiles, create a TCP profile with the base TCP parent
3
Server SSL profile is only necessary if configuring SSL Bridging.
4
If you expect more than 6,000 concurrent users per Client Access Server, create a SNAT Pool instead of using Auto Map. You must also create the iRule in Creating an iRule when
using a SNAT pool on page 79. See the BIG-IP documentation for creating SNAT Pools. This field is called "Secure Address Translation in version" 11.3 and later.
68
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Health Monitors External Program1 See Importing the monitor script files on page 73 for the EAV script
(Local Traffic--> Variables1
Name Value
Monitors)
USER The account name associated with a mailbox.
PASSWORD The password for the account
DOMAIN The Windows domain for the account
EMAIL The email address for the user mailbox (such as j.smith@example.com)
Service Port 80 (443 if configuring SSL Bridging) Repeat Address and Port for all members
HTTP Parent Profile http
TCP WAN2 Parent Profile tcp-wan-optimized
Profiles Add each of the profiles you created above from the appropriate list
SNAT Pool 4
Auto Map 4
Port 443
Virtual Servers iRules If using APM, enable the built-in _sys_APM_ExchangeSupport_OA_BasicAuth
(Local Traffic--> rule (or if using 11.3.x and NTLM, _sys_APM_ExchangeSupport_OA_NTLMAuth)
Virtual Servers) Default Pool Select the pool you created for Autodiscover above
Destination Address IP address for the virtual server (Service Port 80)
Port 80
(optional, for redirect Profiles HTTP profile only
purposes only)
iRule _sys_https_redirect
1
For Advanced Monitors only. Simple monitors only require the Type, Interval, and Timeout.
2
The optimized TCP profiles are optional. If not creating the optimized profiles, create a TCP profile with the base TCP parent
3
Server SSL profile is only necessary if configuring SSL Bridging.
4
If you expect more than 6,000 concurrent users per Client Access Server, create a SNAT Pool instead of using Auto Map. You must also create the iRule in Creating an iRule when
using a SNAT pool on page 79. See the BIG-IP documentation for creating SNAT Pools. This field is called "Secure Address Translation in version" 11.3 and later.
69
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
i Important
xchange Server 2013 Client Access Servers do not offer MAPI as a connection option. If you are deploying
E
Exchange Server 2013, do NOT configure the BIG-IP system for RPC Client Access.
70
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Virtual Servers Profiles Add each of the profiles you created above from the appropriate list
(Local Traffic--> SNAT Pool Auto Map 4
Virtual Servers)
Default Pool Select the pool with members using Service Port 135 you created for RPC Client Access above
Create two additional virtual servers, one for MAPI and one for Address Book Service, using the settings above; only the Name, Service
Port and Pool are different: The Service Port depends on your configuration. Use the associated pool you created.
After completing this virtual server, you must modify either the Single virtual server you created for the HTTP-based CAS services, or the
separate virtual server you created for Outlook Anywhere to use the persistence profile you created in this section as a Fallback persistence
Additional steps
profile. From the Fallback Persistence Profile list of the Single virtual, or the Outlook Anywhere separate virtual, select the profile you
created in this section, and then click the Update button.
1
In Exchange Server 2010, you must configure a Client Access Array for your site to use the FQDN you have set to resolve to the IP address of the BIG-IP LTM virtual server, and
you must update the existing mailbox database attributes to use that array.
2
You must select Advanced from the Configuration list for this option to appear
3
The optimized TCP profiles are optional. If not creating the optimized profiles, create a TCP profile with the base TCP parent
4
If you expect more than 6,000 concurrent users per Client Access Server, create a SNAT Pool instead of using Auto Map. You must also create the iRule in Creating an iRule
when using a SNAT pool on page 79. See the BIG-IP documentation for creating SNAT Pools.
71
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
72
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Note
If you are using a redundant BIG-IP system, you need to make sure any modifications to the script EAVs are manually
copied between BIG-IP LTMs, and given the required permissions when configuration is synchronized.
If you are going to use two instances of the health check to monitor two mail boxes, you must use a unique user name
and password for each monitor.
• Autodiscover
»» If you configured SSL Offload (2010): www.f5.com/solution-center/deployment-guides/files/autodiscover-eav-offload.zip
»» If you configured SSL Bridging www.f5.com/solution-center/deployment-guides/files/autodiscover-eav-ssl-bridging.zip
4. Type the following command to change the permissions of the file using the following command syntax:
chmod 755 /config/monitors/<file name>
For example
chmod 755 /config/monitors/autodiscover-monitor.sh
6. From the Main tab of the BIG-IP Configuration utility, expand System, and then click File Management.
9. In the File Name row, click Browse, and then locate the appropriate file.
10. In the Name box, type a name for the file related to the script you are using.
Now when you create the advanced monitors, you can select the name of the file you imported from the External Program list.
73
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
iRules
This section contains the iRules referenced from the manual configuration tables. To create an iRule, from the Main tab, expand Local
Traffic, and then click iRules. Click Create, give the iRule a unique name, and then copy and paste the iRule code into the Definition
section (omitting the line numbers). If specified, you must replace any parts of the code in red text with the names of the appropriate BIG-IP
object.
This iRule should appear at the top of the iRule list in the virtual server and come before any persistence iRules you might use.
Persistence iRule if using a single virtual server for all HTTP-based services
For this configuration, you must create an additional iRule which changes persistence methods based on the service being
accessed. When using a single virtual server for OWA, Outlook Anywhere, ActiveSync, and Autodiscover, you need to use an iRule
to separate the traffic that supports cookie persistence (Outlook Web App and ActiveSync) from that which does not (Outlook
Anywhere) and assign appropriate persistence methods. This example creates a persistence iRule that uses correct persistence
methods for each access type. This iRule assumes the use of separate pools for the services as configured by the template.
! Critical
You must change the pool names in the following iRules (shown in red) to match the names of the pools in your
configuration.
Because of the length of this iRule, you can use the following text file to make the copy paste operation easier:
http://www.f5.com/solution-center/deployment-guides/files/exchange-persist.zip.
However, if you download the zip file, you must still modify the iRule to match the name of the pools in your configuration.
If you are using Exchange 2013, you must use the iRule in Exchange 2013 only: Persistence iRule if using a single virtual server for all
HTTP-based services on page 77
74
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Exchange 2010 only: Persistence iRule if using a single virtual server for all HTTP-based services
1 ## iRule to select pool and persistence method when all Exchange Client
2 ## Access HTTP-based services are accessed through the same BIG-IP virtual
3 ## server. This iRule will use an HTTP header inserted by a BIG-IP Edge
4 ## Gateway for persistence (if that header is present); otherwise it will
5 ## set persistence according to traditional methods.
6
7 ## CHANGE ALL POOL NAMES TO MATCH THOSE IN YOUR ENVIRONMENT.
8
9 when HTTP_REQUEST {
10
11 ## Offline Address Book and Autodiscover do not require persistence.
12
13 switch -glob -- [string tolower [HTTP::path]] {
14
15 "/microsoft-server-activesync*" {
16 ## ActiveSync.
17 if { [HTTP::header exists "APM_session"] } {
18 persist uie [HTTP::header "APM_session"] 7200
19 } elseif { [HTTP::header exists "Authorization"] } {
20 set as_key [sha256 [HTTP::header "Authorization"]]
21 persist uie $as_key 7200
22 } else {
23 persist source_addr
24 }
25 pool as_pool_name
26 COMPRESS::disable
27 CACHE::disable
28 return
29 }
30
31 "/owa*" {
32 ## Outlook Web Access
33 if { [HTTP::header exists "APM_session"] } {
34 persist uie [HTTP::header "APM_session"] 7200
35 } else {
36 persist cookie insert timeout 0
37 }
38 pool owa_pool_name
39 return
40 }
41
42 "/ecp*" {
43 ## Exchange Control Panel.
44 if { [HTTP::header exists "APM_session"] } {
45 persist uie [HTTP::header "APM_session"] 7200
46 } else {
47 persist cookie insert timeout 0
48 }
49 pool owa_pool_name
50 return
51 }
52
53 "/ews*" {
54 ## Exchange Web Services.
55 if { [HTTP::header exists "APM_session"] } {
56 persist uie [HTTP::header "APM_session"] 7200
57 } else {
58 persist source_addr
59 }
60 pool oa_pool_name
61 COMPRESS::disable
62 CACHE::disable
63 return
64 }
75
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
ÂÂ Critical This iRule is a continuation of the iRule from the previous page.
65 "/oab*" {
66 ## Offline Address Book.
67 pool oa_pool_name
68 return
69 }
70
71 "/rpc/rpcproxy.dll*" {
72 ## Outlook Anywhere.
73 if { [HTTP::header exists "APM_session"] } {
74 persist uie [HTTP::header "APM_session"] 7200
75 } elseif { [string tolower [HTTP::header "Authorization"]] starts_with "basic" } {
76 set oa_key [sha256 [HTTP::header "Authorization"]]
77 persist uie $oa_key 7200
78 } else {
79 persist source_addr
80 }
81
82 pool oa_pool_name
83 COMPRESS::disable
84 CACHE::disable
85 return
86 }
87
88 "/autodiscover*" {
89 ## Autodiscover.
90 pool ad_pool_name
91 return
92 }
93
94 default {
95 ## This final section takes all traffic that has not otherwise
96 ## been accounted for and sends it to the pool for Outlook Web App
97 if { [HTTP::header exists "APM_session"] } {
98 persist uie [HTTP::header "APM_session"] 7200
99 } else {
100 persist source_addr
101 }
102 pool owa_pool_name
103 }
104 }
105 }
106
107 when HTTP_RESPONSE {
108 if { [string tolower [HTTP::header values "WWW-Authenticate"]] contains "negotiate"} {
109 ONECONNECT::reuse disable
110 ONECONNECT::detach disable
111 ## this command disables NTLM conn pool for connections where OneConnect has been disabled
112 NTLM::disable
113 }
114 ## this command rechunks encoded responses
115 if {[HTTP::header exists "Transfer-Encoding"]} {
116 HTTP::payload rechunk
117 }
118 }
76
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Exchange 2013 only: Persistence iRule if using a single virtual server for all HTTP-based services
1 ## iRule to select pool when all Exchange Client Access HTTP-based services are
2 ## accessed through the same BIG-IP virtual server. This iRule is for users who
3 ## do not require any persistence.
4 ## CHANGE ALL POOL NAMES TO MATCH THOSE IN YOUR ENVIRONMENT.
5
6 when HTTP_REQUEST {
7 switch -glob -- [string tolower [HTTP::path]] {
8 "/microsoft-server-activesync*" {
9 ## ActiveSync.
10 pool as_pool_name
11 COMPRESS::disable
12 CACHE::disable
13 return
14 }
15 "/owa*" {
16 ## Outlook Web Access
17 pool owa_pool_name
18 return
19 }
20 "/ecp*" {
21 ## Exchange Control Panel.
22 pool owa_pool_name
23 return
24 }
25 "/ews*" {
26 ## Exchange Web Services.
27 pool oa_pool_name
28 COMPRESS::disable
29 CACHE::disable
30 return
31 }
32 "/oab*" {
33 ## Offline Address Book.
34 pool oa_pool_name
35 return
36 }
37 "/rpc/rpcproxy.dll*" {
38 ## Outlook Anywhere.
39 pool oa_pool_name
40 COMPRESS::disable
41 CACHE::disable
42 return
43 }
44 "/autodiscover*" {
45 ## Autodiscover.
46 pool ad_pool_name
47 return
48 }
49 default {
50 ## This final section takes all traffic that has not otherwise
51 ## been accounted for and sends it to the pool for Outlook Web App
52 pool owa_pool_name
53 }
54 }
55 }
56 when HTTP_RESPONSE {
57 if { [string tolower [HTTP::header values "WWW-Authenticate"]] contains "negotiate"} {
58 ONECONNECT::reuse disable
59 ONECONNECT::detach disable
60 ## this command disables NTLM conn pool for connections where OneConnect
61 ## has been disabled
62 NTLM::disable
63 }
64 ## this command rechunks encoded responses
65 if {[HTTP::header exists "Transfer-Encoding"]} {
66 HTTP::payload rechunk
67 }
68 }
77
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Outlook Anywhere persistence iRule if using separate pools AND virtual servers
This iRule is necessary because the Microsoft Outlook client does not support HTTP cookies, so the BIG-IP LTM persists based on other
HTTP header information. In some cases you may be able to use other persistence methods such as Source Address Affinity, which bases
persistence on the IP address of the client. However, because proxy servers or NAT (network address translation) devices may aggregate
clients behind a single IP address, such methods are not always effective. To ensure reliable persistence, we recommend using the following
iRule and associated persistence profile. Use the appropriate iRule depending on your version of Exchange.
Outlook Anywhere persistence iRule for Exchange 2010 only
1 when HTTP_REQUEST {
2 switch -glob -- [string tolower [HTTP::path]] {
3 "/ews*" {
4 ## Exchange Web Services.
5 if { [HTTP::header exists "APM_session"] } {
6 persist uie [HTTP::header "APM_session"] 7200
7 } else {
8 persist source_addr
9 }
10 }
11 "/rpc/rpcproxy.dll*" {
12 ## Outlook Anywhere.
13 if { [HTTP::header exists "APM_session"] } {
14 persist uie [HTTP::header "APM_session"] 7200
15 } elseif { [string tolower [HTTP::header "Authorization"]] starts_with "basic" } {
16 set oa_key [sha256 [HTTP::header "Authorization"]]
17 persist uie $as_key 7200
18 } else {
19 persist source_addr
20 }
21 }
22 }
23 }
24 when HTTP_RESPONSE {
25 if { [string tolower [HTTP::header values "WWW-Authenticate"]] contains "negotiate"} {
26 ONECONNECT::reuse disable
27 ONECONNECT::detach disable
28 ## disables NTLM conn pool for connections where OneConnect has been disabled
29 NTLM::disable
30 }
31 ## this command rechunks encoded responses
32 if {[HTTP::header exists "Transfer-Encoding"]} {
33 HTTP::payload rechunk
34 }
35 }
Outlook Anywhere persistence iRule for Exchange 2013 or deployments not using persistence only
1 when HTTP_RESPONSE {
2 if { [string tolower [HTTP::header values "WWW-Authenticate"]] contains "negotiate"} {
3 ONECONNECT::reuse disable
4 ONECONNECT::detach disable
5 ## disables NTLM conn pool for connections where OneConnect has been disabled
6 NTLM::disable
7 }
8 ## this command rechunks encoded responses
9 if {[HTTP::header exists "Transfer-Encoding"]} {
10 HTTP::payload rechunk
11 }
12 }
78
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Make sure to attach the iRule to the virtual servers where you are using a SNAT pool.
1 when RULE_INIT {
2 # Use a local array to configure SNAT addresses.
3 # These addresses must be defined in a SNAT pool.
4 # In this example, we use three addresses. Replace
5 # these with the IP addresses used in your SNAT Pool.
6 # Follow the pattern of the existing addresses to add more than three.
7
8 set static::snat_ips(0) 10.0.0.1
9 set static::snat_ips(1) 10.0.0.2
10 set static::snat_ips(2) 10.0.0.3
11 }
12
13 when CLIENT_ACCEPTED {
14 # Calculate the crc32 checksum of the client IP.
15 # Use the modulo of the checksum and the number of SNAT IPs in the array
16 # to select a SNAT IP address.
17
18 snat $static::snat_ips([expr {[crc32 [IP::client_addr]] % [array size static::snat_ips]}])
19
20 }
Note
If you are configuring multiple Exchange deployments on the same BIG-IP device and are using SNAT pools,
you must change the variable names (snat_ips) in the iRule for each separate deployment.
79
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Proxy Auth
Clients
b. B
oth the BIG-IP APM and the BIG-IP LTM will perform SSL Bridging; they will decrypt SSL traffic in order to process it, then
re-encrypt the traffic before placing it back on the network.
Active
Directory
Proxy Auth
Clients
2. A
single BIG-IP configured with both APM and LTM modules.
There are two options in this scenario:
a. The BIG-IP will terminate SSL connections and forward traffic to your Exchange Client Access servers on HTTP port 80.
Active
Directory
Proxy Auth
Clients
HTTPS HTTP
BIG-IP APM
and LTM
(SSL Offload) Client Access
Servers
(SSL Offload enabled)
b. T
he BIG-IP will perform SSL bridging; SSL will be decrypted on the BIG-IP but re-encrypted before it is placed back on the
network.
Active
Directory
Proxy Auth
Clients
HTTPS HTTPS
BIG-IP APM
and LTM
(SSL Bridging) Client Access
Servers
80
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
DNS and NTP See Configuring DNS and NTP settings on page 60 for instructions.
Type LDAP
Interval 10 (recommended)
Timeout 31 (recommended)
User Name Type a user name with administrative permissions
Health Monitor
Password Type the associated password
(Main tab-->Local
Traffic-->Monitors) Base Specify your LDAP base tree. For example, CN=Exchange Users,DC=example,DC=com
Filter Specify the filter. We type cn=user1, using the example above: user1 in OU group “Exchange Users”
and domain “example.com”
Security Select a Security option (either None, SSL, or TLS)
81
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Access Policy Edit the Access Profile you just created using the Visual Policy Editor
Edit
(See procedure below) Continue now with configuring the Access policy below.
2
If you are using BIG-IP version 11.3, you can optionally create a Kerberos SSO configuration for Outlook Anywhere. See Optional: Configuring the BIG-IP Access Policy
Manager for Outlook Anywhere with NTLM Authentication - BIG-IP version 11.3 or later only on page 97
3
If using the Exchange profile in 11.4 and later, you must remove any _sys_APM irules from the virtual server
4
Optional, only available in 11.4 and later, and only applicable if you created the Exchange profile.
82
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
3. Click the + symbol between Start and Deny. A box opens with options for different actions.
a. Click the Logon Page option button, and then the Add Item button at the bottom.
b. From the Split domain from full Username list, select Yes.
c. Configure the rest of the Logon Page properties as applicable, and then click Save.
b. I n the Active Directory properties box, from the Server list, select the AAA server you created using the table above. The rest
of the settings are optional. Click Save.
5. On the Successful path between AD Auth and Deny, click the + symbol.
a. Click the SSO Credential Mapping option button, and then click Add Item.
b. Configure the Properties as applicable for your configuration; we leave the settings at the defaults. Click the Save button.
6. O
n the fallback path between SSO Credential Mapping and Deny, click the Deny box. Click the Allow option button, and then
click Save. See screenshot below.
7. Click the yellow Apply Access Policy link in the upper left part of the window. You must apply an access policy before it takes effect.
3. I n the Definition section, copy and paste the following iRule, omitting the line numbers. If you used a different name for your
forms-based SSO Configuration when creating it based on the table above, use that name in line 3
1 when RULE_INIT {
2 ##replace exchange_forms_sso here with your forms-based SSO name
3 set static::OWA_FORM_BASE_SSO_CFG_NAME "exchange_forms_sso"
4 }
5 when ACCESS_ACL_ALLOWED {
6 set req_uri [HTTP::uri]
7 #selects the forms-based SSO when Outlook Web Access is detected
8 if { $req_uri contains "/owa/&reason=0" } {
9 WEBSSO::select $static::OWA_FORM_BASE_SSO_CFG_NAME
10 }
11 unset req_uri
12 }
Exchange 2013 only If using Exchange 2013, line 8 is: if { $req_uri contains "/owa" } {
83
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Configuration table for scenario 1: BIG-IP APM sending traffic to a remote BIG-IP LTM
If you are using the BIG-IP APM for scenario 1 with either SSL offload or SSL Bridging, use the following table to configure the APM. There
are additional procedures immediately following this table.
84
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
SSL Profile (Client) Select the Client SSL profile you created above
SSL Profile (Server) Select the Server SSL profile you created above (only for Scenario 2, SSL Bridging).
Access Profile Select the Access Profile you created above
BIG-IP APM iRules1 Enable the Append iRule you created on page 74.
Exchange virtual Enable the iRule you created to terminate inactive sessions
server Enable either the built-in _sys_APM_ExchangeSupport_OA_BasicAuth or sys_APM_ExchangeSupport_
(Main tab-->Local Traffic- OA_NTLMAuth Rule as depending on your auth method. This rule is necessary whether deploying Outlook
->Virtual Servers) Anywhere or not.1
Enable the iRule that chooses the SSO configuration you created (select_SSO_irule in our example)
Enable the APM session ID irule you created (edge-gateway-irule in our example)
Default Pool Select the Pool you created above
1
Do not attach the _sys_APM_ExchangeSupport_OA_BasicAuth iRule if you are using BIG-IP v11.4 and the Exchange profile.
3. In the Definition section, copy and paste the following iRule, omitting the line numbers.
1 when ACCESS_ACL_ALLOWED {
2 set sessionid [ACCESS::session data get "session.user.sessionid"]
3 HTTP::header insert APM_session $sessionid
4 }
5 when HTTP_RESPONSE {
6 if { [string tolower [HTTP::header values "WWW-Authenticate"]] contains "negotiate"} {
7 ONECONNECT::reuse disable
8 ONECONNECT::detach disable
9 ## disables NTLM conn pool for connections where OneConnect has been disabled
10 NTLM::disable
11 }
12 ## this command rechunks encoded responses
13 if {[HTTP::header exists "Transfer-Encoding"]} {
14 HTTP::payload rechunk
15 }
16 }
BIG-IP LTM iRule if all traffic goes through the BIG-IP APM
If all of your Exchange traffic goes through the BIG-IP APM, and you do not have internal users who go directly to the BIG-IP LTM, you must
modify the persistence iRule on the remote BIG-IP LTM to use the following iRule (and remove the existing persistence iRule).
Important This iRule is only necessary if all traffic is going through the BIG-IP APM. If you have internal users who go directly to the BIG-IP
LTM, do not use this iRule.
To create the persistence iRule if all traffic goes through the BIG-IP APM to the LTM
1. On the Main tab, expand Local Traffic, click iRules, and then click the Create button to create a new iRule.
2. In the Name box, type a unique name. In our example, we type edge-gateway-persist.
3. In the Definition section, copy and paste the appropriate iRule (omitting the line numbers), depending on your version of Exchange.
85
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
86
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
87
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
4. In the Definition section, copy and paste the following iRule:
1 when RULE_INIT {
2 set static::cookie_sessionid [format "sessionid=null; path=/; Expires=Thurs, 01-Jan-1970 00:00:00 GMT;"]
3 set static::cookie_cadata [format "cadata=null; path=/; Expires=Thurs, 01-Jan-1970 00:00:00 GMT;"]
4 }
5
6 when ACCESS_SESSION_STARTED {
7 if { [HTTP::uri] contains "UA=0" } {
8 ACCESS::session remove
9 }
10 }
11
12 when ACCESS_ACL_ALLOWED {
13 set apm_mrhsession [HTTP::cookie value "MRHSession"]
14 if { [table lookup $apm_mrhsession] == "EXCHANGE_LOGOUT" } {
15 ACCESS::session remove
16 table delete $apm_mrhsession
17 }
18 }
19
20 when HTTP_REQUEST {
21 set isset 0
22 if {[string tolower [HTTP::uri]] starts_with "/owa" } {
23 if {[string tolower [HTTP::uri]] contains "logoff" } {
24 ACCESS::session remove
25 HTTP::respond 302 Location "https://[HTTP::host]/vdesk/hangup.php3" "Set-Cookie" $static::cookie_sessionid "Set-Cookie" $static::cookie_cadata
26 } else {
27 if { [HTTP::uri] contains "UA=0" } {
28 set mrhsession [HTTP::cookie value "MRHSession"]
29 set isset 1
30 }
31 }
32 }
33 }
34 when HTTP_RESPONSE {
35 if { $isset == 1 } {
36 if { $mrhsession != "" && [HTTP::status] == 440 } {
37 table set $apm_mrhsession "EXCHANGE_LOGOUT"
38 return
39 }
40 }
41 }
5. Click Finished.
7. F
rom the Virtual Server list, click the name of the appropriate virtual server (either the BIG-IP APM virtual server, the combined virtual
server, or the separate OWA virtual server, depending on how you configured the BIG-IP system.
88
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
10. From the Available list, select the iRule you just created and then click Add (<<).
11. If deploying for BIG-IP APM, click the Up button to move the this iRule just below the <iapp-name>_sys_APM_
ExchangeSupport_OA_BasicAuth (or <iapp-name>_sys_APM_ExchangeSupport_OA_NtlmAuth if using NTLM for OA) rule.
If you are using BIG-IP version 11.4 and deploying with the BIG-IP APM Exchange profile, this step is not necessary.
1. On the Main tab, expand Local Traffic, click iRules, and then click the Create button.
2. In the Name box, give the iRule a unique name. We use apm-persistence-irule.
3. In the Definition section, copy and paste the appropriate iRule (omitting the line numbers), depending on your version of Exchange.
89
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
90
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Modifying the virtual server to use the iRules and Access Profile
The final task is to modify the BIG-IP LTM virtual server(s) to use the new persistence iRule (and remove any existing persistence iRules) ,
the terminate inactive sessions iRule, and add the Access Profile you created on BIG-IP APM.
If you created separate virtual servers, you must add the persistence iRule and Access Profile to all BIG-IP LTM virtual server for the HTTP-
based Client Access Services (Outlook Web App, Outlook Anywhere, ActiveSync, and Autodiscover). The terminate inactive sessions iRule
only needs to be assigned to the OWA virtual server.
91
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
1 when HTTP_REQUEST {
2 if { [HTTP::uri] contains "/ecp" } {
3 et response "<html><head><title>EAC Access Denied</title></head><body>We are sorry, but access to the Exchange
s
Administration Center is restricted to approved client IP addresses. Your IP address, [IP::client_addr], is not
approved.</body></html>"
5 if { [HTTP::header exists "Referer"] } {
6 if { [HTTP::header "Referer"] contains "rfr=owa" } {
7 pool my_iapp_2013_owa_pool
8 }
9 } elseif { [class match [IP::client_addr] equals "trustedAddresses"]} {
10 pool my_iapp_2013_owa_pool
11 } else {
12 HTTP::respond 200 content $response
13 }
14 unset response
15 }
16 }
92
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
1. On the Main tab, expand Access Policy, and click Access Profiles.
2. In the Access Policy list, find the row for the Access Policy created by the Exchange iApp template. This policy starts with the name
you gave the iApp, followed by _apm_access.
4. In the Copied Profile Name box, type a new name for this profile.
6. Continue with Editing the APM Access Policy if you copied the existing Access Policy on page 95.
Editing the APM Access Policy if you created a new Access Policy
Use this section to edit the Access Profile if you created a new Access Policy.
1. On the Main tab, expand Access Policy, and click Access Profiles.
2. L
ocate the Access Profile you created using the table above, and then, in the Access Policy column, click Edit. The VPE opens in a
new window.
3. Click the + symbol between Start and Deny. A box opens with options for different actions.
a. Click the Logon Page option button, and then the Add Item button at the bottom.
b. From the Split domain from full Username list, select Yes.
c. Configure the rest of the Logon Page properties as applicable, and then click Save.
b. In the Active Directory properties box, from the Server list, select the AAA server created by the iApp.
5. On the Successful path between AD Auth and Deny, click the + symbol.
a. Click the Empty option button, and then click Add Item.
93
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
6. On the is EAC path (if you did not modify the name, this is Branch Rule 1) between EAC URI Check and Deny click the + symbol.
a. Click AD Query, and then click Add Item.
c. From the Server list, select the AAA server created by the iApp.
f. In the Name box, delete any existing text, and then type Organization Management.
h. Click the Delete (x) button to the right of the User's Primary Group ID is box.
l. In the User is a member of box, type CN=Organization Management,OU=Microsoft Exchange Security
Groups,DC=example,DC=com.
7. On the fallback path between EAC URI Check and Deny, click the + symbol.
a. Click SSO Credential Mapping, and then click Add Item.
c. Click Save.
d. On the fallback path between SSO Credential Mapping and Deny, click the Deny box/link.
8. On the Organization Management path, between EAC AD Query and Deny click +.
a. Click SSO Credential Mapping, and then click Add Item.
c. Click Save.
d. On the fallback path between SSO Credential Mapping and Deny, click the Deny box/link.
94
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
9. C
lick the yellow Apply Access Policy link in the upper left part of the window. You must apply an access policy before it takes
effect.
10. Continue with Modifying the virtual server to use the new Access Policy on page 96.
When you are finished, your VPE should look like the following:
Editing the APM Access Policy if you copied the existing Access Policy
Use this section to edit the Access Profile if you made a copy of the Access Policy created by the iApp template.
1. On the Main tab, expand Access Policy, and click Access Profiles.
2. L
ocate the Access Profile you created using the table above, and then, in the Access Policy column, click Edit. The VPE opens in a
new window.
3. On the Successful path between AD Auth and SSO Credential Mapping, click the + symbol.
a. Click the Empty option button, and then click Add Item.
4. On the is EAC path (if you did not modify the name, this is Branch Rule 1) between EAC URI Check and Deny click the + symbol.
a. Click AD Query, and then click Add Item.
95
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
c. From the Server list, select the AAA Server created by the iApp.
f. In the Name box, delete any existing text, and then type Organization Management.
h. Click the Delete (x) button to the right of the User's Primary Group ID is box.
l. In the User is a member of box, type CN=Organization Management,OU=Microsoft Exchange Security
Groups,DC=example,DC=com.
5. On the Organization Management path, between EAC AD Query and Deny click the + symbol.
a. Click SSO Credential Mapping, and then click Add Item.
c. Click Save.
d. On the fallback path between SSO Credential Mapping and Deny, click the Deny box/link.
6. C
lick the yellow Apply Access Policy link in the upper left part of the window. You must apply an access policy before it takes
effect.
7. Use the following procedure to add the Access Policy to the virtual server.
1. On the Main tab, expand Local Traffic and then click Virtual Servers.
2. C
lick the name of the appropriate virtual server. This is either the single virtual server for all HTTP-based CAS services or the separate
virtual server for OWA.
3. In the Access Policy section, from the Access Profile list, select the Access profile you just modified.
4. Click Update.
96
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Optional: Configuring the BIG-IP Access Policy Manager for Outlook Anywhere with NTLM Authentication - BIG-IP
version 11.3 or later only
F5’s Access Policy Manager (APM) module supports NTLM authentication for Outlook clients using the RPC-over-HTTP protocol (Outlook
Anywhere) in version 11.3 and later.
Before configuring BIG-IP system, you must perform prerequisite configuration steps on the Exchange Server(s) and Active Directory
servers. See Appendix E: Active Directory and Exchange Server configuration for NTLM on page 105.
Use the following table for guidance on configuring the BIG-IP APM.
BIG-IP Object Non-default settings/Notes
97
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
11.4 only: In the left pane of the box, click Outlook Anywhere
Exchange Profile1 Front End Authentication NTLM
(continued) SSO Configuration From the OAB SSO Configuration list, select the Kerberos SSO Configuration you created above.
Name Type a unique name. We use exchange-kerberos-access.
Access Profile
(Main tab-->Access Microsoft Exchange 2 If you created the Exchange profile, select the profile you created from the list.
Policy-->Access Profiles) SSO Configuration Select name of Kerberos SSO configuration you created above
Access Policy
Edit Edit the Access Profile. Continue now with configuring the Access Profile on this page.
(See procedure below)
1
If using the Exchange profile in 11.4 and later, you must remove any _sys_APM irules from the virtual server
2
Optional, only available in 11.4 and later, and only applicable if you created the Exchange profile.
Creating the NTLM Auth Configuration from the TMSH command line
As noted in the preceding table, you must create the NTLM Auth Configuration object in the same partition and folder location as the virtual
server to which the Access Profile is applied.
If you are manually reconfiguring the BIG-IP system from a previous iApp deployment, you need to create this object from the tmsh
command line. This is only necessary if configuring the BIG-IP system from a previous iApp deployment.
For example, if the iApp is named my_exchange_iapp, the domain controller FQDN is dc.mydomain.com, the machine account is
bigip_machine_acct, and the virtual server is named my_exchange_iapp_combined_https, the tmsh commands is:
Creating the Access profile for Outlook Anywhere on a separate virtual server
Use the following procedure for configuring the Access Policy for a separate Outlook Anywhere virtual server.
To configure the Access Policy for Outlook Anywhere on a separate virtual server
1. On the Main tab, expand Access Policy, and click Access Profiles.
2. Locate the Access Profile you created using the table above, and then, in the Access Policy column, click Edit. The VPE opens.
3. Click the + symbol between Start and Deny. A box opens with options for different actions.
a. Click the Client for MS Exchange option button, and then the Add Item button at the bottom.
b. Click the Save button.
4. O
n the Client for MS Exchange path, click the + symbol between Client for MS Exchange and Deny. A box opens with options for
different actions.
98
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
a. Click the NTLM Auth Result Check option button, and then the Add Item button at the bottom.
5. On the Successful path between NTLM Auth Result Check and Deny, click the + symbol.
a. Click the SSO Credential Mapping option button, and then click Add Item.
b. C
onfigure the Properties as applicable for your configuration. In our example, we leave the settings at the defaults. Click the
Save button.
6. O
n the fallback path between SSO Credential Mapping and Deny, click the Deny box. Click the Allow option button, and then
click Save.
7. On the Fallback path between NTLM Auth Result Check and Deny, click the + symbol.
a. Click the Logon Page option button, and then the Add Item button at the bottom.
b. From the Split domain from full Username list, select Yes.
c. Configure the rest of the Logon Page properties as applicable, and then click Save.
8. On the Fallback path between Logon Page and Deny, click the + symbol.
a. In the Authentication section, click the AD Auth option button, and click Add Item.
b. I n the Active Directory properties box, from the Server list, select the AAA Server you created using the table above. The
rest of the settings are optional.
c. Click Save.
9. On the Successful path between AD Auth and Deny, click the + symbol.
a. Click the SSO Credential Mapping option button, and then click Add Item.
b. C
onfigure the Properties as applicable for your configuration. In our example, we leave the settings at the defaults. Click the
Save button.
10. O
n the fallback path between SSO Credential Mapping and Deny, click the Deny box. Click the Allow option button, and then
click Save.
11. C
lick the yellow Apply Access Policy link in the upper left part of the window. You must apply an access policy before it takes effect.
Your VPE should look like the following example.
This completes the Access Policy for the separate virtual server scenario. Continue with Enabling the ECA Profile on Outlook Anywhere
Virtual Server on page 101.
Creating the Access profile for Outlook Anywhere on a combined virtual server
Use the following procedure for configuring the Access Policy if you configured Outlook Anywhere as a part of a combined virtual server.
99
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
To configure the Access Policy for Outlook Anywhere on a combined virtual server
1. On the Main tab, expand Access Policy, and click Access Profiles.
2. L
ocate the Access Profile you created using the table above, and then, in the Access Policy column, click Edit. The VPE opens in a
new window.
3. Click the + symbol between Start and Deny. A box opens with options for different actions.
a. Click the Client for MS Exchange option button, and then the Add Item button at the bottom.
4. O
n the Client for MS Exchange path, click the + symbol between Client for MS Exchange and Deny. A box opens with options for
different actions.
a. Click the NTLM Auth Result Check option button, and then the Add Item button at the bottom.
5. On the Successful path between NTLM Auth Result Check and Deny, click the + symbol.
a. Click the SSO Credential Mapping option button, and then click Add Item.
b. C
onfigure the Properties as applicable for your configuration. In our example, we leave the settings at the defaults. Click the
Save button.
6. O
n the fallback path between SSO Credential Mapping and Deny, click the Deny box. Click the Allow option button, and then
click Save.
7. On the Fallback path between NTLM Auth Result Check and Deny, click the + symbol.
a. Click the Logon Page option button, and then the Add Item button at the bottom.
b. From the Split domain from full Username list, select Yes.
c. Configure the rest of the Logon Page properties as applicable, and then click Save.
8. On the Fallback path between Logon Page and Deny, click the + symbol.
a. In the Authentication section, click the AD Auth option button, and click Add Item.
b. I n the Active Directory properties box, from the Server list, select the AAA Server you created using the table above. The
rest of the settings are optional.
c. Click Save.
9. On the Successful path between AD Auth and Deny, click the + symbol.
a. Click the SSO Credential Mapping option button, and then click Add Item.
b. C
onfigure the Properties as applicable for your configuration. In our example, we leave the settings at the defaults. Click the
Save button.
10. O
n the fallback path between SSO Credential Mapping and Deny, click the Deny box. Click the Allow option button, and then
click Save.
11. On the Fallback path between Client for MS Exchange (the first box of the VPE) and Deny, click the + symbol.
a. Click the Logon Page option button, and then the Add Item button at the bottom.
b. From the Split domain from full Username list, select Yes.
c. Configure the rest of the Logon Page properties as applicable, and then click Save.
12. On the bottom Fallback path between the new Logon Page and Deny, click the + symbol.
100
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
a. In the Authentication section, click the AD Auth option button, and click Add Item.
b. I n the Active Directory properties box, from the Server list, select the AAA Server you created using the table above. The
rest of the settings are optional.
c. Click Save.
13. On the Successful path between AD Auth and Deny, click the + symbol.
a. Click the SSO Credential Mapping option button, and then click Add Item.
b. C
onfigure the Properties as applicable for your configuration. In our example, we leave the settings at the defaults. Click the
Save button.
14. O
n the fallback path between SSO Credential Mapping and Deny, click the Deny box. Click the Allow option button, and then
click Save.
15. C
lick the yellow Apply Access Policy link in the upper left part of the window. You must apply an access policy before it takes effect.
Your VPE should look like the following example.
This completes the Access Policy for the combined virtual server.
To attach the ECA profile to the virtual server from the command line
2. Type tmsh
For example:
modify ltm virtual my_exchange_iapp.app/my_exchange_iapp_combined_https profiles add { eca }
i Important
You must have enabled the ECA profile on the Outlook Anywhere virtual server as described above before
applying the system iRule in the next step. Do NOT enable this profile or attach the system iRule if using BIG-IP
version 11.4 and the Exchange Profile.
101
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
7. Click Finished.
Access Policy example when using both EAC restricted access and NTLM for Outlook Anywhere
Using both EAC restricted access and NTLM for Outlook Anywhere in a single Access Policy is an acceptable configuration, although the
step by step procedure is outside the scope of this document (use the iApp for this scenario if you need the walkthrough). The following
screenshot shows what the VPE should look like with both EAC restricted access and NTLM for Outlook Anywhere.
102
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
F5 testing has shown that 300 seconds (5 minutes) is generally sufficient to allow a rebooted Exchange Client Access server to fully start all
services and be ready to handle a full load of traffic, but that time is highly dependent on local conditions. You may want to adjust the time
period up or down in your environment based on your server capacity and load.
103
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
On fast networks, connect using HTTP first, then connect using TCP/IP Not selected Selected
On slow networks, connect using HTTP first, then connect using TCP/
Selected Selected
IP
You must replace ArrayName with the name you want for your Client Access Array, replace outlook.example.com with the FQDN you have
configured in DNS, and replace SiteName with the name of your Active Directory site.
You must modify the attributes of any pre-existing mailbox databases to use the new array. Use the Exchange Management Shell to run the
following command for each database in your array:
You must specify the correct mailbox databases for your site, and the correct FQDN for your Client Access Array. You can only configure
one Client Access Array (and thus one FQDN and one BIG-IP virtual server) per site.
Important note about BIG-IP health monitors that use Exchange server accounts
The monitors described in this section require a valid Exchange server account and associated mailbox specifically for monitoring purposes.
The accounts used for authentication must be associated with a valid mailbox. If authentication should fail for any reason, for instance, the
account is locked, the Mailbox server associated with that account is down for maintenance, or the account password is changed, the
monitors will mark all Client Access servers down for the relevant service (Autodiscover, ActiveSync, or Outlook Anywhere). Maintenance of
the accounts and associated mailboxes thus becomes an integral part of your health status checks.
If you choose to use this method, we recommend using at least two separate instances of the monitor, with Mailboxes located on different
servers. You should then configure the pool to only mark members down if all monitors fail.
You should create accounts (and associated mailboxes) for monitoring that are not accessed by actual users and that do not have
privileged access anywhere else in your network. Because you have to store the user name and password in plain text on your BIG-IP
devices, make sure the credentials are not used elsewhere in your organization for anything other than monitoring.
We strongly recommend creating a mailbox account(s) specifically for use in the monitor(s).
104
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Note
This section provides guidance only; for specific instructions, consult the appropriate documentation. F5 cannot
be responsible for improper configuration of Active Directory or Microsoft devices.
F5 recommends that you do not use an account with domain administrator permissions for delegation, and that you select the User
cannot change password and Password never expires check boxes under Account Properties.
105
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
The servicePrincipalName value should match the user logon name of the delegation account.
106
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
107
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
DNS reverse zone configured for EDGE to LTM scenario (10.133.90.63 is the IP address of internal LTM virtual server, returning the host
name matching the SPN created in the next section):
108
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Perform this step for every host name that you will be accessing using NTLM client authentication, which includes Autodiscover by default.
The command to set an SPN for Autodiscover is setspn HTTP/autodiscover.mydomain.com where you substitute your Autodiscover
DNS name for autodiscover.mydomain.com. Also, you must ensure that the previously created delegation account is allowed to log on for
all of the SPNs you just created (see Enabling Delegation for Account on page 106).
Based on reverse DNS lookups or the SPN pattern specified in the Kerberos SSO configuration on page 97, APM will construct a
Kerberos ticket request to the Active Directory domain controller for the SPN HTTP/oa.extest.local. You must allow Kerberos constrained
delegation for HTTP/oa.extest.local via the Delegation tab within the properties of the previously created user account:
Finally, you must change the Application Pool Identity for the Application Pool used by Outlook Anywhere, Autodiscover, and Exchange Web
Services to use the previously created delegation user account.
Begin by opening IIS Manager and selecting Application Pools > DefaultAppPool > Advanced Settings.
109
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Under Process Model, click Advanced Settings and then click ... to the right of Identity.
Enter the credentials of the previously created user account for delegation, in DOMAIN\user format:
110
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
Repeat this process for the MSExchangeAutodiscoverAppPool and MSExchangeServicesAppPool. You need to restart Internet
Information Services for these changes to take effect.
111
112
DEPLOYMENT GUIDE
Exchange Server 2010 and 2013
1.0 New deployment guide for the f5.microsoft_exchange_2010_2013_cas.v1.2.0 iApp template. 08-02-2013
- In "Appendix C: Manual Configuration Tables", added the section Creating an iRule when using a SNAT pool on page 79
for deployments using SNAT Pool(s), and linked to this section from each applicable configuration table. No changes are
1.1 08-08-2013
required to configurations using the iApp, the template creates this iRule automatically.
- Expanded the descriptions of the deployment scenarios which include BIG-IP APM on page 6 and page 7.
- Added the section Microsoft Exchange Remote Connectivity Analyzer fails to successfully run the FolderSync command to
Troubleshooting on page 53. Only necessary on versions prior to 11.4.
- Added to the description of the configuration and benefits of the BIG-IP system on the first page, calling out the fact that the
1.2 09-10-2013
BIG-IP system performs as a reverse proxy (in addition to other functions) using the configuration in this guide.
- Added a note to Creating the iRule to terminate inactive APM sessions on page 88 stating the iRule is only effective if using
Forms-based authentication for OWA.
1.3 Added iApp gives an error when using Analytics and deploying POP3 and IMAP4 on page 54 to the troubleshooting section 09-27-2013
-A
dded ActiveSync and/or Autodiscover aren't working after deploying the iApp for separate virtual servers and using APM on
1.4 page 55 to the troubleshooting section. Updated the separate virtual server configuration tables to use the proper iRules. 10-08-2013
- Added support for BIG-IP version 11.4.1
- Updated the iRule in the manual configuration section for Creating the iRule to terminate inactive APM sessions on page
88 to match the iRule created by the iApp template.
-A
dded Clients receiving error message when using BIG-IP APM with OWA 2013 and IE10 or Google Chrome on page 55
to the troubleshooting section.
1.5 - Added a note to the manual configuration tables that the _sys_APM_ExchangeSupport_OA_NTLMAuth iRule is only 10-22-2013
applicable if using BIG-IP v11.3.x (and NTLM authentication).
-A
dded Experiencing issues with iOS devices and ActiveSync when the BIG-IP system is behind a device performing NAT
on page 56 to the troubleshooting section. Updated the persistence iRules in the manual configuration section with the
resolution described in the troubleshooting section.
- Added support for Exchange 2013 CU3
-A
dded Advanced monitors for Autodiscover, EWS, and Outlook Anywhere only support Basic and NTLMv1 authentication on
page 56 in the Troubleshooting section. Added cross references to this section from the Prerequisites and the applicable
1.6 11-27-2013
section of the iApp walkthrough.
-A
dded Creating the Data Group and iRule for securing EAC access if not using BIG-IP APM on page 57 to Troubleshooting.
Added cross references to this section from the Prerequisites and the applicable section of the iApp walkthrough.
Added an additional entry to the troubleshooting section concerning Guest accounts on the BIG-IP system that have been
1.7 12-23-2013
explicitly granted tmsh command line access. See Troubleshooting on page 53.
Added an additional entry to the troubleshooting section concerning authentication issues when deploying the iApp using
1.8 01-09-2014
BIG-IP APM for client-side NTLM for Outlook Anywhere. See Troubleshooting on page 53.
- Added an additional entry to the troubleshooting section concerning iOS users experiencing certificate errors after deploying
1.9 the template for ActiveSync. See Troubleshooting on page 53. 01-22-2014
- Updated the applicable iRules to use SHA256 (replacing CRC32), as it is more secure.
2.0 - Added support for BIG-IP version 11.5 01-31-2014
2.1 Removed a comment line about TMM sending gratuitous ARPs during failover from the SNAT Pool iRule on page 79 02-20-2014
- Added support for Microsoft Exchange 2013 SP1, which includes support for SSL offload. Modified all guidance for SSL
2.2 offload to include 2013 SP1. 03-14-2014
- Added an optional section for MAPI over HTTP on page 49 which was introduced in 2013 SP1.
2.3 - Added support for BIG-IP version 11.5.1 03-19-2014
- Added an additional entry to the troubleshooting section concerning slow response times for calendar functionality and
2.4 03-28-2014
reduced responsiveness. See page 59.
F5 Networks, Inc. 401 Elliott Avenue West, Seattle, WA 98119 888-882-4447 www.f5.com
©2014 F5 Networks, Inc. All rights reserved. F5, F5 Networks, the F5 logo, and IT agility. Your way., are trademarks of F5 Networks, Inc. in the U.S. and in certain other countries. Other F5 trademarks are identified
at f5.com. Any other products, services, or company names referenced herein may be trademarks of their respective owners with no endorsement or affiliation, express or implied, claimed by F5. 0412