| Author |
Message |
Tony Scarola
Guest
|
 Posted:
Tue Feb 15, 2005 1:13 am Post subject:
Exchange 5.5 to 2003, Single Org, Multi-Domain, Multi-Site |
|
|
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
|
|
| Back to top |
|
 |
Don Wilwol
Guest
|
| Posted:
Tue Feb 15, 2005 4:33 am Post subject:
Re: Exchange 5.5 to 2003, Single Org, Multi-Domain, Multi-Si |
|
|
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.
--
Hope it helps...........
dw
Don Wilwol
Blog - http://spaces.msn.com/members/wilwol/
Web - http://capital.net/~wilwol/dw.htm
DonWilwol@yahoo.com
"Tony Scarola" <tony.scarola@discussions.microsoft.com> wrote in message
news:%237yIXlsEFHA.2756@TK2MSFTNGP15.phx.gbl...
| Quote: | 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
|
|
|
| Back to top |
|
|
Tony Scarola
Guest
|
| Posted:
Tue Feb 15, 2005 6:48 am Post subject:
Re: Exchange 5.5 to 2003, Single Org, Multi-Domain, Multi-Si |
|
|
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.
"Don Wilwol" <donwilwol@yahoo.com> wrote in message
news:uE7I9UuEFHA.3648@TK2MSFTNGP10.phx.gbl...
| Quote: | 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.
--
Hope it helps...........
dw
Don Wilwol
Blog - http://spaces.msn.com/members/wilwol/
Web - http://capital.net/~wilwol/dw.htm
DonWilwol@yahoo.com
"Tony Scarola" <tony.scarola@discussions.microsoft.com> wrote in message
news:%237yIXlsEFHA.2756@TK2MSFTNGP15.phx.gbl...
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
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in