You have met two prerequisites for deploying the Exchange Server 2013 Edge Transport role -- having Active Directory...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Lightweight Directory Services and a separate server from the Client Access Server and Mailbox Server roles. Because you can't finalize the Edge Transport Server role installation, the most likely cause is you haven't met all the prerequisites.
Before diving into all the prerequisites for this installation, let's look at the domain to which you joined the Edge Server. The Exchange 2013 Edge Transport Server role should be placed in a perimeter network. As a general rule, you don't want machines in the perimeter network to be joined to an internal Active Directory domain. Place the Edge Transport server in the perimeter or DMZ network, instead of on the internal network.
Here's a full list of requirements for deploying an Exchange 2013 Edge Transport Server role:
- Windows Server 2008 R2 with SP1 or higher;
- Microsoft .NET Framework 4.5.2;
- Windows Management Framework 4.0;
- DNS suffix for the internal domain appended to Edge Transport Server role's computer name;
- Configure the Edge Transport Server role to use DNS to resolve internal Exchange servers; configure internal Exchange servers to use DNS to resolve the name of the Edge Transport servers;
- Ensure the account used for setup is a member of local administrators group; and
- Firewall(s) must be configured to allow the following Internet ports:
- External: Inbound/Outbound SMTP port 25/TCP
- External: Inbound/Outbound SMTP ports 25/TCP and 2525/TCP
- External: Inbound/Outbound DNS port 53/TCP and 53/UDP
- Local to Edge server LDAP port 50389/TCP
- Internal: Outbound Secure LDAP port 50636TCP
Verify that you have met all the prerequisites to determine what is halting the Exchange 2013 Edge Transport Server installation. After the Edge Transport role installation is complete, additional configurations, such as creating an Edge subscription, are needed to deploy Edge-Sync between the Edge Transport server and internal Exchange 2013 servers.
Why fewer Exchange 2013 server roles are better
Methods for rebuilding the Edge Transport Server role
The role of server roles in an Exchange 2013 upgrade
Is Exchange 2013 as protected as it could be?
Dig Deeper on Microsoft Exchange Server Mailbox Management
Related Q&A from Richard Luckett
Some folders in a mailbox on Exchange Server 2013 are not showing up on the folder list in the OWA virtual directory but do appear in other views.continue reading
How can I enable Outlook Anywhere to allow internal use for all users and external use for only some users in Exchange 2013?continue reading
Exchange Server transaction logs have filled up my hard drive. How do I free up space taken by these logs? And can I prevent it from happening again?continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.