Intrasite communications[1] between servers in E2K is substantially less chatty. Routing groups don't have the same intense high bandwidth requirements one generally saw imposed with Exchange 5.5.
[1] Or more properly intr-routing group. On 4/2/03 10:56, "ml.exchange" <[EMAIL PROTECTED]> wrote: > We are beginning the planning for our AD migration to be followed by Exchange > 5.5 to 2K3 migration. I am looking for ideas to correct 1 main shortcoming of > our 5.5 Org. > > We have 5 remote offices connected to our main office in Atlanta via 256k > frame relay. We have a Exchange server in Atlanta that runs Atlanta mail and > the > IMC for all the other servers. Each office has a separate BDC/File server and > Exchange 5.5 server. > > The problem is that the remote servers were not deployed as separate sites, > but as servers under our Atlanta site (all 6 servers are in one Exchange site > but different physical sites and subnets). I have two questions on this > configuration. > 1) Is this going to be a problem moving forward to future versions of > exchange? > 2) If so what would be the best way to fix it, either before the upgrade or > post/during the upgrade at each site? > > Thanks for your insights! > > Miles > > ----------------------- > Miles Holt > Network Engineer > Summit Marketing > [EMAIL PROTECTED] > 770-303-0426 > ----------------------- > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
