Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Exchange Server / Design / February 2005

Tip: Looking for answers? Try searching our database.

Exchange 5.5 to 2003, Single Org, Multi-Domain, Multi-Site

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Tony Scarola - 14 Feb 2005 19:13 GMT
Hello all.

We currently have two domains (domain A = Windows 2003 at operations, domain
B = Windows 2000 at branch) joined by two-way trusts, split across a T1 WAN
connection (1.544 Mbps). The branch office has less than 120 users. We
currently have one Exchange 5.5 server at each location, configured as a
single organization, dual-site system. These two are connected using a Site
Connector and Directory Replication Connector.

We need to accomplish two things; the first being to merge domain B into
domain A (I realize that this is for another newsgroup), however, from what
I understand about this, my ADMT should take care of resetting the
permissions on the mailboxes of the branch Exchange 5.5 server to reflect
the merged/migrated user accounts. We would love to also consolidate the
Exchange servers into one Exchange 2003 Server, however, I am concerned that
there will be bandwidth issues. I have read that Exchange 2003 has the
capability to do so with it's over-the-wire MAPI compression and client-side
caching, however, I really do not want to cause much delay to the end users
at the remote branch. Should I simply plan on having an Exchange 2003 server
at the remote site? Are there any guidelines available when dealing with
bandwidth issues, server consolidations from Exchange 5.5 multi-site to
Exchange 2003 single site via T1 connection? Any recommendations? What have
others experienced?

Thank you in advance,

Tony
Don Wilwol - 14 Feb 2005 22:33 GMT
There are some considerations you need to look at. When you consolidate will
you have a DC at the second site. You will need one if you are going to put
an exchange server there.

You can use Exchange RPC over HTTP as long as you are using outlook 2003 in
caching mode. You could also use OWA. The best way to tell for sure is to
test it. It has a lot to do with your current bandwidth utilization, and
what you consider as acceptable performance.

Signature

Hope it helps...........

dw

Don Wilwol
Blog - http://spaces.msn.com/members/wilwol/
Web - http://capital.net/~wilwol/dw.htm
DonWilwol@yahoo.com

> Hello all.
>
[quoted text clipped - 23 lines]
>
> Tony
Tony Scarola - 15 Feb 2005 00:48 GMT
Yes, 2003 DC at second site with Global Catalog services. I understand that
I need Outlook 2003 to take care of the caching services. Looks like I will
need to setup a second Exchange 2003 Server at second site until we get
Outlook 2003 rolled out.

Thank you.

> There are some considerations you need to look at. When you consolidate
> will you have a DC at the second site. You will need one if you are going
[quoted text clipped - 32 lines]
>>
>> Tony
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.