RE: Best solution for merging EX servers??

2001-11-15 Thread Andy David

We're still talking about Exchange here right?


-Original Message-
From: Roger Seielstad [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 15, 2001 7:04 AM
To: Exchange Discussions
Subject: RE: Best solution for merging EX servers??


We are going to need to patch him, then. I still receive the I'm just a
fvcking contractor error during use.

--
Roger D. Seielstad - MCSE MCT
Senior Systems Administrator
Peregrine Systems
Atlanta, GA
http://www.peregrine.com


 -Original Message-
 From: Doug Hampshire [mailto:[EMAIL PROTECTED]]
 Sent: Wednesday, November 14, 2001 3:52 PM
 To: Exchange Discussions
 Subject: RE: Best solution for merging EX servers??
 
 
 Remember, we upgraded Jeff Mr. CSV Eskens from fvcking 
 contractor to
 fvcking employee last year. It still requires the MGD even 
 number bolt on
 adaptor though.
 
 -Original Message-
 From: Roger Seielstad [mailto:[EMAIL PROTECTED]] 
 Sent: Wednesday, November 14, 2001 3:57 AM
 To: Exchange Discussions
 Subject: RE: Best solution for merging EX servers??
 
 
 Let's not forget that the Roger Ex-Merge Seielstad tool 
 works best when
 used in conjunction with the Jeff Mr. CSV Eskens add-on.
 
 Please note that the Jeff Mr. CSV Eskens add-on tends to 
 mutter I'm just
 a fvcking contractor and requires large quantities of a 
 substance known as
 MGD, in even numbers only.
 
 --
 Roger D. Seielstad - MCSE MCT
 Senior Systems Administrator
 Peregrine Systems
 Atlanta, GA
 http://www.peregrine.com
 
 
  -Original Message-
  From: Doug Hampshire [mailto:[EMAIL PROTECTED]]
  Sent: Tuesday, November 13, 2001 1:49 PM
  To: Exchange Discussions
  Subject: RE: Best solution for merging EX servers??
  
  
  I generally use the Roger Ex-Merge Seielstad tool in
  situations like this.
  It's not a perfect tool, it does tend to whine and demand 
  being fed on a
  regular basis, but it also gets the job done. For the right 
  price I might be
  willing to rent you the tool (price includes my small 
  management fee of
  course).
  
  -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

RE: Best solution for merging EX servers??

2001-11-15 Thread Roger Seielstad

Yes.

You met Jeff Mr. CSV Eskens at MEC. He was easy to find - always had 2
MGD's in his hands.

--
Roger D. Seielstad - MCSE MCT
Senior Systems Administrator
Peregrine Systems
Atlanta, GA
http://www.peregrine.com


 -Original Message-
 From: Andy David [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, November 15, 2001 7:24 AM
 To: Exchange Discussions
 Subject: RE: Best solution for merging EX servers??
 
 
 We're still talking about Exchange here right?
 
 
 -Original Message-
 From: Roger Seielstad [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, November 15, 2001 7:04 AM
 To: Exchange Discussions
 Subject: RE: Best solution for merging EX servers??
 
 
 We are going to need to patch him, then. I still receive the 
 I'm just a
 fvcking contractor error during use.
 
 --
 Roger D. Seielstad - MCSE MCT
 Senior Systems Administrator
 Peregrine Systems
 Atlanta, GA
 http://www.peregrine.com
 
 
  -Original Message-
  From: Doug Hampshire [mailto:[EMAIL PROTECTED]]
  Sent: Wednesday, November 14, 2001 3:52 PM
  To: Exchange Discussions
  Subject: RE: Best solution for merging EX servers??
  
  
  Remember, we upgraded Jeff Mr. CSV Eskens from fvcking 
  contractor to
  fvcking employee last year. It still requires the MGD even 
  number bolt on
  adaptor though.
  
  -Original Message-
  From: Roger Seielstad [mailto:[EMAIL PROTECTED]] 
  Sent: Wednesday, November 14, 2001 3:57 AM
  To: Exchange Discussions
  Subject: RE: Best solution for merging EX servers??
  
  
  Let's not forget that the Roger Ex-Merge Seielstad tool 
  works best when
  used in conjunction with the Jeff Mr. CSV Eskens add-on.
  
  Please note that the Jeff Mr. CSV Eskens add-on tends to 
  mutter I'm just
  a fvcking contractor and requires large quantities of a 
  substance known as
  MGD, in even numbers only.
  
  --
  Roger D. Seielstad - MCSE MCT
  Senior Systems Administrator
  Peregrine Systems
  Atlanta, GA
  http://www.peregrine.com
  
  
   -Original Message-
   From: Doug Hampshire [mailto:[EMAIL PROTECTED]]
   Sent: Tuesday, November 13, 2001 1:49 PM
   To: Exchange Discussions
   Subject: RE: Best solution for merging EX servers??
   
   
   I generally use the Roger Ex-Merge Seielstad tool in
   situations like this.
   It's not a perfect tool, it does tend to whine and demand 
   being fed on a
   regular basis, but it also gets the job done. For the right 
   price I might be
   willing to rent you the tool (price includes my small 
   management fee of
   course).
   
   -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

RE: Best solution for merging EX servers??

2001-11-15 Thread John Matteson

For edification and clarification:

MGD = Miller Genuine Draft?

John Matteson; Exchange Manager
Geac Corporate Infrastructure Systems and Standards
(404) 239 - 2981

With sufficient thrust, pigs fly just fine. - RFC 1925



-Original Message-
From: Roger Seielstad [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 15, 2001 7:38 AM
To: Exchange Discussions
Subject: RE: Best solution for merging EX servers??


Yes.

You met Jeff Mr. CSV Eskens at MEC. He was easy to find - always had 2
MGD's in his hands.

--
Roger D. Seielstad - MCSE MCT
Senior Systems Administrator
Peregrine Systems
Atlanta, GA
http://www.peregrine.com


 -Original Message-
 From: Andy David [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, November 15, 2001 7:24 AM
 To: Exchange Discussions
 Subject: RE: Best solution for merging EX servers??
 
 
 We're still talking about Exchange here right?
 
 
 -Original Message-
 From: Roger Seielstad [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, November 15, 2001 7:04 AM
 To: Exchange Discussions
 Subject: RE: Best solution for merging EX servers??
 
 
 We are going to need to patch him, then. I still receive the 
 I'm just a
 fvcking contractor error during use.
 
 --
 Roger D. Seielstad - MCSE MCT
 Senior Systems Administrator
 Peregrine Systems
 Atlanta, GA
 http://www.peregrine.com
 
 
(This remainder of this message has been clipped and recycled using an
environmentally sound method)

_
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]



RE: Best solution for merging EX servers??

2001-11-15 Thread Roger Seielstad

Yes.

--
Roger D. Seielstad - MCSE MCT
Senior Systems Administrator
Peregrine Systems
Atlanta, GA
http://www.peregrine.com


 -Original Message-
 From: John Matteson [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, November 15, 2001 10:27 AM
 To: Exchange Discussions
 Subject: RE: Best solution for merging EX servers??
 
 
 For edification and clarification:
 
   MGD = Miller Genuine Draft?
 
 John Matteson; Exchange Manager
 Geac Corporate Infrastructure Systems and Standards
 (404) 239 - 2981
 
 With sufficient thrust, pigs fly just fine. - RFC 1925
 
 
 
 -Original Message-
 From: Roger Seielstad [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, November 15, 2001 7:38 AM
 To: Exchange Discussions
 Subject: RE: Best solution for merging EX servers??
 
 
 Yes.
 
 You met Jeff Mr. CSV Eskens at MEC. He was easy to find - 
 always had 2
 MGD's in his hands.
 
 --
 Roger D. Seielstad - MCSE MCT
 Senior Systems Administrator
 Peregrine Systems
 Atlanta, GA
 http://www.peregrine.com
 
 
  -Original Message-
  From: Andy David [mailto:[EMAIL PROTECTED]]
  Sent: Thursday, November 15, 2001 7:24 AM
  To: Exchange Discussions
  Subject: RE: Best solution for merging EX servers??
  
  
  We're still talking about Exchange here right?
  
  
  -Original Message-
  From: Roger Seielstad [mailto:[EMAIL PROTECTED]]
  Sent: Thursday, November 15, 2001 7:04 AM
  To: Exchange Discussions
  Subject: RE: Best solution for merging EX servers??
  
  
  We are going to need to patch him, then. I still receive the 
  I'm just a
  fvcking contractor error during use.
  
  --
  Roger D. Seielstad - MCSE MCT
  Senior Systems Administrator
  Peregrine Systems
  Atlanta, GA
  http://www.peregrine.com
  
  
 (This remainder of this message has been clipped and recycled using an
 environmentally sound method)
 
 _
 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]



RE: Best solution for merging EX servers??

2001-11-14 Thread Ed Crowley

Spell checkers are for wimps.

Ed Crowley MCSE+I MVP
Tech Consultant
Compaq Computer
There are seldom good technological solutions to behavioral problems.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Doug Hampshire
Sent: Tuesday, November 13, 2001 10:51 AM
To: Exchange Discussions
Subject: RE: Best solution for merging EX servers??


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]

_
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]



RE: Best solution for merging EX servers??

2001-11-14 Thread Roger Seielstad

Let's not forget that the Roger Ex-Merge Seielstad tool works best when
used in conjunction with the Jeff Mr. CSV Eskens add-on.

Please note that the Jeff Mr. CSV Eskens add-on tends to mutter I'm just
a fvcking contractor and requires large quantities of a substance known as
MGD, in even numbers only.

--
Roger D. Seielstad - MCSE MCT
Senior Systems Administrator
Peregrine Systems
Atlanta, GA
http://www.peregrine.com


 -Original Message-
 From: Doug Hampshire [mailto:[EMAIL PROTECTED]]
 Sent: Tuesday, November 13, 2001 1:49 PM
 To: Exchange Discussions
 Subject: RE: Best solution for merging EX servers??
 
 
 I generally use the Roger Ex-Merge Seielstad tool in 
 situations like this.
 It's not a perfect tool, it does tend to whine and demand 
 being fed on a
 regular basis, but it also gets the job done. For the right 
 price I might be
 willing to rent you the tool (price includes my small 
 management fee of
 course).
 
 -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]
 

_
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]



RE: Best solution for merging EX servers??

2001-11-14 Thread Doug Hampshire

Remember, we upgraded Jeff Mr. CSV Eskens from fvcking contractor to
fvcking employee last year. It still requires the MGD even number bolt on
adaptor though.

-Original Message-
From: Roger Seielstad [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, November 14, 2001 3:57 AM
To: Exchange Discussions
Subject: RE: Best solution for merging EX servers??


Let's not forget that the Roger Ex-Merge Seielstad tool works best when
used in conjunction with the Jeff Mr. CSV Eskens add-on.

Please note that the Jeff Mr. CSV Eskens add-on tends to mutter I'm just
a fvcking contractor and requires large quantities of a substance known as
MGD, in even numbers only.

--
Roger D. Seielstad - MCSE MCT
Senior Systems Administrator
Peregrine Systems
Atlanta, GA
http://www.peregrine.com


 -Original Message-
 From: Doug Hampshire [mailto:[EMAIL PROTECTED]]
 Sent: Tuesday, November 13, 2001 1:49 PM
 To: Exchange Discussions
 Subject: RE: Best solution for merging EX servers??
 
 
 I generally use the Roger Ex-Merge Seielstad tool in
 situations like this.
 It's not a perfect tool, it does tend to whine and demand 
 being fed on a
 regular basis, but it also gets the job done. For the right 
 price I might be
 willing to rent you the tool (price includes my small 
 management fee of
 course).
 
 -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]
 

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com

Best solution for merging EX servers??

2001-11-13 Thread Alex Alborzfard

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]



Re: Best solution for merging EX servers??

2001-11-13 Thread Tony Hlabse

Actually this could be done with little work. You will need to setup some
trusts between for administrative purposes and x400 connectors for com.
between the differnent orgs. Add a new email domanin to the company being
purchased and add the new email addresses as needed. They is more but that
should start you in the right direction. How many users that are being
brought into the mother company. If in the thousands then you will want to
write a script to add the new email addresses.

- Original Message -
From: Alex Alborzfard [EMAIL PROTECTED]
To: Exchange Discussions [EMAIL PROTECTED]
Sent: Tuesday, November 13, 2001 12:57 PM
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]



RE: Best solution for merging EX servers??

2001-11-13 Thread Roger Seielstad

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]



RE: Best solution for merging EX servers??

2001-11-13 Thread Doug Hampshire

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]