How to configure Exchange 2010 Hub Transport (HT) Server

Hub Transport server role manages all mail flow inside the organization, applies transport rules, applies journaling policies and delivers messages to a recipient’s mailbox. Hub Transport server is placed internal network with an Active Directory Forrest. Messages that are sent to the Internet are relayed by the Hub Transport server to the Edge Transport server role that’s deployed in the perimeter network. Messages that are received from the Internet are processed by the Edge Transport server before they’re relayed to the Hub Transport server. If you don’t have an Edge Transport server, you can configure the Hub Transport server to relay Internet messages directly or utilize a third-party smart host. You can also install and configure the Edge Transport server agents on the Hub Transport server to provide anti-spam and antivirus protection inside the organization. It is best practice to keep two separate servers for HT and ET roles.

You must deploy a Hub Transport server role in each Active Directory site that contains a Mailbox server role. Deploying more than one Hub Transport server per site provides redundancy. When you install more than one Hub Transport server in an Active Directory site, the connections are distributed. HT server or HT servers read Active Directory for user authorization. That means you can deploy Single Sign on (SSO) in your organization.

To configure HT and ET, DNS record maintaining is vital part. The Edge Transport server queries the configured external DNS servers to find the DNS records that are required to deliver the message. The DNS servers that are configured for external DNS lookups are queried in the order in which they’re listed. If one of the DNS servers is unavailable, the query goes to the next DNS server on the list. The DNS servers are queried for the following information:

Mail exchange (MX) records for the domain part of the external recipient.   The MX record contains the fully qualified domain name (FQDN) of the messaging server that’s responsible for accepting messages for the domain, and a preference value for that messaging server. To optimize fault tolerance, most organizations use multiple messaging servers and multiple MX records that have different preference values.

Address (A) records for the destination messaging servers.   Every messaging server that’s used in an MX record should have a corresponding A record. The A record is used to find the IP address of the destination messaging server. The subscribed Edge Transport server uses the IP address to open an SMTP connection with the destination messaging server. The required combination of iterative DNS queries and recursive DNS queries that start with a root DNS server is used to resolve the FQDN of the messaging server that’s found in the MX record into an IP address.

In HT server or HT servers, you must obtain certificates from a Windows Enterprise Root Certificate Authority before you start installing HT role.

Prepare Windows Server 2008 x64

Install windows Features:

Windows Server 2008 x64 SP 2 or Windows Server 2008 R2

HT server must be a member of Active Directory Domain

Microsoft .NET Framework 3.5

WCF Activation

Windows Remote Management 2.0

Windows PowerShell V2

Active Directory Lightweight Directory Services (AD LDS)

Net TCP port sharing services started and automatic start-up

Microsoft Office Filter Pack installed.

Computer Certificate and web certificates installed

  

Install HT server

Configure HT Server

 

Add IP address of HT server as internal connector.

Specify local IP ranges.

 

Test Outlook Web App

Relevant Topics

How to configure Exchange 2010 Client Access Server (CAS) Role

Step by Step Guide on Exchange Server 2010 Edge Transport Role

Forefront TMG 2010: Publish Outlook Web Access and Exchange Servers using Forefront TMG 2010

Forefront Protection 2010: how to install and configure Forefront Protection 2010 for Exchange Server 2010—Step by step

share this

How to configure Exchange 2010 Client Access Server (CAS) Role

The Client Access server (CAS) role is one of five server roles for Microsoft Exchange Server 2010. CAS is placed in a DMZ or perimeter network facing internet that means CAS configured with a public IP accessible to external network. There are six components of CAS. Components are Outlook Web App, Exchange ActiveSync client applications, Post Office Protocol version 3 (POP3), Internet Message Access Protocol (IMAP) version 4, the Availability service and Auto discover Service. The Client Access server role also provides access to free/busy data by using the Availability service and enables certain clients to download automatic configuration settings from the Auto discover service.

The Client Access server role accepts connections to Exchange server 2010 from software clients such as Microsoft Outlook Express, Microsoft office Outlook and Eudora use POP3 or IMAP4 connections to communicate with the Exchange HT server. Hardware clients such as mobile phones, use ActiveSync, POP3 or IMAP4 to communicate with the Exchange server. You must install the Client Access server (CAS) role in every Exchange organization and every Active Directory Domain site that has the Mailbox server (HT) role installed.

Prerequisites

Operating System requirement is similar to other Exchange Server roles. CAS does not store any mailboxes. CAS acts as a media in-between clients and HT server. you don’t need big storage for CAS server but the following Windows Server 2008 features must be installed. Outlook web access is a secure https web access. Web certificate and computer certificates must be installed in CAS server. To configure Outlook Anywhere you need to buy a SSL certificate from third party vendor such as verisign or godaddy.

Installation

 

Configuration

 

Once you finish installation and configuration of CAS role. You have to create Outlook web publishing rule in Forefront TMG 2010 or ISA server otherwise you will be blocked by Forefront TMG.

 

Relevant Topics

Forefront TMG 2010: Publish Outlook Web Access and Exchange Servers using Forefront TMG 2010

Step by Step Guide on Exchange Server 2010 Edge Transport Role

Exchange Server 2010: Server Roles

Forefront Protection 2010: how to install and configure Forefront Protection 2010 for Exchange Server 2010—Step by step

share this

Transitioning from Exchange 2007 to Exchange 2010—-Step by Step

Exchange Server 2007 and Exchange Server 2010 are similar in architecture so the transition process is more straightforward. The following procedure illustrates a typical transition from Exchange Server 2007 to Exchange 2010:

 

Prerequisite:

 

Run Dcdiag, Netdiag and check FSMO roles functioning perfect.

All domains in an existing Active Directory forest have to be running in native mode.

The Active Directory forest has to be running on a Windows Server 2008 forest functionality level.

Each site in Active Directory should have at least one PDC, schema master and the Global Catalog server on a Windows Server 2008 SP2 level. It is recommended to have 64-bit type Domain Controllers and Global Catalog Servers for optimal performance preferably Windows Server 2008 x64 SP2 or Windows Server 2008 R2

All Exchange Server 2007 servers must have Exchange Service Pack 2 installed.

The Internet facing Active Directory sites must be the first sites that will be migrated to Exchange Server 2010.

Windows Server 2008 SP2 64 bit or Windows Server 2008 R2.

Internet Information Server needs to be installed for CAS.

Web Certificates must be installed in server holding CAS

Windows Remote Management (WinRM) 2.0

PowerShell 2.0 (Windows Server 2008 feature if R2 version)

.NET Framework 3.5 (Windows Server 2008 feature)

Desktop Experience (Windows Server 2008 feature)

Net. TCP Services started and set automatic (services.msc)

Disable TCP/IP6 from Registry (if you use tcp/ip4)

2007 Office System Converter

Better to Prepare a document showing task list and systems build info. Tick one after one when finishing a task accordingly.

Precautions:

Backup Active Directory global Catalog servers, Exchange servers and Servers that interoperate with Exchange Server, such as gateway systems or replicated directory servers. It is also a best practice to turn off any replication to other environments during the transition process, such as Forefront Identity Manager (previously named ILM, MIIS, IIFP, and MMS).

Please bear in mind that an in-place upgrade to Exchange Server 2010 in any scenario is NOT supported!

Please be aware that Win2k8 AD and Exchange 2010 (HT, MT, CAS, ET Role, Unified Messaging) are based on 64 bit architecture.

Migration from Windows 2003 AD Forest to Windows 2008 AD Forest and Forest Preparation

Create user with domain admin, schema admin and enterprise admin role from existing AD

Log on using new user name

Bring the AD forest and domains to Windows Server 2003 Functional Level

Insert Win2k8 Server DVD into Win2k3 DC

Use elevated command prompt using domain\username (where user name must be above mentioned) Start Menu>Run type runas /user:domain\username cmd.exe

Provide Password

d:\sources\adprep\adprep.exe /forestprep where d: is DVD ROM

d:\sources\adprep\adprep.exe /domainprep /gpprep

d:\Setup and select upgrade option to use existing DC

Transfer FSMO Roles for a new Win2k8 DC with new Hardware

Make one DC as GC

Replicate AD database, GPO or wait tomstone to replicate

Retire Windows 2003 DC

Run DCPROMO (Uncheck this is last remaining DC)

Raise new Domain Functional level to Win2k8

Insert Exchange 2010 DVD into DC to upgrade AD

Open command prompt and change directory to DVD rom

Type Setup.com /PrepareSchema

Type .\Setup /PrepareAD /OrganizationName:organisation_name

 

Transition Sequencing:

Once you have finished prerequisite, you have to take the installation order of the Exchange Server 2010 servers into account to minimize the impact:

Exchange Server 2010 Client Access Server. The Client Access Server can work with an Exchange Server 2007 Mailbox Server as well as an Exchange Server 2010 Mailbox Server.

Exchange Server 2010 Hub Transport Server (New Internal and External Connector). Documents all the policies you have in existing HT and apply same in new HT server.

Exchange Server 2010 Mailbox Server. After you have installed the Mailbox Server role and established a proper Public Folder replication between Exchange Server 2007 and Exchange Server 2010, you can start moving mailboxes to the new Exchange 2010 Mailbox Server. Of course, the Public Folder replication needs only be configured when Public Folders are used in Exchange Server 2007.

The Edge Transport Server can be installed at any time, since an Exchange Server 2010 Edge Transport Server can be subscribed to an Exchange Server 2007 SP2 Hub Transport Server. Use Export and Import option for all policies applied in previous ET server.

Finally Unified Messaging

 

Transitioning from Exchange Server 2007 to Exchange Server 2010

1. Prepare Windows Server 2008 (RTM or R2) x64 edition server for the first Exchange 2010

2. Install the AD LDIFDE tools on the new Exchange 2010 server (to upgrade the schema).

3. Install necessary prerequisites (WWW for CAS server role) including web certificates.

4. Install CAS server role servers and configure per 2010 design. Validate functionality.

5. Transfer OWA, ActiveSync, and Outlook Anywhere traffic to new CAS servers.

6. Install Hub Transport role and configure per 2010 design.

7. Transfer inbound and outbound mail connector to the new 2010 HT servers.

8. Install mailbox servers and configure Databases (DAG if needed).

9. Create public folder replicas on Exchange 2010 servers using Exchange 2010 Public Folder tool.

10. Move mailboxes to Exchange 2010 using Move Mailbox Wizard.

11. Re-home the Offline Address Book (OAB) generation server to Exchange Server 2010.

12. Transfer all Public Folder Replicas to Exchange Server 2010 Public folder stores.

13. Delete Public and Private Information Stores from Exchange 2007 servers.

14. Remove Exchange 2007 Edge Transport subscription

15. Uninstall all Exchange 2007 servers.

Test Procedure:

Double check Exchange Roles and services are started

Check event logs

Check internal and external connector

Test OWA and Email using test user

Run BPA

 Verify with the system build info you created at beginning to check what you might have missed out or not!

Key Factors:

The following key factors differentiate a 2007 to 2010 transition from a 2003 to 2010 transition:

Exchange admin groups and routing groups are already out of the picture.

The Recipient Update Service is no longer part of the transition process.

The public folder hierarchy does not need to be re-homed. Indeed, because public Folders are not required for Exchange Server 2007, they might not even be part of the transition.

One added advantage of transition from Exchange Server 2007 to Exchange Server 2010: if Outlook clients are at 2007 levels or above, the move mailbox process does not result in downtime, making the end user transition experience completely transparent.

Further Study

Transition from Exchange 2003 to Exchange 2010 

Watch TechNet Video on Transition from Exchange 2007 to Exchange 2010

Step by Step Guide on Exchange Server 2010 Edge Transport Role

Edge Transport Role in Exchange Server 2010 provides an important layer of security between external and internal messaging infrastructure. The Edge server analyses messages and can identify spam, content, connection trends and take the appropriate action to prevent delivery of potentially harmful content, spam, and other undesired messages. So, all message coming to and going form entire organization scanned through Edge Transport Server and verify with the policies deployed in it then pass through toward external networks. The Edge Transport server plays a vital role in the messaging infrastructure, protecting the organization from attack and the preventing delivery of unnecessary email, which ultimately can save an organization’s reputation, reduce administrative overhead, and increase productivity.

Installation Prerequisite:

Windows Server 2008 x64 SP 2 or Windows Server 2008 R2

Microsoft .NET Framework 3.5

Windows Remote Management 2.0

Windows PowerShell V2

Active Directory Lightweight Directory Services (AD LDS)

Exchange Server 2010 HT, CAS, Mailbox Roles installed in a separate Windows Server 2008 computer

Installation:

   

Edge Transport Config:

Now from Start>All Programs>Microsoft Exchange Server 2010>Exchange Management Console you have to configure Anti-Spam, Receive Connectors, Send Connectors, Transport Rules, Accepted Domains tabs available in Edge Transport console. on Anti-Spam tab, you have to configure Content Filtering, IP Allow List, IP Allow List Providers, IP Block List, IP Block List Providers, Recipient Filtering, Sender Filtering, Sender ID and Sender Reputation through action pan.

EdgeSync Config on an Edge Transport Server:

In Edge Transport Server, Open the Exchange Management Shell> Type following

New-EdgeSubscription –FileName “C:\Edgeinfo.xml”

Copy the Edge subscription file to the Hub Transport server into C:\Edgeinfo.xml

In Hub Transport Server, Open Exchange Management Console>Organization Configuration>Hub Transport section

In the action pane, click New Edge Subscription>New Edge Subscription Wizard.

Click Browse>select Active Directory site>Select Default First Site

Browse to the location of the Edge subscription file you copied from the Edge Transport server and click Next>Finish

Verify synchronization to the Edge Transport server’s AD LDS and review the application log in Event Viewer on both Hub and Edge Transport servers

Further Study:

Microsoft Tech

Edge Transport Overview

Key Words: Edge Transport, Exchange 2010, AD LDS, Windows Server 2008

 

 

 

 

 

 

 

 

 

 

 

Transitioning from Exchange Server 2003 to Exchange Server 2010—-Step by Step

Step 1: Prerequisite

· Windows Server 2008 with Service Pack 2 or later or Windows Server 2008 R2 must be used for all servers running Exchange 2010 server roles or management tools

· .NET Framework 3.5 (Windows 2008 feature)

· Windows Remote Management 2.0

· Windows PowerShell v2 (Windows Server 2008 feature)

· Desktop Experience (Windows Server 2008 feature)

· Net. TCP Services started and set automatic (services.msc)

· Disable TCP/IP6 from Registry (if you use tcp/ip4)

· 2007 Office System Converter

· IIS for Client Access Role

· Active Directory Services Remote Management Tools (ServerManagerCmd –i RSAT-ADDS)

Step 2: Migrating from Windows 2003 AD Forest to Windows 2008 AD Forest

· Create user with domain admin, schema admin and enterprise admin role from existing AD

· Log on using new user name

· Run Dcdiag and Netdiag tools

· Bring the AD forest and domains to Windows Server 2003 Functional Level

· Insert Win2k8 Server DVD into Win2k3 DC

· Run following command from Command prompt

· d:\sources\adprep\adprep.exe /forestprep where d: is DVD ROM

· d:\sources\adprep\adprep.exe /domainprep /gpprep

· d:\Setup and select upgrade option to use existing DC

· Transfer FSMO Roles for a new Win2k8 DC with new Hardware

· Make one DC as GC

· Replicate AD database, GPO or wait tomstone to replicate

· Retire Windows 2003 DC

· Run DCPROMO (Uncheck this is last remaining DC)

· Raise new Domain Functional level to Win2k8

Step3: Transition from Exchange 2003 to Exchange 2010

· Bring the Exchange organization to Exchange Native Mode.

· Upgrade all Exchange Servers to Exchange Server 2003 Service Pack 2.

· Upgrade at least one Global Catalog domain controller in each AD site that will house Exchange Server to Windows Server 2003 SP2 or greater.

· Prepare a Windows Server 2008 (RTM or R2) x64 edition server for the first Exchange 2010 server.

· Install the AD LDIFDE tools on the new Exchange 2010 server (to upgrade the
schema by running d:Exchange2010\Setup /PrepareSchema or Setup /ps)

· Run d:\Exchange2010\Setup /PrepareAD /OrganizationName:your_organisation_name from command prompt where D: DVD ROM

· Install any necessary prerequisites (WWW for CAS server role).

· Run setup on the Exchange 2010 server, upgrade the schema, and prepare the forest and domains. (Setup runs all in one step or separate at the command line eg.

D:\Exchange2010\Setup.com /mode:install /roles:H,C,M

· Install Client Access Server role servers and configure per 2010 design. Validate functionality.

ServerManagerCmd -i Web-Server

ServerManagerCmd -i Web-ISAPI-Ext

ServerManagerCmd -i Web-Metabase

ServerManagerCmd -i Web-Lgcy-Mgmt-Console

ServerManagerCmd -i Web-Basic-Auth

ServerManagerCmd -i Web-Digest-Auth

ServerManagerCmd -i Web-Windows-Auth

ServerManagerCmd -i Web-Dyn-Compression

ServerManagerCmd -i NET-HTTP-Activation

ServerManagerCmd -I RPC-over-HTTP-proxy

ServerManagerCmd –I Web-Server Web-ISAPI-Ext Web-Metabase Web-Lgcy-Mgmt-Console Web-Basic-Auth Web-Digest-Auth Web-Windows-Auth Web-Dyn-Compression NET-HTTP-Activation RPC-over-HTTP-proxy –Restart

· Transfer OWA, ActiveSync, and Outlook Anywhere traffic to new CAS servers.

· Install Hub Transport role and configure per 2010 design (New internal/external SMTP connector)

· Transfer inbound and outbound mail traffic to the HT servers.

· Install mailbox servers and configure Databases (DAG if needed).

· Create public folder replicas on Exchange 2010 servers using Exchange 2010 Public Folder tool.

· Move mailboxes to Exchange Server 2010 using Move Mailbox Wizard or PowerShell.

· Re-home the Offline Address Book (OAB) generation server to Exchange Server 2010.

· Re-home the public folder hierarchy on the new Exchange Server 2010 admin group.

· Transfer all Public Folder Replicas to Exchange Server 2010 Public folder store(s).

· Review and verify Installation log, events, Exchange related Windows services, server roles

· Test Mail Flow, public folder, webmail, outlook config

· Run BPA

· Delete Public and Private Information Stores from Exchange 2003 server(s).

· Delete Routing Group Connectors to Exchange Server 2003.

· Delete Recipient Update Service agreements using ADSIEdit.

· Uninstall all Exchange 2003 servers and remove from domain.

Tools to use:

Dcdiag

Netdiag

Repadmin

Replmon

Ntdsutil.exe

ADSIEdit

Exchange Management Console

Further Help:

Microsoft Technet

Keywords: FSMO, Exchange 2010, Exchange 2003, Exchange Server Roles, Windows Server 2008, Windows Server 2003

Important Warning: I am talking about messaging technology. It could be heart of your organization. So Prepare a test lab that simulate your circumstances and fit in your organisation. I created this instruction in a VMware lab environment. Visit TechNet web site to learn more about Exchange 2010 before you deploy in production environment. 

Cheers & Good Luck.

Exchange Server 2010: Server Roles

Microsoft Exchange Server 2010 provides new technologies, features, functionality and services to the communication and messaging product line. Exchange 2010 is a comprehensive, integrated, and flexible messaging solution for small business to enterprise. Exchange Server contains five different roles. Exchange configuration and server roles deployment depends on individual need and licenses you bought. Five different roles and their functionality are: 

Mailbox Server   This server can host mailboxes and public folders. A mailbox server also contains address lists, Calendar Repair, E-Mail Address Policies, Exchange 2010 Store, Exchange Search, Importing and Exporting Mailbox Data,Inbox Rules, move Requests,Recipients. Mailbox server interact with rest of the servers holding the following roles and also with Microsoft Active Directory.

Client Access Server   This is the server that hosts the client protocols, such as Post Office Protocol 3 (POP3), Internet Message Access Protocol 4 (IMAP4), Exchange 2010 ActiveSync, Secure Hypertext Transfer Protocol (HTTPS), Outlook Anywhere, Availability service, and Auto discover service. The Client Access Server also hosts Web services (internet facing webmail). 

Unified Messaging Server   This is the server that connects a Private Branch PBX system to Exchange 2010. Microsoft Exchange Server 2010 Unified Messaging (UM) combines voice messaging, and e-mail messaging into a single messaging infrastructure. Unified Messaging puts all e-mail and voice messages into one Exchange 2010 mailbox that can be accessed from many different devices. After Unified Messaging servers have been deployed on the network, users can access their messages using Outlook Voice Access, from any telephone, from a mobile phone, or from the computer. Microsoft Exchange 2010 provides access to Exchange information,  voice mail, Call answering and outlook voice access.      

Hub Transport Server   This is the mail routing server that routes mail within the Exchange organization i.e. an internal mail delivery systems. The Microsoft Exchange Server 2007 Hub Transport server role is deployed inside your organization’s Active Directory directory service. It handles mail flow, categorize, routing and delivery. you can setup custom rules in hub transport server to record entire email communication to and form your organisation. You may deploy two HT server in your organisation to obtain redundancy and load balancing.

Edge Transport Server   This is the mail routing server that typically sits at the perimeter/DMZ of the network and routes mail in to and out of the Exchange organization. The Edge Transport server role accepts mail coming into the Exchange 2010 organization from the Internet/ un-trusted networks and routes all outbound messages to the Internet. The Edge Transport server role acts as a smart host and SMTP relay for the Exchange organization. You have to configure Send connectors and Receive connectors on the Edge Transport server to control message processing. Edge transport server also facilitate content filtering such as Antivirus/ Anti-spam functionality in and out of exchange organisation. You have to configure Edge rules in this server to control and monitor send and receive email from un-trusted network.

Further Study

Microsoft TechNet

Keywords: Exchange Server 2010, Exchange Server Roles

Exchange 2010: installation error

I experienced few errors while installing exchange 2010 on test bed. I reckon, I should share the resolution with you guys testing exchange 2010…

hub transport role fails to install

The execution of: “$error.Clear(); if($RoleStartTransportService) { start-SetupService -ServiceName MSExchangeTransport }”, generated the following error: “Service ‘MSExchangeTransport’ failed to reach  status ‘Running’ on this server.”

Cause: TCP/IP6 disabled or unchecked on TCP/IP properties of windows 2008 server.

Resolution: If you are not using tcp/ip6 then disable TCP/IP6 permanently to resolve the issue. To completely disable IPv6 on a Windows Server 2008, follow these steps:

1. Start menu>run>regedit.exe>ok
2. HKLM>system>CurrentControlSet>Services>tcpip6>parameters
3. Right Click on Parameters>New>DWORD (64-bit) value
4. Type DisabledComponents, and then press ENTER.
5. Double-click DisabledComponents and then type 0xffffffff in Hexadecimal or 4294967295 in Decimal
6. Reboot server

2007 Office System Converter: Microsoft Filter Pack

I have been given warning for 2007 Office System Converter pack not installed while prerequisite check before installation start.

Resolution: Download Office System Converter and install before proceed further.

Desktop Experience Features

I installed exchange 2010 on Windows 2008 R2. I have been given another warning for Desktop Experience feature not installed in server.

resolution: install desktop experience

Start menu>Administrative tools>Server Manager>Features>Add Features>follow installation screen