Add Edge to Production Exchange 2010

I just want a bit of advice on adding in an Edge Transport Server to a production Exchange 2010 environment.

We have two servers both running the HT and CAS roles with a Windows NLB connection between them.  All our mail currently routes out through a SmartHost linux server in a different domain in our forest.  Here's my questions for clarification:

1) Do I have to apply the edge.xml file onto both my HT servers to configure them both, or will applying it on one make the changes to the environment and be "done"?

2) I assume I then will just need to re-point my MX record for our domain from the IP address of HT connection to the IP address of the Edge server?  Can/should I leave the MX record that points to the HT in place with a higher value on it to guarantee mail will route continuously through the changeover?

3) Anything else obvious I'm overlooking?  I've looked at the Edge with 2003 documentation here: http://technet.microsoft.com/en-us/library/bb124011%28EXCHG.80%29.aspx, but not all that is applicable for my 2010 environment.

Thanks in advance!
LVL 5
e_sandrsAsked:
Who is Participating?
 
Rajith EnchiparambilOffice 365 & Exchange ArchitectCommented:
1. As long as both hub servers are in the same AD site, you only have to do it once. You are subscribing to the ad site.

2. MX records should point to the firewall which then forwards the request to Edge server. It should now be forwarding to hub servers.

Isn't linux server involved in inbound emails?

3. Make the change out of hours.
0
 
Fox85IT and Security ProfessionalCommented:
0
 
e_sandrsAuthor Commented:
1.  Ok, thanks for the verification.

2. We have an external address MX record which forwards to the linux server, which then forwards employee mail to Exchange and student mail to an open source solution we host (we're a college).  We have a separate internal DNS for our private network, so when we went to Exchange 2010, I put in an MX record to point that subdomain to the hub servers.  

I'll plan on making the MX record change and the Edge subscription "at the same time" during off-hours as you mentioned.

Not really relevant to the question, but eventually we will be outsourcing our student email to Microsoft (Live @ EDU) and then will have mail routed through MS servers first, then to our environment.  This Edge implementation is to make that email transfer "all Microsoft" and remove the Linux server from the routing (eventually).
0
 
e_sandrsAuthor Commented:
Edge implementation went (essentially) fine.  Ended up with a bit of a server loop for a short bit between my Edge and two Hub Transport servers with some addresses in a shared address space - but once that was worked out we're good until the next phase.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.