worpx
asked on
Setup Exchange 2007 Servers in multiple locations
Hi Exchange Experts-
I am going to be setting up Exchange 2007 servers for my company. I have read up on the preliminary groundwork for the setup and here is what I found you need:
-2 Domain Controllers for each organizational site
-1 Mailbox/ 1 HUB / 1 Client Access Server at each location
-Edge server is optional
I have 5 total locations. What is the best way to implement mail servers to go across a SINGLE domain and how will the mail servers know which location to go to?
In example, if I have email in Italy and have the setup above, how will the mail server know to route the email
FROM ITALY to ITALY (and not go out ITALY->Mail Gateway in US->back to ITALY)
or FROM ITALY to US
or FROM ITALY to OTHER GLOBAL LOCATIONS.
I was thinking MX records but that is usually for split domain or load balancing.
How would the mail server know that a user in Italy is a user in Italy and deliver it there? (does it check an OU on active directory and if the user is there it accepts mail?)
I'm looking for best practices in this specific setup (single domain, multiple remote sites, single or multiple gateways).
Thank you in advance!
I am going to be setting up Exchange 2007 servers for my company. I have read up on the preliminary groundwork for the setup and here is what I found you need:
-2 Domain Controllers for each organizational site
-1 Mailbox/ 1 HUB / 1 Client Access Server at each location
-Edge server is optional
I have 5 total locations. What is the best way to implement mail servers to go across a SINGLE domain and how will the mail servers know which location to go to?
In example, if I have email in Italy and have the setup above, how will the mail server know to route the email
FROM ITALY to ITALY (and not go out ITALY->Mail Gateway in US->back to ITALY)
or FROM ITALY to US
or FROM ITALY to OTHER GLOBAL LOCATIONS.
I was thinking MX records but that is usually for split domain or load balancing.
How would the mail server know that a user in Italy is a user in Italy and deliver it there? (does it check an OU on active directory and if the user is there it accepts mail?)
I'm looking for best practices in this specific setup (single domain, multiple remote sites, single or multiple gateways).
Thank you in advance!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi there,
Thank you for the responses-
TalonNYC- In the case of creating multiple AD sites and multiple MX records -
Couldn't the cost be the same to all servers (similar to load balancing) and direct mail to the different mail servers at different locations or is the decision all based at the Hub/Transport as to determine which location to go to?
I.E. mail from Loc1 to Loc2 and Loc2 to Loc5; does the Hub/Transport know which location its going to by determining AD structure and which users and in which site (as you suggested)?
Debating on using an edge or not; I have mail gateway machines doing those server roles in place (linux based).
Thank you for the responses-
TalonNYC- In the case of creating multiple AD sites and multiple MX records -
Couldn't the cost be the same to all servers (similar to load balancing) and direct mail to the different mail servers at different locations or is the decision all based at the Hub/Transport as to determine which location to go to?
I.E. mail from Loc1 to Loc2 and Loc2 to Loc5; does the Hub/Transport know which location its going to by determining AD structure and which users and in which site (as you suggested)?
Debating on using an edge or not; I have mail gateway machines doing those server roles in place (linux based).
Internally, the Exchange Servers use AD to figure out where the mail is supposed to go, based on AD Sites. The MX records are only for mail coming in from the outside world.
Good read: http://www.msexchange.org/tutorials/Exchange-Server-2007-Email-Routing-Part1.html