| Author |
Message |
Brett
Guest
|
 Posted:
Thu Oct 28, 2004 9:41 pm Post subject:
Exchange 2003 across sites |
|
|
My company has a headquarters in MI with 30 users and remote offices
in FL and IL with about 10-15 users each. Currently, we have a single
domain, single AD site, and single Exchange site for all offices. The
remote users are connected over a WAN link and retrieve e-mail, files,
etc. from the main office. Due to complaints by remote users over
reliability and slow access, we purchased a server for each location
that would replicate files, provide print services, and possibly
e-mail. To accomplish the file replication I was going to create 2
additional sites within our existing domain. My question is: does it
make sense to purchase Exchange 2003 server for the remote sites, and
if so are there any issues that I need to be aware of (should I create
additional Exchange sites, etc)? Simply retrieving new e-mail from
the server in MI doesn't seem to be so bad to me. All users have
Outlook 2003 in Cached Mode, which I believe should provide the speed
they need. If the WAN connection is down, they have separate internet
access in each location so they could just use OWA. Thanks in advance
for the feedback!
|
|
| Back to top |
|
 |
Al Mulnick
Guest
|
| Posted:
Fri Oct 29, 2004 6:24 am Post subject:
Re: Exchange 2003 across sites |
|
|
Have you considered allowing RPC/HTTP? It fails over nicely and if in
cached mode they may not notice.
As a general rule, I would hate to put something like Email servers in a
small office with nobody around to watch after it. It's just screaming for
issues to occur.
Putting it centrally and making sure there is enough performance on the
central server is a good idea. You don't want them to wait any longer than
the network. Performance won't be any faster than the weakest link in the
conversation, so the network can still play a part.
If it gets too bad, let them get it via RPC/HTTP over the internet as normal
course and they can rest assured they won't get it faster anywhere else.
That's off the cuff. I don't really know enough about your environment to
make a better suggestion at this point. For example, I don't know what
expectations are, what the components are, what the available bandwidth is
at all times and at times of complaints, etc.
Al
"Brett" <brett_thelen@mail.com> wrote in message
news:96c689c.0410280841.3ae3d220@posting.google.com...
| Quote: | My company has a headquarters in MI with 30 users and remote offices
in FL and IL with about 10-15 users each. Currently, we have a single
domain, single AD site, and single Exchange site for all offices. The
remote users are connected over a WAN link and retrieve e-mail, files,
etc. from the main office. Due to complaints by remote users over
reliability and slow access, we purchased a server for each location
that would replicate files, provide print services, and possibly
e-mail. To accomplish the file replication I was going to create 2
additional sites within our existing domain. My question is: does it
make sense to purchase Exchange 2003 server for the remote sites, and
if so are there any issues that I need to be aware of (should I create
additional Exchange sites, etc)? Simply retrieving new e-mail from
the server in MI doesn't seem to be so bad to me. All users have
Outlook 2003 in Cached Mode, which I believe should provide the speed
they need. If the WAN connection is down, they have separate internet
access in each location so they could just use OWA. Thanks in advance
for the feedback! |
|
|
| Back to top |
|
|
Brett
Guest
|
| Posted:
Fri Oct 29, 2004 8:11 pm Post subject:
Re: Exchange 2003 across sites |
|
|
Thank you very much for the suggestion! I wasn't very familiar with
RPC/HTTP until you mentioned it and it seems like a great solution.
Thanks!
"Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> wrote in message news:<#nLAXYVvEHA.908@TK2MSFTNGP11.phx.gbl>...
| Quote: | Have you considered allowing RPC/HTTP? It fails over nicely and if in
cached mode they may not notice.
As a general rule, I would hate to put something like Email servers in a
small office with nobody around to watch after it. It's just screaming for
issues to occur.
Putting it centrally and making sure there is enough performance on the
central server is a good idea. You don't want them to wait any longer than
the network. Performance won't be any faster than the weakest link in the
conversation, so the network can still play a part.
If it gets too bad, let them get it via RPC/HTTP over the internet as normal
course and they can rest assured they won't get it faster anywhere else.
That's off the cuff. I don't really know enough about your environment to
make a better suggestion at this point. For example, I don't know what
expectations are, what the components are, what the available bandwidth is
at all times and at times of complaints, etc.
Al
"Brett" <brett_thelen@mail.com> wrote in message
news:96c689c.0410280841.3ae3d220@posting.google.com...
My company has a headquarters in MI with 30 users and remote offices
in FL and IL with about 10-15 users each. Currently, we have a single
domain, single AD site, and single Exchange site for all offices. The
remote users are connected over a WAN link and retrieve e-mail, files,
etc. from the main office. Due to complaints by remote users over
reliability and slow access, we purchased a server for each location
that would replicate files, provide print services, and possibly
e-mail. To accomplish the file replication I was going to create 2
additional sites within our existing domain. My question is: does it
make sense to purchase Exchange 2003 server for the remote sites, and
if so are there any issues that I need to be aware of (should I create
additional Exchange sites, etc)? Simply retrieving new e-mail from
the server in MI doesn't seem to be so bad to me. All users have
Outlook 2003 in Cached Mode, which I believe should provide the speed
they need. If the WAN connection is down, they have separate internet
access in each location so they could just use OWA. Thanks in advance
for the feedback! |
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in