How to Deploy Microsoft Exchange Server 2010 in a Two-Armed Configuration

Last updated on 2016-05-06 13:02:08

Before completing a two-armed configuration, verify you have completed all of the steps in Microsoft Exchange Server 2010 Deployment.

If you plan to use a one-armed configuration, go to How to Deploy Exchange 2010 in a One-Armed Configuration.

In a two-armed configuration, create Services for Exchange Services on the active Barracuda Load Balancer by doing the following steps.

Step 1. Create Services

1a. Log into the Barracuda Load Balancer, and go to the BASIC > Services page.

1b. For each entry in the following table, add a Service:

Enter the Service Name.
Enter the Virtual IP Address specified in the table.
Select the protocol, and enter the Port specified for the Service in the table.
Enter the IP address of each real server in the CAS array under Real Servers.

Service Name Virtual IP Address Protocol Service Type Service Port Real Server Port Monitor Port

Exchange

Service Name	Virtual IP Address	Protocol	Service Type	Service Port	Real Server Port	Monitor Port
Exchange	VIP address for FQDN that resolves to CAS array e.g. `exchange.domain.local` Note: This service is helpful in cases where there is no port restriction.	TCP	Layer 4	ALL	N/A	443
OWA - HTTPS	VIP address for FQDN that clients use to access OWA e.g. `owa.domain.local` Note: This service is helpful if there are port restrictions, and traffic is allowed only for port 443.	TCP	Layer 7 - HTTPS	443	80	80
HTTP Redirect	VIP address for FQDN that clients use to access OWA e.g. `owa.domain.local` Note: This service is needed to automatically redirect the users to the HTTPS service.	TCP	Layer 7 - HTTP	80	N/A (Redirect Service)	80

VIP address for FQDN that resolves to CAS array
e.g. exchange.domain.local

Note: This service is helpful in cases where there is no port restriction.

TCP

Layer 4

ALL

N/A

443

OWA - HTTPS

VIP address for FQDN that clients use to access OWA
e.g. owa.domain.local

Note: This service is helpful if there are port restrictions, and traffic is allowed only for port 443.

TCP

Layer 7 - HTTPS

443

HTTP Redirect

VIP address for FQDN that clients use to access OWA
e.g. owa.domain.local

Note: This service is needed to automatically redirect the users to the HTTPS service.

TCP

Layer 7 - HTTP

N/A (Redirect Service)

1c. Add the following Services if you have deployed the Hub Transport Role on separate servers from the servers with the CAS Role. The Services in the following table are optional and depend on your environment.

Service Name	Virtual IP Address	Protocol	Service Type	Service Port	Real Server Port	Monitor Port
SMTP	VIP address for FQDN that resolves to HUB Services e.g. `smtp.domain.local`	TCP	Layer 4	25	25	25
SMTP / SSL (optional)	VIP address for FQDN that resolves to HUB Services e.g. `smtp.domain.local`	TCP	Layer 4	587	587	587

1d. Once all of the Services are created, use the following steps to edit the settings:

On the BASIC > Services page, for each Service, click the Edit icon to edit the settings.
In the Service Detail page, for each service in the following table, edit the settings and save your changes:

Service Name	Service Detail Page Settings
Exchange	In the Persistence section, set Persistence Time (Seconds) to 1200.
OWA - HTTPS	In the General section, set the value of Service Type to Layer 7 - HTTPS. In the SSL Offloading section, in the Certificate menu, select the certificate that you uploaded in Preparing Your Environment for SSL Offloading. In the Persistence section, set Persistence Time to 1200. Set Persistence Type to HTTP Header. In the Header Name field, set the value to Authorization. In the Advanced Options section, set Session Timeout to 1200.
HTTP Redirect	In the General section, set the value of Service Type to Layer 7 - HTTP. Set Enable HTTP Redirect to Yes.

1e. Change the port and Server Testing Method for every Real Server associated with the OWA – HTTPS / Outlook Anywhere Service:

On the BASIC > Services page, click the Edit icon for each Real Server associated with the OWA - HTTPS Service; The Real Server Detail page displays.
In the Real Server Detail section, set Port to 80.
In the Server Monitor section:

- Set the Testing Method to Simple HTTP.
- Set the Port to 80.
- Change the Test Target to
  /owa/auth/logon.aspxIf you have modified the path of logon.aspx from the Exchange 2010 default, use the modified path in the Test Target.
- Change Test Match to
  2006 Microsoft Corporation
- Change Additional Headers to
  User-Agent: Barracuda Load Balancer Server Monitor
- Set theStatus Code to 200 and set the Test Delay to 30.

1f. Update TCP timeout values on the Barracuda Load Balancer:

Log into the Barracuda Load Balancer, and go to the ADVANCED > System Settings page.
Set the TCP Connections Timeout and TCP Closed ConnectionsTimeout to 1200 seconds.

Step 2. Configure a Rewrite Rule

Use the following steps to configure a rewrite rule to add '/OWA' to the end of the URL:

2a. Log into the Barracuda Load Balancer, and go to the WEBSITES > URL Rewrites page.

2b. In the Layer 7 - HTTP Services section, select the newly created service.

2c. In the HTTP Request Rewrite section, create a new rule, for example OWA:

In the Rule Order field, enter 3
From the Action drop-down menu, select Redirect URL
Leave the Header Name field blank.
In the Old Value field, enter /
In the Rewrite Value field, enter slash (/) and the rule name, for example /OWA
In the Rewrite Condition field, enter *

2d. Click Add.

Your installation is complete. Continue to How to Test the Microsoft Exchange Server 2010 Deployment Configuration.