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.