Curious factoid - My spel chucker suggests that Siesta is the correct spelling for Seielstad. Coincidence? I think not.
-----Original Message----- From: Roger Seielstad [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 13, 2001 10:42 AM To: Exchange Discussions Subject: RE: Best solution for merging EX servers?? That's really a consulting question - much more in depth that you're going to get out of a mailing list like this. I can recommend some very good folks, depending on where you are located. ------------------------------------------------------ Roger D. Seielstad - MCSE MCT Senior Systems Administrator Peregrine Systems Atlanta, GA http://www.peregrine.com > -----Original Message----- > From: Alex Alborzfard [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, November 13, 2001 12:58 PM > To: Exchange Discussions > Subject: Best solution for merging EX servers?? > > > Scenario > ----------- > > Company X has merged with company Y. > > Company X has 2 locations: > East Coast - 1 EX 5.5 SP4 on NT 4, responsible for > X.com domain's mail > UK - NONE (Using East coast mail > server via Internet) > Company Y has 2 locations: > West Coast - 1 EX 5.5 SP4 on NT 4, responsible for > Y-west.com domain's mail > East Coast - 2 EX 5.5 SP4 on NT 4, > responsible for > Y-east.com domain's mail > > Following is the connections between these sites: > > X - Y(East) : 512kbps (FR) > Y(West) - Y(East) : 256kbps (FR) > Y(East) - FR Cloud : 512kbps (FR) > > X and Y(West) have to go through Y(East) to connect to Internet. > > (There are additional/backup Internet connections as follows:) > > X - Internet(backup): 384kbps (DSL) > X(UK) - Internet: 128kbps (ISDN) > Y(East) - Internet: 768kbps (T1) > > Needs > -------- > > 1- The new company has taken the name X and wants all > employees in all 3 > locations to receive email > sent to "[EMAIL PROTECTED]". This should be done without any or > minimum email > service interruption. > > 2- Provide a fault-tolerant solution, in case one of the EX > servers goes > down or loses it's Internet connection. > > 3- Company wants to move EX2K at some point in the future. > Should it wait to > merge first and > then migrate or migrate first and then merge? > > > > Solutions > ----------- > > 1- What type of connector and why? > 2- How should the DNS MX records be arranged? > 3- What are pluses & minuses for each merge now versus migrate now > scenarios? > > > > Let me know if you need more information. > > Thanks > > > > _________________________________________________________________ > 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] _________________________________________________________________ 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]
