Re: Extend Exchange server to remote offices

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



2 ways to do this for inbound mail:
1) Have users in NY get the same Recipient Policy as the London users, they
get the same email address(es), no need for additional MX. Inbound mail
comes to London and any mail for NY recipients gets delivered to NY
Exchange.
- If you want, you can place the NY Exchange server in a different Routing
Group and create Routing Group Connectors on either end. However, in single
server scenarios this doesn't really buy you much except some control on
scheduling, message sizes, et al.

2) Create a sub-domain for NY users, something like ny.domain.com or
us.domain.com, point the MX to the A record of NY Exchange server.

For outbound email, if you're in the same Routing Group and have a SMTP
Connector for address space * to deliver outbound internet mail, you can add
the NY server as a Bridgehead so it doesn't need to hop through the London
server.

If in different Routing Groups, you can add a SMTP Connector for address
space * in the NY Routing Group to deliver outbound.
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------


"SAQIB1972" <SAQIB1972@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AFFAD148-E4FF-4F83-BA49-FDFADA37F4D1@xxxxxxxxxxxxxxxx
Hi,

We have a small office in London with one DC and Exhange server along with
a
few file servers. We are looking to open one office in New York. The New
York
office will have Router to Router VPN connectivity between the two
offices.
We are planning to have a domain controller in NY office, a file server
and
exchange server. I would like to know what is the best way to setup
exchange.

The current email is being delivered to the box in London and I am trying
to
figure out what I need to do on the Exchange side in NY to have the mail
delivered for the NY useres without getting a separate domain and
repointing
the MX record. PLEASE ANY HELP WOULD BE GREATLY APPRECIATED.


.



Relevant Pages

  • Re: Mail sitting in E2k3->E2k7 (Routing Group Connctor) Queue?
    ... I also have similar problem when some of the users somehow still sending to the old Routing group connectors? ... Looking at the Headers and the Queue on the 2003 server, ... Exchange 2003 to Exchange 2007 will delay. ... Seems like I would also need a Routing Connector on the 2000 to bridge to ...
    (microsoft.public.exchange.connectivity)
  • Re: Question re: adding Exchange cluster to an Existing Exchange org
    ... The Exchange cluster I have created is in the same Routing Group as the ... original Exchange server. ... Exchange cluster it came with its own instance of OWA? ...
    (microsoft.public.exchange.admin)
  • Re: Exchange in a Child domain
    ... MVP - Exchange ... Are they answering mail sent from the new server, ... The server is in a different Routing Group. ... The OAB system public folder must replicate to the public folder ...
    (microsoft.public.exchange.setup)
  • Re: Routing group connector stoped working
    ... It's a network problem, not an Exchange problem, and I'm afraid I don't have enough visibility into your network to help, sorry. ... The office that moved has VPN tunnles to two offices with Exchnage 2003 servers and are in their own routing group with their exchange server as master. ... There was a routing group connector between group A and B which made all internal mail flow between the moving office Exchnge server and all other exchange servers. ...
    (microsoft.public.exchange.connectivity)
  • Re: send mail for a specific customer to a specific mail server over vpn link
    ... I was attempting to force my Exchange server- only Exchange ... I created an additional SMTP Connector defining ... the address space for customer.com and the non preferred mail server as the ... A routing group is a logical concept. ...
    (microsoft.public.exchange.admin)