Exchange 2013 architecture with a legacy Edge Server
Hi guys, Just a quick question. I have a (potential) customer who has Exchange Server 2007 and wants to migrate to 2013. He wants to add an Edge Server into the equation, and until SP1 is released a 2007 or 2010 Edge Server is the only option. I read in Technet the following: "You can subscribe an Exchange 2007 or Exchange 2010 Edge Transport server to a standalone Exchange 2013 Mailbox server, or to a server where the Mailbox server and the Client Access server are installed on the same computer. You can't subscribe the Edge Transport server to a standalone Exchange 2013 Client Access server." My was to install 2 CAS with NLB and 2 Mailbox Servers, but having read this requirement, can I change my architecture to have 1 CAS/MB (no mailboxes) for Edge Sync, and 1 CAS standalone and still maintain the NLB cluster? Or perhaps to one of the MB servers in my DAG? Thanks in advance.
January 31st, 2013 10:37pm
Hi The transport service in 2013 runs on the mailbox servers so you would subscribe one or both of them to the edge. Having said that I would consider the need for the edge role at all - if they don't need one currently why would they be looking to install it now? Cheers, Steve
January 31st, 2013 11:27pm
Hi Steve, Thanks for the answer. It's at the customer's request to have an Edge Server. Would it interfere with the DAG if I connect the Edge to one of the Mailbox Servers? Thanks!
February 1st, 2013 12:10am
Hello, If you are utilizing legacy edge servers, they can still be used with 2013 and EdgeSync can be set up between Mailbox role and your legacy Edge servers. There should be no conflict. If your MBX servers are in the same AD site, when Edge Transport server is subscribed to one of the MBX servers, there is replication. If you have any feedback on our support, please click here Cara Chen TechNet Community Support
February 1st, 2013 5:46am
No problem. The design is to have Edgesync to the mailbox server so this will not interfere with the operation of the DAG. This would be a supported configuration in Exchange 2010 too. Cheers, Steve
February 1st, 2013 12:32pm