[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1706
  • Last Modified:

Migrating mailboxes from Exchange 5.5 to Exchange 2003

I have seen a slew of posts about this.  My question is as follows.  

There are two ways two migrate mailboxes ... interorganizational (setup Exchange 2003 as a new organization than that of Exchange 5.5) and using the ADC with Exchange 2003 in the same organization as Exchange 5.5.  My site had no public folders.  

Someone correct me if I'm wrong.  If I install with the ADC, then I can migrate users and nothing should happen connection wise during this process?  Then, once I have migrated users, I can remove the Exchange 5.5 box.

Now, if I setup Exchange in a new organization and migrate users using Exchange Migration tool (remember, no public folders) should I not also be able to migrate users, and while the Exchange 5.5 box is still in place, nothing happens to their connection.  

My ultimate goal is little to no downtime of users mailboxes if possible.  MS recommends the ADC, but I was wondering if anyone actually had war stories related to this problem.  

Thanks  
0
neowolf219
Asked:
neowolf219
  • 2
  • 2
  • 2
2 Solutions
 
David WilhoitSenior Consultant, ExchangeCommented:
Well, it sounds the same, but the 2 are nowhere close to being the same. Whenever possible, use the ADC to join the 2003 server to your 5.5 org, inter-org is only for special situations. Not having public folders, I'd say your migration should be a breeze. But you do actually have some PFs, the system folders. Don't forget about them, they are relatively important to your calendaring and scheduling process.

If done properly, your users should have zero interruption of mailflow during the migration process.

D
0
 
visioneerCommented:
I agree with Kidego.  The easiest thing to do here is:

1) Install a new Exchange 2003 server into your 5.5 site.

2) Move the mailboxes and public folders from the 5.5 server to the 2003 server (there are wizards that do this).

3) Remove the 5.5 server from the site. http://support.microsoft.com/default.aspx?scid=kb;en-us;822450&Product=exch2003

Complete process outlined here: http://support.microsoft.com/default.aspx?scid=kb;en-us;316886
0
 
neowolf219Author Commented:
I guess I should have added I am doing this on a cluster ... does this make a difference.  
0
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

 
neowolf219Author Commented:
Actually, I just read in a MS doc that SRS is not support in a clustered environment.  So I will have to create a new organization and then use the migration wizard to move the mailboxes.  Active Directory is already in place, so theoritally this shouldn't be an issue.  
0
 
David WilhoitSenior Consultant, ExchangeCommented:
No, you can create a stand-alone server for the first server in your environment, then create the cluster. When the migration is over, you can remove the front end server. Don't create the new org, you'll have to exmerge then, and that's just no fun :)

D
0
 
visioneerCommented:
Exactly what Kidego said.  It's way easier to just install the new server and move the mailboxes, as I previously outlined, than to use exmerge.  Just create the server, join it to the site (cluster is irrelevant), move the mailboxes, and remove the old server.  Then like Kidego says, create your cluster with the new server.
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 2
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now