Edge Transport Server

  • The Edge Transport server role is available from Exchange 2013 Service Pack 1.
  • This server role is deployed in the perimeter network and outside the Active Directory forest.
  • Edge Transport servers don’t have direct access to Active Directory for configuration and recipient information in the way Client Access or Mailbox servers do. The Edge Transport server uses the Active Directory Lightweight Directory Service (AD LDS) to store configuration and recipient information locally.

Edge Transport Server Pre-Requisites:

Hardware

OS

Software

4 GB RAM

At least 30 GB on the drive on which you install Exchange

An additional 500 MB of available disk space for each Unified Messaging (UM) language pack that you plan to install

200 MB of available disk space on the system drive

A hard disk that stores the message queue database on with at least 500 MB of free space.

Windows Server 2012 R2 Standard or Datacenter1

Windows Server 2012 Standard or Datacenter

Windows Server 2008 R2 Standard with Service Pack 1 (SP1)

Windows Server 2008 R2 Enterprise with Service Pack 1 (SP1)

Windows Server 2008 R2 Datacenter RTM or later

ADLDS (Active Directory Lightweight Directory Service)

NET Framework 4.7.1

Windows Management Framework 4.0

Visual C++ Redistributable Package for Visual Studio 2012

Communication port settings for Edge Transport servers:

Network interface

Open port

Protocol

Note

Inbound from and outbound to the Internet

25/TCP

SMTP

This port is required for mail flow to and from the Internet.

Inbound from and outbound to the internal network

25/TCP

SMTP

This port is required for mail flow to and from the Exchange organization.

Local only

50389/TCP

LDAP

This port is used to make a local connection to AD LDS.

Inbound from the internal network

50636/TCP

Secure LDAP

This port is required for EdgeSync synchronization.

Inbound from the internal network

3389/TCP

RDP

Opening this port is optional. It provides more flexibility in managing the Edge Transport servers from inside the internal network by letting you use a remote desktop connection to manage the Edge Transport server.

Ref: https://docs.microsoft.com/en-us/exchange/exchange-2013-system-requirements-exchange-2013-help

Leave a Reply

Your email address will not be published. Required fields are marked *