RE: Exchange 2000 migration issues

2002-06-06 Thread Crosby, Tim (Sarcom)
Title: Message



Thanks 
William, that's exactly what I was looking for.

  
  -Original Message-From: William 
  Lefkovics [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 
  05, 2002 7:52 PMTo: MS-Exchange Admin IssuesSubject: RE: 
  Exchange 2000 migration issues
  There is a specific whitepaper on the 
  process:
  http://www.microsoft.com/Exchange/techinfo/deployment/2000/UpgradeFolders.asp
   
  1) 
  create public folder agreement (which is two way) in ADC.
  2) 
  configure permissions and remove bad accounts.
  3) 
  set replicas to migrate data
   
  Rehoming and removal of 5.5 are covered in the 
  migration docs as well.
  In 
  Exchange2000, you can rehome by top level folder and 
  propogate:
  http://support.microsoft.com/default.aspx?scid=kb;EN-US;q288150
   
  And 
  don't forget the chats on June 19:
  http://www.microsoft.com/technet/treeview/default.asp?url=/technet/itcommunity/chats/default.asp
   
  William
   
  

-Original Message-From: Crosby, Tim 
(Sarcom) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 
05, 2002 4:12 PMTo: MS-Exchange Admin IssuesSubject: 
RE: Exchange 2000 migration issues

Thanks William, we 
are planning to get rid of 5.5 as soon as we feel like the 2000 Server is 
running OK.  What is the easiest 
way to get the public folders moved over?  Right now, we are going into each 
folder and setting it to replicate to E2k, but then we'll wait until it has 
replicated and go back in and remove it from E55.  But don't you also then have to set 
the "home server" for each folder to be the new E2k?  Isn't there a simpler way than going 
into properties on each folder and doing this?  
 
-Original 
Message-From: William 
Lefkovics [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 6:18 
PMTo: MS-Exchange Admin 
    IssuesSubject: RE: 
Exchange 2000 migration issues
 

The 
requirement of patience can not be 
underestimated.

 

Use 
the E2K tools to admin E2K and the 5.5 tools to admin 
5.5.

 

If 
it's single server, single site, minimize co-existence.  Get the 
mailboxes and public folders moved then free yourself of the ADC and 
5.5.

 
-Original 
  Message-From: 
  Crosby, Tim (Sarcom) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 8:15 
  AMTo: MS-Exchange Admin 
  IssuesSubject: Exchange 
  2000 migration issues
  We are in the middle of 
  migrating our single site, single server organization over to Exchange 
  2000.  We have setup the ADC and run ForestPrep.  Everything 
  seems cool so far.  All accounts seem to be syncing in AD.  We 
  are at the point now where we are going to build the E2k box, join the 5.5 
  site and start moving mailboxes.  What I'd like to know is what to 
  look out for once users are moved over.  What should we test 
  specifically to make sure that the moved mailboxes work?  I have a 
  few obvious ones in mind, check sending and receiving internet mail, check 
  calendar availability, GAL, sending from E2k to E5.5, etc.  Is there 
  a list of all the things you should test in order to make sure the E2k box 
  is working properly?  What problems have you all run into when moving 
  to E2k?
  Thanks, 
  
  Tim 
  
  List Charter and FAQ 
  at:http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ 
at:http://www.sunbelt-software.com/exchange_list_charter.htmList 
Charter and FAQ 
at:http://www.sunbelt-software.com/exchange_list_charter.htmList 
  Charter and FAQ 
  at:http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm





RE: Exchange 2000 migration issues

2002-06-05 Thread William Lefkovics
Title: Message



There 
is a specific whitepaper on the process:
http://www.microsoft.com/Exchange/techinfo/deployment/2000/UpgradeFolders.asp
 
1) 
create public folder agreement (which is two way) in ADC.
2) 
configure permissions and remove bad accounts.
3) set 
replicas to migrate data
 
Rehoming and removal of 5.5 are covered in the 
migration docs as well.
In 
Exchange2000, you can rehome by top level folder and 
propogate:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q288150
 
And 
don't forget the chats on June 19:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/itcommunity/chats/default.asp
 
William
 

  
  -Original Message-From: Crosby, Tim 
  (Sarcom) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 
  05, 2002 4:12 PMTo: MS-Exchange Admin IssuesSubject: RE: 
  Exchange 2000 migration issues
  
  Thanks William, we 
  are planning to get rid of 5.5 as soon as we feel like the 2000 Server is 
  running OK.  What is the easiest 
  way to get the public folders moved over?  Right now, we are going into each 
  folder and setting it to replicate to E2k, but then we'll wait until it has 
  replicated and go back in and remove it from E55.  But don't you also then have to set 
  the "home server" for each folder to be the new E2k?  Isn't there a simpler way than going 
  into properties on each folder and doing this?  
   
  -Original 
  Message-From: William 
  Lefkovics [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 6:18 
  PMTo: MS-Exchange Admin 
  IssuesSubject: RE: Exchange 
  2000 migration issues
   
  
  The 
  requirement of patience can not be 
  underestimated.
  
   
  
  Use the 
  E2K tools to admin E2K and the 5.5 tools to admin 
  5.5.
  
   
  
  If it's 
  single server, single site, minimize co-existence.  Get the mailboxes and 
  public folders moved then free yourself of the ADC and 
  5.5.
  
   
  
-Original 
Message-From: Crosby, 
Tim (Sarcom) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 8:15 
AMTo: MS-Exchange Admin 
IssuesSubject: Exchange 
2000 migration issues
We are in the middle of 
migrating our single site, single server organization over to Exchange 
2000.  We have setup the ADC and run ForestPrep.  Everything seems 
cool so far.  All accounts seem to be syncing in AD.  We are at 
the point now where we are going to build the E2k box, join the 5.5 site and 
start moving mailboxes.  What I'd like to know is what to look out for 
once users are moved over.  What should we test specifically to make 
sure that the moved mailboxes work?  I have a few obvious ones in mind, 
check sending and receiving internet mail, check calendar availability, GAL, 
sending from E2k to E5.5, etc.  Is there a list of all the things you 
should test in order to make sure the E2k box is working properly?  
What problems have you all run into when moving to 
E2k?
Thanks, 

Tim 

List Charter and FAQ 
at:http://www.sunbelt-software.com/exchange_list_charter.htm
  List Charter and FAQ 
  at:http://www.sunbelt-software.com/exchange_list_charter.htmList 
  Charter and FAQ 
  at:http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm





RE: Exchange 2000 migration issues

2002-06-05 Thread Garland Mac Neill
Title: Message









Patience……

 

A room to cuss……

 

And an emergency sledgehammer…

 

-Original Message-
From: Crosby, Tim (Sarcom)
[mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, June 05, 2002
5:12 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2000
migration issues

 

Thanks William, we are
planning to get rid of 5.5 as soon as we feel like the 2000 Server is running
OK.  What is the easiest way to get the
public folders moved over?  Right now, we
are going into each folder and setting it to replicate to E2k, but then we'll
wait until it has replicated and go back in and remove it from E55.  But don't you also then have to set the
"home server" for each folder to be the new E2k?  Isn't there a simpler way than going into
properties on each folder and doing this? 


 

-Original Message-
From: William Lefkovics
[mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, June 05, 2002
6:18 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2000
migration issues

 



The
requirement of patience can not be underestimated.





 





Use the
E2K tools to admin E2K and the 5.5 tools to admin 5.5.





 





If it's
single server, single site, minimize co-existence.  Get the mailboxes and
public folders moved then free yourself of the ADC and 5.5.





 





-Original Message-
From: Crosby, Tim (Sarcom)
[mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, June 05, 2002 8:15
AM
To: MS-Exchange Admin Issues
Subject: Exchange 2000 migration
issues

We are in the middle of migrating our single site,
single server organization over to Exchange 2000.  We have setup the ADC
and run ForestPrep.  Everything seems cool so far.  All accounts seem
to be syncing in AD.  We are at the point now where we are going to build
the E2k box, join the 5.5 site and start moving mailboxes.  What I'd like
to know is what to look out for once users are moved over.  What should we
test specifically to make sure that the moved mailboxes work?  I have a
few obvious ones in mind, check sending and receiving internet mail, check
calendar availability, GAL, sending from E2k to E5.5, etc.  Is there a
list of all the things you should test in order to make sure the E2k box is
working properly?  What problems have you all run into when moving to E2k?

Thanks, 

Tim 

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm



List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm







RE: Exchange 2000 migration issues

2002-06-05 Thread Crosby, Tim (Sarcom)
Title: Message









Thanks William, we are planning to get rid
of 5.5 as soon as we feel like the 2000 Server is running OK.  What is the easiest way to get the
public folders moved over?  Right
now, we are going into each folder and setting it to replicate to E2k, but then
we'll wait until it has replicated and go back in and remove it from
E55.  But don't you also then
have to set the "home server" for each folder to be the new
E2k?  Isn't there a simpler
way than going into properties on each folder and doing this?  

 

-Original Message-
From: William Lefkovics
[mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, June 05, 2002
6:18 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2000
migration issues

 



The requirement of
patience can not be underestimated.





 





Use the E2K tools to
admin E2K and the 5.5 tools to admin 5.5.





 





If it's single server,
single site, minimize co-existence.  Get the mailboxes and public folders
moved then free yourself of the ADC and 5.5.





 





-Original Message-
From: Crosby, Tim (Sarcom)
[mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, June 05, 2002
8:15 AM
To: MS-Exchange Admin Issues
Subject: Exchange 2000 migration
issues

We are in the middle of migrating our single site,
single server organization over to Exchange 2000.  We have setup the ADC
and run ForestPrep.  Everything seems cool so far.  All accounts seem
to be syncing in AD.  We are at the point now where we are going to build
the E2k box, join the 5.5 site and start moving mailboxes.  What I'd like
to know is what to look out for once users are moved over.  What should we
test specifically to make sure that the moved mailboxes work?  I have a
few obvious ones in mind, check sending and receiving internet mail, check
calendar availability, GAL, sending from E2k to E5.5, etc.  Is there a
list of all the things you should test in order to make sure the E2k box is
working properly?  What problems have you all run into when moving to E2k?

Thanks, 

Tim 

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm



List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm







RE: Exchange 2000 migration issues

2002-06-05 Thread William Lefkovics
Title: Message



The 
requirement of patience can not be underestimated.
 
Use 
the E2K tools to admin E2K and the 5.5 tools to admin 5.5.
 
If 
it's single server, single site, minimize co-existence.  Get the mailboxes 
and public folders moved then free yourself of the ADC and 
5.5.
 

  
  -Original Message-From: Crosby, Tim 
  (Sarcom) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 
  05, 2002 8:15 AMTo: MS-Exchange Admin IssuesSubject: 
  Exchange 2000 migration issues
  We are in the middle of migrating our single site, 
  single server organization over to Exchange 2000.  We have setup the ADC 
  and run ForestPrep.  Everything seems cool so far.  All accounts 
  seem to be syncing in AD.  We are at the point now where we are going to 
  build the E2k box, join the 5.5 site and start moving mailboxes.  What 
  I'd like to know is what to look out for once users are moved over.  What 
  should we test specifically to make sure that the moved mailboxes work?  
  I have a few obvious ones in mind, check sending and receiving internet mail, 
  check calendar availability, GAL, sending from E2k to E5.5, etc.  Is 
  there a list of all the things you should test in order to make sure the E2k 
  box is working properly?  What problems have you all run into when moving 
  to E2k?
  Thanks, 
  Tim List Charter and FAQ 
  at:http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm





RE: Exchange 2000 migration issues

2002-06-05 Thread Precht, David
Title: Exchange 2000 migration issues



www.swinc.com/resource/e2kfaq_appxa.htm

  -Original Message-From: Crosby, Tim (Sarcom) 
  [mailto:[EMAIL PROTECTED]]Sent: Wednesday, June 05, 2002 
  11:15 To: MS-Exchange Admin IssuesSubject: Exchange 2000 
  migration issues
  We are in the middle of migrating our single site, 
  single server organization over to Exchange 2000.  We have setup the ADC 
  and run ForestPrep.  Everything seems cool so far.  All accounts 
  seem to be syncing in AD.  We are at the point now where we are going to 
  build the E2k box, join the 5.5 site and start moving mailboxes.  What 
  I'd like to know is what to look out for once users are moved over.  What 
  should we test specifically to make sure that the moved mailboxes work?  
  I have a few obvious ones in mind, check sending and receiving internet mail, 
  check calendar availability, GAL, sending from E2k to E5.5, etc.  Is 
  there a list of all the things you should test in order to make sure the E2k 
  box is working properly?  What problems have you all run into when moving 
  to E2k?
  Thanks, 
  Tim List Charter and FAQ 
  at:http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm