Install and Configure Exchange 2010 - Part 3

In this post, i'm going to show you some basic configuration for Hub Transport role.

Hub Transport Server Role Configurations
1. Acceptance Domain Configuration

An accepted domain is any Simple Mail Transfer Protocol (SMTP) namespace for which a Microsoft Exchange organization sends or receives e-mail. Accepted domains include those domains for which the Exchange organization is authoritative. An Exchange organization is authoritative when it handles mail delivery for recipients in the accepted domain. Accepted domains also include domains for which the Exchange organization receives mail and then relays it to an e-mail server that is outside the AD directory service forest for delivery to the recipient.

2. E-mail Address Policy Configuration

3. Send Connector Configuration

The Send connectors are configured on servers that are running Microsoft Exchange Server 2010 and that have Hub Transport server roles installed. The Send Connector represents a logical gateway through which outbound messages are sent.

4. Receive Connector Configuration
Exchange 2010 transport servers require Receive connectors to receive messages from the Internet, from e-mail clients, and from other e-mail servers. Receive connectors represent a logical gateway through which all inbound messages are received.

On the hub transport servers, two receive connectors are created automatically during setup Exchange 2010. To establish mail flow to and from the Internet through a Hub Transport server, an additional receive connector has been created and configured to allow anonymous connections.

• Client EXCH01 / EXCH02 = that is configured to receive messages from all remote IP addresses through SMTP port 587. This connector is used to accept SMTP connections from non-MAPI clients and the usage type for this connector is Internal.
• Default EXCH01 / EXCH02 = that is configured to accept messages from all remote IP addresses through SMTP port 25.
• SMTP Relay EXCH01 / EXCH02 = that is configured to accept messages from application servers.

NOTE: Both EXCH01 and EXCH02 have the identical configuration.

Client Receive Connector

Default Receive Connector

Create a New Receive Connector

1. Open EMC ->Server Configuration -> Hub Transport -> Click New Receive Connector. Create the SMTP name for each server with custom configuration.
 

2. Configure the local IP address to receive mail and specify the FQDN for HELO or EHLO
 

3. Define the remote IP addresses. This IP address is to grant/allow SMTP relay.
 

4. Select New

5. Select Finish to exit the wizard
 

6. Open the properties to Allow Authentication with TLS and Permission Groups with Anonymous users.
 

7. Open the EMS and run the following cmdlet

Get-ReceiveConnector "exch01\SMTP Relay EXCH01" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient"

Get-ReceiveConnector "exch02\SMTP Relay EXCH02" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient"

SMTP Relay Receive Connector

Install and Configure Exchange 2010 - Part 2

In this post, i will start the Exchange 2010 SP 3 installation. I'm going to setup 2 Exchange servers with CAS, HT and MB role install into each server. Both servers will load balance by HLB.

1. Log on to EXCH01 and launch the installer, select step 4 to start the exchange installation

2. Next on the introduction page

3. Accept the license agreement

4. Select No on the error reporting page

5. Choose the Typical Exchange Server Installation and specify the path for the Exchange Server program file

6. Select No because no Outlook 2003 in our environment. If you do have any outlook 2003, public folder database is required.

7. Mark the Client Access server role will be Internet-facing and enter the domain name as mail.external.com. This is the owa address that access from external.

8. Select I don't want to join the program at this time on the customer experience improvement program page

9. After the readiness checks, click Install to start the installation.

10. Click Finish to exit installation wizard

11. Restart the server after complete of installation

12. Install Exchange 2010 SP3 latest rollup after restarted. Here with the reference for Exchange Server and Update Rollups Build Numbers.

13. Repeat Step 1 to step 12 for EXCH02

14. Repeat Step 1 to Step 12 for EXCH03 but choose the Custom Exchange Server Installation and select only Mailbox Role in step 5

Install and Configure Exchange 2010 - Part 1

I'm going to show you how to install and configure Exchange 2010.

Here with some little information of my setup.

• 2 Exchange servers - named EXCH01 and EXCH02 with HT, CAS & MB roles installed. Both Exchange servers will need to join domain. 2 NICs (Mapi & Replication)
• 1 Exchange server - named EXCH03 with MB roles installed and join domain. This server will only contain journal mailbox database. Single NIC.
• 1 SMTP Gateway - named SMTP01
• Both EXCH01 and EXCH02 Exchange servers will be load balanced by hardware load balance. I will not show you the HLB configuration here
• A SAN certificate which will be used for OWA, EAS, OA & RMS publishing. I'm using a certificate issued by DigiCert. Example for SAN name: mail.external.com; autodiscover.external.com; rms.external.com

Pre-Requisite

1. Install the Windows Server 2008 R2 Operating System Prerequisites

NOTE: You may refer to following link if you are using different version of operating system.

Exchange 2010 Prerequisites

1. On servers that will host the Hub Transport or Mailbox server role, install the Microsoft Filter Pack. 

2. On the Start menu, navigate to All Programs > Accessories > Windows PowerShell. Open an elevated Windows PowerShell console, and run the following command.

Import-Module ServerManager

3. Use the Add-WindowsFeature cmdlet to install the necessary operating system components:

For a server that will host the Client Access, Hub Transport and Mailbox server roles, use the following cmdlet

Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,Web-Asp-Net,Web-Client-Auth,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Http-Redirect,Web-Http-Tracing,Web-ISAPI-Filter,Web-Request-Monitor,Web-Static-Content,Web-WMI,RPC-Over-HTTP-Proxy –Restart

For a server that will host the Mailbox server roles, use the following cmdlet

Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server -Restart

2. Prepare Active Directory and Domains

1. Login into EXCH01 or EXCH02 and launch the command prompt. Change the path to D:\Exchange Installer\Exchange2010-SP3-x64 that contain the installation file. Enter the command setup /PrepareAD /OrganizationName:ExchOrg

NOTE: You may use the different Exchange Organization Name.

2. Enter the command setup /PrepateAllDomains

3. Network Adapter Configuration for DAG
MAPI network adapter configuration

A network adapter intended for use by a MAPI network should be configured as described in the following table.

Networking features	Settings
Client for Microsoft Networks	Enabled
QoS Packet Scheduler	Optionally enabled
File and Printer Sharing for Microsoft Networks	Enabled
Internet Protocol version 6 (TCP/IP v6)	Enabled
Internet Protocol version 4 (TCP/IP v4)	Enabled
Link-Layer Topology Discovery Mapper I/O Driver	Enabled
Link-Layer Topology Discovery Responder	Enabled

The TCP/IP v4 properties for a MAPI network adapter are configured as follows:

• The IP address for a DAG member's MAPI network can be manually assigned or configured to use DHCP. If DHCP is used, we recommend using persistent reservations for the server's IP address.
• The MAPI network typically uses a default gateway, although one isn't required.
• At least one DNS server address must be configured. Using multiple DNS servers is recommended for redundancy.
• The Register this connection's addresses in DNS check box should be selected.

Replication network adapter configuration

A network adapter intended for use by a Replication network should be configured as described in the following table.

Networking features	Settings
Client for Microsoft Networks	Disabled
QoS Packet Scheduler	Optionally enabled
File and Printer Sharing for Microsoft Networks	Disabled
Internet Protocol version 6 (TCP/IP v6)	Enabled
Internet Protocol version 4 (TCP/IP v4)	Enabled
Link-Layer Topology Discovery Mapper I/O Driver	Enabled
Link-Layer Topology Discovery Responder	Enabled

The TCP/IP v4 properties for a Replication network adapter are configured as follows:

• The IP address for a DAG member's Replication network can be manually assigned or configured to use DHCP. If DHCP is used, we recommend using persistent reservations for the server's IP address.
• Replication networks typically don't have default gateways, and if the MAPI network has a default gateway, no other networks should have default gateways. Routing of network traffic on a Replication network can be configured by using persistent, static routes to the corresponding network on other DAG members using gateway addresses that have the ability to route between the Replication networks. All other traffic not matching this route will be handled by the default gateway that's configured on the adapter for the MAPI network.
• DNS server addresses shouldn't be configured.
• The Register this connection's addresses in DNS check box shouldn't be selected.