Is it possible to remove 2010 Hub Transport entirely in an Exchange 2013 environment?

I'm using Exchange 2010 Edge Transport in our organization that I've recently upgraded to Exchange 2013. I like Edge Transport - along with our spam filter it is an effective and simple way to send and receive external e-mail - and I don't want to get rid of it.  But it seems like it needs a 2010 Hub Transport server to interact with. 

Right now the only other Exchange 2010 Server I have left running in the organization is the one Hub Transport server that interacts with the Edge Server.  Is there a way to undeploy this server too and connect the Edge Server directly to one of the 2013 Mailbox Servers?  Or will this need to stay as part of the organization as a pair with Edge Transport?

I noticed mail flow was running just fine while the Hub Transport server was turned off.  So it seems like it's possible.  But I want to be able to undeploy it safely without hurting mail flow.  Are there any links or white papers that show how best do do

October 24th, 2014 4:06am

Both Edge 2007 and 2010 are supported and you can use them with Exchange 2013, even without any Exchange 2007/2010 servers in the internal network.

http://technet.microsoft.com/en-us/library/jj150569(v=exchg.150).aspx

Beware that you must have Exchange 2013 mailbox server in the environment, mail flow and Edge sync process will happen between Exchange 2013 MBX role and your 2010 Edge, so you need to make sure all the required ports are opened.

Free Windows Admin Tool Kit Click here and download it now
October 24th, 2014 5:22am

I have two 2013 mailbox servers. I guess my main question is, how will I establish and manage sync partnerships once the 2010 Hub Transport server is gone?  Is it all now from either the web GUI or the Mailbox shell prompts? Is there a link that shows how to establish and manage sync relationships to Edge Server from a 2013 organization?
October 24th, 2014 9:50pm

Before you remove your HUB servers, make sure you re-subscribe the Edge server using the below steps:

On Edge Server:

New-EdgeSubscription -FileName "C:\EdgeSubscription.xml"

copy the file to one of the mailbox servers, and run:

New-EdgeSubscription -FileData ([byte[]]$(Get-Content -Path "C:\EdgeSubscription.xml " -Encoding Byte -ReadCount 0)) -Site "ADSITENAME"

once completed, most of the tasks to manage/test your Edge sync will be via PowerShell, please see the below link for more details:

http://technet.microsoft.com/en-us/library/aa996865(v=exchg.150).aspx

Free Windows Admin Tool Kit Click here and download it now
October 25th, 2014 4:58pm

Hi Ron,

Have you checked the suggestion Mohammad provided to manage Edge subscriptions?

Is there any update with your issue?

Best regards,

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

October 28th, 2014 4:52am

Hi guys,

Sorry for such an extended delay in this.  I did recreate the Edge Sync, and that's solved, but now I have an issue with Distribution Groups under Exchange 2010.  They all still list the Exchange 2010 HT server as the Expansion Server.  If I go into Recipient Configuration to change that server in EMC, the only option remains the 2010 HT server.  And I don't see an option to change that in 2013 EAC.  So I'm guessing I need to figure out how to change this in EMS 2013. 

Until I figure that out, I can't remove the 2010 HT server. 

Free Windows Admin Tool Kit Click here and download it now
February 4th, 2015 6:47pm

Derp - nevermind.  All I needed to do was uncheck "Set Expansion Server" in EMC. 
February 4th, 2015 7:13pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics