How to install an Edge Transport role using command-line

Share this:

We are going over the process to install an Edge Transport role in Exchange Server 2013 using the command-line tools. There are a couple of requirements that must be validated before deploying an Edge Transport server, such as (server outside of the domain, place in the network (DMZ), firewall rules and so forth) and we will tackle all that in a different Tutorial. This Tutorial was created using Windows Server 2012 R2 and Exchange Server 2013 CU6.


We are going to cover just the minimum to get the Edge Transport Server installed without issues on this Tutorial however we will be publishing a Tutorial to go over all the details.

The first step is to make sure that we configure the proper DNS suffix for the server, if those servers are going to stay in the DMZ we may want to use the future names that will be used in the Public DNS and banners of the SMTP connectors. In order to change the DNS suffix these are the steps required.

  1. Go to System or properties of My Computer
  2. Click on Change Settings
  3. In the Computer Name tab. Click on Change
  4. In the new Computer Name/Domain Changes window, click on More…
  5. In the new DNS Suffix and NetBIOS Computer Name window (shown in the figure below) for this Tutorial we are going to use apatricio.local.
    Note: It is not supported changing the DNS suffix after installing the Edge Transport Role.


The next step is to install the pre-requisites to support the Edge Transport role, and we can get this done with the following cmdline:

Install-WindowsFeature ADLDS


After changing the DNS suffix and installing the prerequisite, we will be restarting the server before continuing the next step.

Installing the Edge Transport Role using command-line…

Now that we have all prerequisites in place, we are going to download the latest CU (Cumulative Update) available and at the time that this Tutorial was being written was the CU6. After downloading we are going to extract it to the folder C:EX2013-CU6.


In order to install, we will be opening PowerShell as adminitsrator, and we are going to the folder where we extracted the latest CU, in our case C:EX2013-CU6 and we will run the following command-line using setup.exe.

.Setup.exe /Role:et /IAcceptExchangeServerLicenseTerms


That’s all for the Edge Transport role in Exchange Server 2013, after getting the image above we should restart the server and after that we can always run the cmdlet below to check the health of the server in general.




In this Tutorial we went over the process to install the Edge Transport Role using command-line and after this procedure we exchange administrators still have a lot of work to do, such as: create the subscription, clone the configuration (when using more Edge Servers), configure load balancer and so forth.

Written by Anderson Patricio

Anderson Patricio

Anderson Patricio is a Canadian MVP in Cloud and Datacenter Management, and Office Server and Services, besides the Microsoft Award he also holds a Solutions Master (MCSM) in Exchange and several other certifications. Anderson has been contributing to the Microsoft Community with articles, tutorials, blog posts, twitter, forums and book reviews. He is a regular contributor here at,, and Anderson (Portuguese).

Related Post

How to enable permissions for in-place eDiscovery ... In order to use the in-place eDiscovery and administrator has to assign admin roles permission to an user or a group before such user/group can use th...
BYOD Basics: Managing Smartphones and Tablets with... Hello folks, Fellow Anthony Bartolo from the Canadian IT Pro Connection ( blogged an interesting post about ActiveSync when managing BYO...
How to upgrade your existent Exchange Server 2013 ... In the previous article we upgrade the first member of a DAG to Cumulative Update 3 using the graphical user interface, you can check the Tutorial out...
Error MaxWebConfigFileSizeInKB when installing Exc... During Exchange Server 2013 Cumulative Update 10 in a new server the administrator may get an error related to MaxWebConfigFileSizeInKB during the Rea...