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.
When I am trying to install Edge Transport role in the server it showing the error as below:
Edge Transport Role Checks FAILED
There was a problem accessing the registry on this computer. This may happen if the Remote Registry service is not running. It may also indicate a network problem or that the TCP/IP Netbios Helper service is not running.
The Exchange Server setup operation didn’t complete. More details can be found in ExchangeSetup.log located in the :\ExchangeSetupLogs folder.
Please suggest for this error
Even after restarted the remote registry service it showing the same error.
The solution found by myself. We have to check the “Hosts” file inside C:\Windows\System32\drivers\etc folder and should check the line to add the IP Address for the corresponding Hub Transport server FQDN.
HT.domain.com
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
The Real Person!
The Real Person!
Definitely open a support case with Microsoft.
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
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.
The Real Person!
The Real Person!
Where does it say the server should be domain joined? It shouldn’t be.
Pingback: Fix Installedge.com Windows XP, Vista, 7, 8 [Solved]
Hi Paul,
Can you please advise on how to create a relay server to exchange.
Thanks in advance
hi Is it Necessary to install Edge Transport Sever ?
The Real Person!
The Real Person!
Edge Transport is not a required server role.
plz tell me why
The Real Person!
The Real Person!
Sure.
https://www.practical365.com/exchange-2010-edge-transport-server-introduction/
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…
The Real Person!
The Real Person!
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.
Pingback: Exchange 2010 Edge Transport Server: Configuring EdgeSync