| Author |
Message |
ckoymen
Guest
|
 Posted:
Wed Oct 05, 2005 4:58 pm Post subject:
Exchange Servers at different sites |
|
|
I'm trying to build exchange network and I would like to take your
suggestions.
2 sites, 2K3 Exchange Server Standard Edt. on each site.
2 sites have been connected eachother with Les10 fiber optic.
2 sites have their own internet adsl connection. site 1 has 1 mbit, site2
has 2 mbit.
each site has different departments.
company has only one domain.
Now ideally what I am trying to achieve is;
emails which has been sent to sales department at site2 should directly go
to exch. serv at site via its own internet conn. and it deparment at site1
should directly receive and send email using it's own internet connectivity.
I read that; without 2nd domain, it's not possible to receive emails
seperately to 2 sites (exchange servers) unless we hire an exchange hosting
from a company, does it cost a lot?
If I send/receive all emails from the site1 and use Les10 connection to
route sales departments emails, would it be too much for 10 mbit bandwidth?
Is there anything that I can do, thanks for your help anyway.
|
|
| Back to top |
|
 |
Bharat Suneja
Guest
|
| Posted:
Thu Oct 06, 2005 12:08 am Post subject:
Re: Exchange Servers at different sites |
|
|
You can partition the dns namespace to assign email addresses based on
location - so all users at Site1 have email addresses as
site1(orwhatever).domain.com and same thing for site2. Next, mx records for
the sub-domains site1.domain.com pointing to exch in site1, same thing for
site2.
A better solution would be to not go this route and not play with the
namespace at all.
- Let everyone have default @yourdomain.com email addresses, and make sure
both sites have vpn connectivity.
- You can have MX records pointing at both Exchange servers, the one with
higher priority (lowest value in MX record) pointing at Exch1 in primary
site, and the second one pointing to Exch2 in second site.
- This will require both sites to have Internet connectivity, and allow smtp
traffic to the Exch server from the Internet.
- If Site1 goes down, Site2 will continue to receive mail which will be
delivered to local users immediately. Mail for Site1 users will be queued
till Exchange in Site1 is up.
--
Bharat Suneja
MCSE, MCT
--------------------------------
"ckoymen" <ckoymen@hotmail.com> wrote in message
news:u5ozMHcyFHA.2132@TK2MSFTNGP15.phx.gbl...
| Quote: | I'm trying to build exchange network and I would like to take your
suggestions.
2 sites, 2K3 Exchange Server Standard Edt. on each site.
2 sites have been connected eachother with Les10 fiber optic.
2 sites have their own internet adsl connection. site 1 has 1 mbit, site2
has 2 mbit.
each site has different departments.
company has only one domain.
Now ideally what I am trying to achieve is;
emails which has been sent to sales department at site2 should directly go
to exch. serv at site via its own internet conn. and it deparment at site1
should directly receive and send email using it's own internet
connectivity.
I read that; without 2nd domain, it's not possible to receive emails
seperately to 2 sites (exchange servers) unless we hire an exchange
hosting from a company, does it cost a lot?
If I send/receive all emails from the site1 and use Les10 connection to
route sales departments emails, would it be too much for 10 mbit
bandwidth?
Is there anything that I can do, thanks for your help anyway.
|
|
|
| Back to top |
|
|
ckoymen
Guest
|
| Posted:
Thu Oct 06, 2005 1:58 pm Post subject:
Re: Exchange Servers at different sites |
|
|
Thanks for your suggestion Bharat.
So, as far as I understand, please correct me if I'm wrong, for your second
solution which looks more logical, if one of the exch. servers would go
down, those user's emails will be queued. Users will moan a bit, but at
least we're not going to make so much stress at Les10 bandwith connection.
Sorry for my ignorance, but when they both in the same domain, they will
replicate eachother (won't they?) and both exch. servers will see the list
of users via common active directory. how would I tell exch1 to pick up
emails of user which is located on that site and the same thing for the
other site?
Thanks for your help again.
Cenk
"Bharat Suneja" <bharatsuneja@no.spam.org> wrote in message
news:%231VEtAeyFHA.1552@TK2MSFTNGP10.phx.gbl...
| Quote: | You can partition the dns namespace to assign email addresses based on
location - so all users at Site1 have email addresses as
site1(orwhatever).domain.com and same thing for site2. Next, mx records
for the sub-domains site1.domain.com pointing to exch in site1, same thing
for site2.
A better solution would be to not go this route and not play with the
namespace at all.
- Let everyone have default @yourdomain.com email addresses, and make sure
both sites have vpn connectivity.
- You can have MX records pointing at both Exchange servers, the one with
higher priority (lowest value in MX record) pointing at Exch1 in primary
site, and the second one pointing to Exch2 in second site.
- This will require both sites to have Internet connectivity, and allow
smtp traffic to the Exch server from the Internet.
- If Site1 goes down, Site2 will continue to receive mail which will be
delivered to local users immediately. Mail for Site1 users will be queued
till Exchange in Site1 is up.
--
Bharat Suneja
MCSE, MCT
-------------------------------- |
|
|
| Back to top |
|
|
MSNEWS
Guest
|
| Posted:
Thu Oct 06, 2005 4:58 pm Post subject:
Re: Exchange Servers at different sites |
|
|
I would look at keeping it to one Exchange server and have all the clients
use Outlook 2003 Cached Exchange mode, either over HTTP or a site-to-site
VPN. I have well over 100 users doing this where _none_ of the clients are
located in the same facility as the server, and it works well.
The servers are located in a rack elsewhere and my office runs a DC/GC
connected to them via a site-to-site VPN, but you may not even need to
deploy remote domain controllers if all you care about is mail. |
|
| Back to top |
|
|
ckoymen
Guest
|
| Posted:
Thu Oct 06, 2005 4:58 pm Post subject:
Re: Exchange Servers at different sites |
|
|
Well, sorry not to mention couple of details;
we have approx. 100 users at each site.
Users communicate clients with emails at all time. Mostly these emails
include file attachments (approx 2mb.).
we need redundancy procedure, this is the another reason that we decided to
go for 2nd exchange server.
Your solution is so attractive and more easy to setup really, msnews, I wish
I would setup like that.
But I'm not sure if our les10 conn. will support, GC Replication, file
sharing, mail sending/receiving, digital phone conn., etc.
Redundancy, storage, fast communication are my other concerns.
Also we bought 2 exch. server (std. edition) and cals already. So I need to
use them lol!
Thank you.
"MSNEWS" <dlwest@gmail.com> wrote in message
news:eaQB5eoyFHA.1028@TK2MSFTNGP12.phx.gbl...
| Quote: | I would look at keeping it to one Exchange server and have all the clients
use Outlook 2003 Cached Exchange mode, either over HTTP or a site-to-site
VPN. I have well over 100 users doing this where _none_ of the clients are
located in the same facility as the server, and it works well.
The servers are located in a rack elsewhere and my office runs a DC/GC
connected to them via a site-to-site VPN, but you may not even need to
deploy remote domain controllers if all you care about is mail.
|
|
|
| Back to top |
|
|
Bharat Suneja
Guest
|
| Posted:
Thu Oct 06, 2005 4:58 pm Post subject:
Re: Exchange Servers at different sites |
|
|
- You're right, they know about all *mail recipients* (users, mail-enabled
groups/contacts, etc.) from AD
- Exchange servers in the same Organization can deliver mail to any
recipient in the org - they simply lookup the user's properties in AD to
determine where the user's mailbox resides and then deliver to that server
(or a Bridgehead if in different Routing Groups... ). So you don't really
need to tell an Exchange server how to pick up mail from another Exchange
server
- If the servers are in different Routing Groups, you need to create a
Connector at each end to connect those Routing Groups. In your case, you
will have only 2 servers so you don't really need to create separate Routing
Groups.
- If the server where recipient's mailbox resides is down, the sending
server will hold it and deliver when it detects the server is up again.
--
Bharat Suneja
MCSE, MCT
--------------------------------
"ckoymen" <ckoymen@hotmail.com> wrote in message
news:etfEUSlyFHA.460@TK2MSFTNGP15.phx.gbl...
| Quote: | Thanks for your suggestion Bharat.
So, as far as I understand, please correct me if I'm wrong, for your
second solution which looks more logical, if one of the exch. servers
would go down, those user's emails will be queued. Users will moan a bit,
but at least we're not going to make so much stress at Les10 bandwith
connection.
Sorry for my ignorance, but when they both in the same domain, they will
replicate eachother (won't they?) and both exch. servers will see the list
of users via common active directory. how would I tell exch1 to pick up
emails of user which is located on that site and the same thing for the
other site?
Thanks for your help again.
Cenk
"Bharat Suneja" <bharatsuneja@no.spam.org> wrote in message
news:%231VEtAeyFHA.1552@TK2MSFTNGP10.phx.gbl...
You can partition the dns namespace to assign email addresses based on
location - so all users at Site1 have email addresses as
site1(orwhatever).domain.com and same thing for site2. Next, mx records
for the sub-domains site1.domain.com pointing to exch in site1, same
thing for site2.
A better solution would be to not go this route and not play with the
namespace at all.
- Let everyone have default @yourdomain.com email addresses, and make
sure both sites have vpn connectivity.
- You can have MX records pointing at both Exchange servers, the one with
higher priority (lowest value in MX record) pointing at Exch1 in primary
site, and the second one pointing to Exch2 in second site.
- This will require both sites to have Internet connectivity, and allow
smtp traffic to the Exch server from the Internet.
- If Site1 goes down, Site2 will continue to receive mail which will be
delivered to local users immediately. Mail for Site1 users will be queued
till Exchange in Site1 is up.
--
Bharat Suneja
MCSE, MCT
--------------------------------
|
|
|
| Back to top |
|
|
David L. West
Guest
|
| Posted:
Thu Oct 06, 2005 10:16 pm Post subject:
Re: Exchange Servers at different sites |
|
|
I haven't tried this myself, but I think what you'd want to do is first set
up the Active Directory infrastructure such that all the sites were
connected with site-to-site VPN. Once that's up and going you should be
able to put Exchange Servers where you need them and have each set of users
connect to the one at their site. Pretty sure that Exchange will handle
routing between the servers more or less on its own; the master would be the
one that receives internet mail and would route things to the appropriate
message store on the other Exchange server. Maybe somebody else with more
experience with this sort of configuration can chime in, but I'm reasonably
confident that if you set up the site-to-site connections properly you can
get where you want to be.
"ckoymen" <ckoymen@hotmail.com> wrote in message
news:eCMC24oyFHA.664@tk2msftngp13.phx.gbl...
| Quote: | Well, sorry not to mention couple of details;
we have approx. 100 users at each site.
Users communicate clients with emails at all time. Mostly these emails
include file attachments (approx 2mb.).
we need redundancy procedure, this is the another reason that we decided
to go for 2nd exchange server.
Your solution is so attractive and more easy to setup really, msnews, I
wish I would setup like that.
But I'm not sure if our les10 conn. will support, GC Replication, file
sharing, mail sending/receiving, digital phone conn., etc.
Redundancy, storage, fast communication are my other concerns.
Also we bought 2 exch. server (std. edition) and cals already. So I need
to use them lol!
Thank you.
"MSNEWS" <dlwest@gmail.com> wrote in message
news:eaQB5eoyFHA.1028@TK2MSFTNGP12.phx.gbl...
I would look at keeping it to one Exchange server and have all the clients
use Outlook 2003 Cached Exchange mode, either over HTTP or a site-to-site
VPN. I have well over 100 users doing this where _none_ of the clients
are located in the same facility as the server, and it works well.
The servers are located in a rack elsewhere and my office runs a DC/GC
connected to them via a site-to-site VPN, but you may not even need to
deploy remote domain controllers if all you care about is mail.
|
|
|
| Back to top |
|
|
ckoymen
Guest
|
| Posted:
Fri Oct 07, 2005 12:58 am Post subject:
Re: Exchange Servers at different sites |
|
|
I got it Bharat, thanks for your suggestions. I'll set up test servers and
try your design. I'll inform you when I get the results. Thanks a lot again.
"Bharat Suneja" <bharatsuneja@no.spam.org> wrote in message
news:ub4TqNpyFHA.2312@TK2MSFTNGP14.phx.gbl...
| Quote: | - You're right, they know about all *mail recipients* (users, mail-enabled
groups/contacts, etc.) from AD
- Exchange servers in the same Organization can deliver mail to any
recipient in the org - they simply lookup the user's properties in AD to
determine where the user's mailbox resides and then deliver to that
server (or a Bridgehead if in different Routing Groups... ). So you don't
really need to tell an Exchange server how to pick up mail from another
Exchange server
- If the servers are in different Routing Groups, you need to create a
Connector at each end to connect those Routing Groups. In your case, you
will have only 2 servers so you don't really need to create separate
Routing Groups.
- If the server where recipient's mailbox resides is down, the sending
server will hold it and deliver when it detects the server is up again.
--
Bharat Suneja
MCSE, MCT
--------------------------------
"ckoymen" <ckoymen@hotmail.com> wrote in message
news:etfEUSlyFHA.460@TK2MSFTNGP15.phx.gbl...
Thanks for your suggestion Bharat.
So, as far as I understand, please correct me if I'm wrong, for your
second solution which looks more logical, if one of the exch. servers
would go down, those user's emails will be queued. Users will moan a bit,
but at least we're not going to make so much stress at Les10 bandwith
connection.
Sorry for my ignorance, but when they both in the same domain, they will
replicate eachother (won't they?) and both exch. servers will see the
list of users via common active directory. how would I tell exch1 to pick
up emails of user which is located on that site and the same thing for
the other site?
Thanks for your help again.
Cenk
"Bharat Suneja" <bharatsuneja@no.spam.org> wrote in message
news:%231VEtAeyFHA.1552@TK2MSFTNGP10.phx.gbl...
You can partition the dns namespace to assign email addresses based on
location - so all users at Site1 have email addresses as
site1(orwhatever).domain.com and same thing for site2. Next, mx records
for the sub-domains site1.domain.com pointing to exch in site1, same
thing for site2.
A better solution would be to not go this route and not play with the
namespace at all.
- Let everyone have default @yourdomain.com email addresses, and make
sure both sites have vpn connectivity.
- You can have MX records pointing at both Exchange servers, the one
with higher priority (lowest value in MX record) pointing at Exch1 in
primary site, and the second one pointing to Exch2 in second site.
- This will require both sites to have Internet connectivity, and allow
smtp traffic to the Exch server from the Internet.
- If Site1 goes down, Site2 will continue to receive mail which will be
delivered to local users immediately. Mail for Site1 users will be
queued till Exchange in Site1 is up.
--
Bharat Suneja
MCSE, MCT
--------------------------------
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in