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.

setup /m:install /r:e,t /installwindowscomponents

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

Welcome to Microsoft Exchange Server 2010 Unattended Setup

Setup will continue momentarily, unless you press any key and cancel the
installation. By continuing the installation process, you agree to the license
terms of Microsoft Exchange Server 2010.
If you don't accept these license terms, please cancel the installation. To
review the license terms, please go to

http://go.microsoft.com/fwlink/?LinkId=150127&clcid=0x409/

Press any key to cancel setup................
No key presses were detected.  Setup will continue.
Preparing Exchange Setup

    Copying Setup Files                           COMPLETED

The following server role(s) will be installed
Languages
Management Tools
Edge Transport Role

Performing Microsoft Exchange Server Prerequisite Check

    Configuring Prerequisites                                 COMPLETED
    Language Pack Checks                                      COMPLETED
    Edge Transport Role Checks                                COMPLETED

Configuring Microsoft Exchange Server

    Preparing Setup                                           COMPLETED
    Stopping Services                                         COMPLETED
    Copying Exchange Files                                    COMPLETED
    Language Files                                            COMPLETED
    Restoring Services                                        COMPLETED
    Languages                                                 COMPLETED
    Exchange Management Tools                                 COMPLETED
    Edge Transport Role                                       COMPLETED
    Finalizing Setup                                          COMPLETED

The Microsoft Exchange Server setup operation completed successfully.
Setup has made changes to operating system settings that require a reboot to
take effect. Please reboot this server prior to placing it into production.

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.

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…

    • says

      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.

Leave a Reply

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