Edge Transport configuration in Exchange server

It is complicated to deploy a complete Unified Messaging, but it is much easier to deploy a role on the Exchange server. However, when deploying Edge Transport server, you need to pay attention to some unique requirements and precautions.

Among the many new features of Exchange server 2007, Edge Transport and uniied Messaging are the most striking. The complete deployment of the Unified Messaging is complex, but the installation on the Exchange server is very simple. However, Edge Transport server has some unique requirements and skills.

Introduction

◆ Install Edge Transport server on a computer that is not in the Active Directory structure. In this case, Edge Transport server can be sacrificed when it is under external attacks.

◆ Install Edge Transport server on the DMZ computer. Do not place it all outside the firewall or inside the network.

Requirement

◆ Edge Transport server role cannot coexist with other Exchange 2007 server roles, so it must be installed on an independent hardware system.

◆ The Edge Transport server host must have the primary DNS suffix to install the role. For a computer in a domain, you don't have to worry about it, but if it is an independent computer, you should first adjust the computer.

◆ Before installing a new role, you must install Active Directory Application Mode (ADAM) on the Edge Transport server computer ). When installing ADAM, select default for all. Edge Transport server processes ADAM configuration during installation.

◆ The Computer Configuration Requirements for installing Edge Transport server role are the same as those for Exchange 2007 server. Before installation, make sure that. NET Framework 2.0, Microsoft Management Console 3.0, and PowerShell 1.0 are installed.

◆ The external dns mx record must be modified to point to the new Edge Transport server.

◆ The IP address of Edge Transport server must exist in DNS and can be accessed through Hub Transport server.

On the firewall between Edge Transport server and Hub Transport server, you must open the following ports.

Firewall Interface	Protocol	TCPPort
Input or output from the Internet to the Internet	SMTP	25
Input or output from the Intranet to the Internet	SMTP	25
Input from Intranet	Secure LDAP	50636