[Webinar] Streamline your web hosting managementRegister Today

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

Exchange 5.5 to Exchange 2007 options - Swing migration or start fresh?

I have to migrate a 25 user site from Exchange 5.5 to Exchange 2007.  I understant that I have to first go to Exchange 2003 and then to 2007 - that's clear.  However I'm wondering whether it wouldn't be less time consuming to just export all mailboxes to PST, wipe out the Exchange 5.5 server, start fresh with an Exchange 2007 server (on a new box of course) and import all PSTs into the new server.  Would this be less time consuming than doing it doulbe swing migration?  BTW - I can do this over a weekend so downtime is not a concern.
thanks
0
menreeq
Asked:
menreeq
  • 4
  • 2
  • 2
  • +1
1 Solution
 
rakeshmiglaniCommented:
since the number of users are just 25, export and import of pst files would be a good idea.
0
 
menreeqAuthor Commented:
If I remember correctly, Exchange 5.5 doesn't talk to AD unless the AD connector is setup and running.  If that's the case, what do I need to do to remove al remnants of Exchange 5.5 - just uninstall it and that's it?
0
 
rakeshmiglaniCommented:
that is correct. exchange 5.5 has its own directory called dir.edb
if ADC is not installed and configured at this time then just export the users via exmerge and uninstall exchange.
0
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.

 
SembeeCommented:
You can't swing direct.
You would have to upgrade to Exchange 2003 first, then only upgrade to Exchange 2007 once Exchange 5.5 has been removed.

For 25 users I would probably build a new Forest and domain and exmerge everything across. It will let you sort out the rubbish that most domains collect.

Simon.
0
 
menreeqAuthor Commented:
Sembee, I know that I can't swing direct.  I would prefer not to have to build a new Forest and domain if possible.  The ADC is not installed on the Exchange 5.5 server so there shouldn't be anything in the forest regarding the current Exchange 5.5 installation.  Do you see a problem w/ me just exmerging all the mailboxes and importing them into a new Exchange 2007 installation?
0
 
SembeeCommented:
The installation will see the Exchange 5.5 server unless you remove it.
You must have an ADC somewhere, otherwise Exchange 5.5 cannot talk to the domain. It doesn't have to be on the Exchange server, it could be on a domain controller.

Simon.
0
 
menreeqAuthor Commented:
My understanding is that you only need ADC when you migrate from Exchange 5.5 to Exchange 2000 or 2003.  See excerpt from http://www.microsoft.com/technet/archive/exchangeserver55/activedirectoryadmin.mspx?mfr=true below:
When you migrate, you need some way to move your directory objects from the Exchange Server 5.5 directory into Active Directory. Active Directory Connector (ADC) is the solution. The ADC is what will synchronize the Exchange Server 5.5 directory with Active Directory.

I've checked the Exchange server & the domain controller and there is no ADC installed.  There are also no Exchange attributes on the user accounts.  
0
 
menreeqAuthor Commented:
I was able to upgrade directly from Exchange 5.5 to Exchange 2007 on this project because ADC was not configured on the domain.  I used exmerge to extract all the mailboxes from the Exchange 5.5 server and then imported them to the Exchange 2007 server.  Worked very well.  Just to clarify - this was possible in this circumstance because Active Directory Connector was never setup on this site, so Active Directory did not know that there is an Exchange 5.5 Server on the network.

This should be the answer to my original questions.

0
 
Computer101Commented:
PAQed with points refunded (500)

Computer101
EE Admin
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.

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