Home » Exchange Server » Installing an Exchange Server 2010 Edge Transport Server

Installing an Exchange Server 2010 Edge Transport Server

In this tutorial I’ll demonstrate how to install an Exchange Server 2010 Edge Transport server.

To host the Edge Transport server role I am using a server running Windows Server 2008 R2 with Service Pack 1. The server is located in the DMZ of the network.

In the last part of this series the pre-requisites for Edge Transport servers were installed.

You also need to make sure that the server has been configured with a fully qualified domain name (FQDN). A domain-joined server has an FQDN that matches the DNS name of the domain that it is joined to, but the Edge Transport server is usually installed on standalone servers and so this will not automatically be configured for you.

The next step is to install Exchange Server 2010 SP1.

Open a command prompt and navigate to the folder that contains the Exchange Server 2010 SP1 setup files.  Run the following command to install the Edge Transport server role.

Note: the /installwindowscomponents switch isn’t required if you’ve already install the correct pre-requisites, but I always include it anyway.

After setup has finished restart the server, then apply the latest Update Rollup for Exchange Server 2010 SP1.

In the next part of this series we’ll look at setting up EdgeSync for the Edge Transport server.

Paul is a Microsoft MVP for Office Servers and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul is a co-author of Office 365 for IT Pros and several other books, and is also a Pluralsight author.
Category: Exchange Server

14 comments

  1. Ramy Said says:

    Hi Paul.

    Im installaing Exchange 2010 Edge transport role on Microsoft Hyper-V virtual machine, I added the HUB IP address in the hosts file of the Edge and I also added the DNS suffix to the Edge server.

    When I run the installtion wizard, I get the same warning “Setup cannot contact the primary DNS server on port 53” while the machine can resolve all internet domain names using NSLOOKUP.

    Should I ignore the message and continue with the installation or what???

    Please help…

    • I think you should fix the problem. Check that both the DNS server IP addresses you’ve put in the TCP/IP settings for the server are reachable and that the Edge Transport has access to them over port 53 to make DNS queries.

      If the server is constantly querying a primary DNS server it can’t reach it will be sub-optimal performance.

  2. Tony says:

    Hi Paul,

    Thanks for your great article. I have 2 questions. The first, as you said, the ET should be installed on a standalone sever in DMZ. But you also mentioned the server should be joined domain. I am confused. Can you explain it ? Second, may I installed ET in same LAN with HUT ? If yes, the ET need joined domain or not ?

    Thank you very much.

  3. Shridhar says:

    Hi Paul,

    Need your advise with regards to installing public certificate on Exchange Edge server 2010 our current configuration is.

    Symantec Message Labs for email hygiene
    Exchange Edge Servers for mail filtering
    HUB/CAS server for email delivery

    Now the issue is there is no secure communication happening between Symantec Message labs and Exchange Edge server. Currently Exchange Edge server has self signed certificate installed on it which is expired now we have plans to replace current certificate with public certificate for secure TLS communication.

    Can you guide us how can we set it up without causing any disruption to services

  4. bob says:

    Hi there,
    I have made the mistake to install the edge role on an existing 2016 exchange server.
    Now I cannot remove the role, or exchange 2016, do you have any suggestions how to get things running again? Would appriciate all help!

    Kind Regards Bob

Leave a Reply

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