|
|
|
date: Tue, 27 Feb 2007 09:50:00 -0800,
group: microsoft.public.exchange.design
back
Re: Global Exchange solution
I would say make use of the NLB for your FE deployment to enhance
performance and increase your internet speed in front of your US-Based FE.
To have another Exchange in Europe and move Europe an Asia's Mailboxes to it
will not improve anything if users still access OWA or RPC from your
US-Based FE and it will go to retrieve the mail through the VPN that
separates it from their BE, unless u create another OWA address for those
users in Europe and ask them only to use it, in that case you will be having
2 OWA addresses one in US and One in Europe for non-US associates.
Regards,
Waleed Omar
"skyline" wrote in message
news:277CC015-1E3F-4728-9F1E-F138A5AF73C3@microsoft.com...
> Hello,
>
> We have a need for a more globalized Exchange solution. Right now, we
> have
> a central front end and back end server in the US, and have associates all
> across the US connecting, and the other offices and associates worldwide.
> Anyone outside the US uses RPC over HTTP to connect, or OWA, and it is
> incredibly slow on both of them. We need to provide these users in
> Europe/Asia the same performance we have here.
>
> We have discussed placing an additional Exchange server in an office in
> Europe, and having the mailboxes of users outside the US routing here
> instead. Then we could put an internet connector on that server and have
> a
> second MX record for their mail, which would also be a redundant path
> since
> the 2 servers would be interconnected across the ocean via a VPN tunnel.
>
> We are currently looking for documentation with best practices and global
> Exchange solutions and can't find any. Can anyone provide suggestions or
> documentation on how other organizations handle this challenge and what
> they
> do to resolve the issues?
>
> Thanks!
date: Tue, 27 Feb 2007 22:11:30 +0200
author: Waleed Omar
|
|