?
Solved

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

Posted on 2007-03-28
10
Medium Priority
?
278 Views
Last Modified: 2010-05-18
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
Comment
Question by:menreeq
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
  • 2
  • +1
10 Comments
 
LVL 35

Expert Comment

by:rakeshmiglani
ID: 18808805
since the number of users are just 25, export and import of pst files would be a good idea.
0
 

Author Comment

by:menreeq
ID: 18808954
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
 
LVL 35

Expert Comment

by:rakeshmiglani
ID: 18808997
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
U.S. Department of Agriculture and Acronis Access

With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.

 
LVL 104

Expert Comment

by:Sembee
ID: 18809553
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
 

Author Comment

by:menreeq
ID: 18809846
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
 
LVL 104

Expert Comment

by:Sembee
ID: 18809860
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
 

Author Comment

by:menreeq
ID: 18809965
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
 

Author Comment

by:menreeq
ID: 19826094
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
 
LVL 1

Accepted Solution

by:
Computer101 earned 0 total points
ID: 19855653
PAQed with points refunded (500)

Computer101
EE Admin
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
On September 18, Experts Exchange launched the first installment of the Help Bell, a new feature for Premium Members, Team Accounts, and Qualified Experts. The Help Bell will serve as an additional tool to help teams increase question visibility.
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
Suggested Courses

719 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question