We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Load Balancer

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

  • Last updated on

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

If you plan to use a two-armed configuration, refer to How to Deploy Exchange 2010 in a Two-Armed Configuration.

In a one-armed configuration, the ports to be used by internal Outlook® clients when communicating with the Exchange 2010 server using RPC must be pre-configured on both Exchange 2010 and the Barracuda Load Balancer.

Step 1. Configure Exchange 2010 to use a Static Port

By default, the Exchange 2010 RPC client dynamically selects a port between 1024 and 65535. To allow for a one-armed deployment, configure Exchange to use a static port instead.

Refer to the Microsoft TechNet online library article Load Balancing Requirements of Exchange Protocols for more detailed instructions on configuring Exchange 2010 with static ports and hardware load balancers.

On each CAS server, complete the following:

1a. Configure the static port in the registry. Open the Registry Editor by typing regedit in the Start menu. Add a DWORD (32-bit) value named TCP/IP Port under HKEY_LOCL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeRpc\ParametersSystem
You may need to create the ParametersSystem key prior to adding the DWORD registry value. In this case, when prompted, change the Base to Decimal and set the value data to 65500 (or a port of your choice between 1024 and 65535):
registry_editor.jpg
If you have Public Folders in your deployment, you must also repeat this step on each server with the mailbox role installed that hosts a Public Folder.

1b. Change the port that clients use to connect for directory access. On each CAS server, complete the following:

  1. If you are running Microsoft Exchange 2010 RTM (including RTM Rollup 1 - 4), follow these instructions:
    1. In Windows Explorer, navigate to the Microsoft.exchange.addressbook.service.exe.config file. This file is located in the \Bin folder in the root directory of your Exchange 2010 install.
    2. Open this file using Notepad.
    3. Change the default value of 0 on line 13 to 65501 (or a port of your choice within the prior specified range) so it appears as follows, including the quotations: 
      <add key="RpcTcpPort" value="65501" />
  2. If you are running Microsoft Exchange 2010 SP1, follow these instructions:
    1. Configure the static port in the registry. To do this, open the Registry Editor by typing regedit in the Start menu. 
    2. Add a String value (REG_SZ) with Value name RpcTcpPort under
      HKEY_LOCL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchangeAB\Parameters
      You may need to create the Parameters key prior to adding the REG_SZ registry value. In this case, change the value data to 65501 (or a port of your choice between 1024 and 65535):
      registry_editor2.jpg

1c. Restart the Microsoft Exchange Address Book and the Microsoft Exchange RPC Client Access services on all CAS and Mailbox servers that you modified.

1d. To test that your Client Access servers are using ports 65500 and 65501, open a Windows command prompt and run netstat –na

1e. In the output, look for TCP entries marked as LISTENING with the ports 65500 and 65501. You will see an entry marked as LISTENING for 0.0.0.0:65500 and 0.0.0.0:65501.

Step 2. Configure CAS Services on the Barracuda Load Balancer

On each active Barracuda Load Balancer that handles traffic for CAS Services, complete the following steps to configure CAS Services for Exchange 2010:

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

2b. Add each Service listed in Table 1 and Table 2 by following these steps. Use the Basic View. In the Add New Service pane, if you are in the Advanced View, select Switch to Basic View.

  1. Enter the Service Name.
  2. Enter the Virtual IP Address specified in the table.
  3. Select the protocol, and enter the Port for the Service from the table.
  4. Enter the Real Servers IP addresses for each server in the CAS array.

Table 1. Required Services.

Service NameVirtual IP AddressProtocolService TypeService PortReal Server PortMonitor Port
MAPI / DCOM

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

TCPTCP Proxy13513565500
MAPI / RPC Client Access

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

TCPTCP Proxy655006550065500

MAPI / Global Address Book

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

TCPTCP Proxy655016550165501
Exchange Services HTTPS

VIP address for FQDN that clients use to access CAS array
e.g. exchange.domain.local

TCPLayer 7 - HTTPS44380*80*
Exchange Web Services HTTP Redirect VIP address for FQDN that clients use to access CAS array

e.g. exchange.domain.local

TCP  Layer 7 - HTTP80 N/A*N/A 
 *Note: If your deployment requires end-to-end encryption of Exchange traffic, the Real Server and Monitor Port for the Exchange Services HTTPS service is 443, not 80.      

Table 2. Optional Services.

Service NameVirtual IP AddressProtocolService TypeService PortReal Server PortMonitor Port
IMAP4 (optional)

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

TCPTCP Proxy143143143
IMAP4 SSL (optional)

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

TCPTCP Proxy993993993
POP3 (optional)

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

TCPTCP Proxy110110110
POP3 SSL (optional)

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

TCPTCP Proxy996996996

2c. Once all of the Services are created, edit each Service as specified:

  1. On the BASIC > Services page, click the Edit icon for the Service you wish to edit.
  2. In the Service Detail page, for each service in the following table, edit the settings and save your changes:
Service NameService Detail Page Settings
Exchange Web Services (Port 443)
  • In the General section, set Service Type to Layer 7 - HTTPS.
  • In the SSL Offloading section, in the Certificate menu, select the certificate that you uploaded in Prepare Your Environment for SSL Offloading.
  • In the Persistence section, set Persistence Type to HTTP Header, set Persistence Time to 1200, and set Header Name to Authorization.
  • In the Advanced Options section, set Session Timeout to 1200.
Exchange Web Services HTTP RedirectIn the General section, set Service Type to Layer 7 - HTTP. Set Enable HTTP Redirect to Yes.

IMAP4 (Port 143)

IMAP4 / SSL (Port 993)

POP3 (Port 110)

POP3 SSL (Port 996)

In the General section, set Service Type to TCP Proxy. Persistence is not required for these Services as they are transactional based.

MAPI / RPC Client Access (Port 65500)

MAPI / DCOM (Port 135)

MAPI / Global Address Book (Port 65501)

  • In the General section, set Service Type to TCP Proxy.
  • In the Persistence section, set Persistence Time to 1200. Set Persistence Type to Client IP.
  • In the Advanced Options section, set Session Timeout to 1200.

2d. Use the following steps to change the port and Server Testing Method for every Real Server associated with the Exchange Web Services Service:

  1. On the BASIC > Services page, for each Real Server associated with the Exchange Web Services Service, click the Edit icon; the Real Server Detail page displays.
  2. In the Real Server Detail section, set Port to 80.
  3. 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.aspx
      If 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 the Status Code to 200 and set the Test Delay to 30

2e. Create two content rules for the Exchange Web Services Service to maintain persistence for Outlook Web Access and the Exchange Control Panel.

On the BASIC > Services page, click Rule in the Add column of the Exchange Web Services Service. On the Add Rule page, configure the rule.

  • Use the following table to add the rule for Outlook Web Access:
Rule Parameter NameRule Setting
Rule NameOWA
Host Match*
URL Match/owa/*
Persistence TypeHTTP Cookie
Cookie Namesessionid
Persistence Time (Seconds)1200
  •  Click Save Changes.

Use the following table to add the rule for the Exchange Control Panel. On the BASIC > Services page, click Rule in the Add column of the Exchange Web Services Service. On the Add Rule page, configure the rule.

Rule Parameter NameRule Setting
Rule NameECP
Host Match*
URL Match/ecp/*
Persistence TypeHTTP Cookie
Cookie Namesessionid
Persistence Time (Seconds)1200
  •  Click Save Changes.

If you are using Outlook Anywhere (HTTPS only, not RPC over HTTPS), you must create an extra content rule.

For Outlook Anywhere, use the following table to add the rule for the Offline Address Book:

Rule Parameter NameRule Setting
Rule NameOAB
Host Match*
URL Match/oab/*
Persistence TypeHTTP Cookie
Cookie Namesessionid
Persistence Time (Seconds)1200

outlook_anywhere.jpg

2f. If Real Servers are segregated and secure in your network, we recommend not enabling back-end SSL for each Real Server thereby avoiding additional processing load. But if you require end-to-end encryption of Exchange Web Services data, direct the Barracuda Load Balancer to re-encrypt traffic before sending it to the Real Server:

  1. On the BASIC > Services page, for each Real Server associated with the Exchange Web Services Service, click the Real Server Edit icon; the Real Server Detail page displays.
  2. In the Real Server Detail section, set Port to 443.
  3. In the SSL section, set Enable HTTPS/SSL to Yes.


Traffic is now encrypted using the same key uploaded and created from your Exchange CAS array. If this setting is enabled, Exchange Web Services will no longer need to accept unencrypted sessions on port 80. This increases processing load on both the Barracuda Load Balancer and all CAS Array members.

Step 3. Configure Hub Transport Services on the Barracuda Load Balancer

On each active Barracuda Load Balancer that handles traffic for Hub Transport Services, complete the following steps to configure Hub Transport Services for Exchange 2010.

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

3b. Using the following table, add the SMTP Service and, optionally, the SMTP / SSL Service. To add a Service (use the Basic View. These instructions assume you do not Switch to Advanced View):

  1. In the Service Name box, enter the name for the Service.
  2. Enter the Virtual IP Address specified in the table.
  3. Select the protocol and enter the Port for the Service in the table.
  4. In the Real Servers box, if your Real Servers are consolidated with both the CAS and HUB roles installed, enter the IP address for each Service you create. If the Hub Transport role is installed on separate servers from the CAS role, enter the IP addresses of only the servers with the Hub role installed. The created Services load balance the SMTP traffic to the Hub transport servers for incoming client SMTP connections.

    Exchange Hub Transport should never be configured to communicate with other internal Microsoft Exchange Hub Servers via the Barracuda Load Balancer. The Service on the Barracuda Load Balancer should only be used for client connections or inbound connections from other organizations.

Service NameVirtual IP AddressProtocolService TypeService PortReal Server PortMonitor Port
SMTP

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

TCPTCP Proxy252525
SMTP / SSL (optional)

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

TCPTCP Proxy587587587

3c. To change the Service type for the SMTP and SMTP / SSL Services to TCP Proxy:

  1. On the BASIC > Services page, click the Edit icon for the Service.
  2. In the Service Detail page, in the General section, set the value of Service Type to TCP Proxy.
  3. Save your changes.

Step 4. Configure a Rewrite Rule

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

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

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

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

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

4d. Click Add.

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


 If you are using Outlook Anywhere (HTTPS only, not RPC over HTTPS), you must create an extra content rule for the Offline Address Book.

Last updated on