Exchange 5.5 to 2003 migration

[mlnrao]

Hi,
We have two locations each with Exchange 5.5 on Windows 2000 and Win NT PDC and BDC.
Now we are planning to move to win 2003/Exch 2003.

What is the best way to start with ?

Shall i install a new Windows 2003 AD member server in the organistation, and install Exchange 2003 on that and join exchange 5.5 organisation and then move the all the mail box to Windows 2003

or

Upgrade one of the Win NT PDC to Windows 2000/2003 and then install an Exchange 2003?

I have gone throgh few documentation on this, but getting confused for my kind of scenario.

Thanks

Lakshmi Narayana

 

[zephyran]

I haven't yet completed our migration to Exchange 2003, but we started out with a system similar to yours.

First, you MUST be running an Active Directory domain in order to use Exchange. You could either upgrade your domain by upgrading the PDC to Windows 2000 or 2003, or you could create a new, fresh domain on a clean 2003 box and migrate the user accounts and other resources to the new domain. The clean migration is usually the recommended one if you have lots of time, but I personally did the domain upgrade without much trouble.

It's recommended that your domain also be at least Windows 2000 Native Mode, so you can gain access to Universal Groups. Exchange makes pretty heavy use of them. If you start with a clean Win2003 domain, then you can easily switch it to this functional level. Otherwise, if you're upgrading, make sure all your NT4 domain controllers are either upgraded or removed from the domain, and then switch the domain to Native Mode.

Once that's done, run the Exchange Deployment Tools (available on the Exchange 2003 disc or download from Microsoft.com). They have all the steps, in order, that you should need to follow to get your system migrated to Exchange 2003.

You probably know that you cannot do an in-place upgrade from 5.5 to 2003, so you're right on track with the migration plan. But there's a lot of work you need to do before you ever install the first Exch2003 server, and it must all be done carefully to avoid messing up your system.

I would make sure to check out FAQ#858-3483 over in the Exchange 2000 forum. It's a collection of a lot of good info on the legwork that was needed to migrade from Exchange 5.5 to 2000. Although Exch2003 automates a good portion of this stuff for you, doing all that work beforehand will GREATLY reduce the number of problems you run into.

I'll be happy to help with any questions you may have on the domain upgrade, and though I haven't finished the Exchange migration myself, I can try to point you in the right direction for answers.

 

[Marcs41]

posted here before:

http://www.msexchange.org/tutorials/Migrating_Exchange_5_5_to_2003.html

Marc
[sub]If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all. Please specify details.
Free Tip: The F1 Key does NOT destroy your PC![/sub]
How Do I Get Great Answers To my Tek-Tips Questions? See faq222-2244

 

[TruBlu01]

We upgraded our original PDC to 2003 and then a few DC afterwords. Our main site then did the Exchange org and install with remote offices to follow, but yes, you join the 2k3 exchange to the 5.5 org.

 

[mlnrao]

thanks wildmagpie8,

my question is, if i upgrade my NT domain to Windows 2003 native mode and can exchange 5.5 can be running as before without any changes ?

do i need to change any exchnage directory stuff there so that that should point to new AD

Otherwise can i bring in an Windows 2003 and make it part of NT domain and continue with NT 4.0 and exch 5.5

thanks
Lakshmi Narayana

 

[zephyran]

As long as the Exchange 5.5 server is running either Windows NT4 or 2000 and is a member server in the domain, you should be fine. If you're going to move Exchange to a new server, you should probably go ahead and make it a Windows 2003 member server so you can take advantage of all of Exchange 2003's new features. One thing - make sure you run the Exchange setup from the Deployment Tools kit, after you have the domain in a stable state. Don't immediately install ADC after upgrading the domain (as some have) or else you could run into major problems.

If you have a test network available (or can wire a couple PCs together to simulate a domain controller and an Exchange server) I would test it out first. I, however, had no trouble with my scenario upgrade scenario, as far as I've gone (getting ready to apply the ADC Connection Agreements).

 

[mlnrao]

then after upgrading Domain to Windows 2003, there should be no problems for Exchange 5.5 right ?
Exchange 5.5 SP4 is running on Win 2000 SP4, as u said once local domain gets stable then i can think of Exch 2003.

One more problem here is i need to install Exch 2003 on same server as currently runnning exch 5.5,
i think i will have to configure one swing server in during installtion., and move mail box and then re-install and re-move mail-boxes.

is there any proper doc on this ?

Lakshmi Narayana

 

[zephyran]

Well, there's a multitude of documentation on switching between 5.5 servers. Search Microsoft's site, Tek-Tips, and other tech sites like Techrepublic.com and msexchange.org for documents related to what you want to do; all of them are very good resources. The basic steps you're talking about are well-documented:

1. Migrate an Exchange 5.5 server onto new hardware running Exchange 5.5.
2. Migrate an existing Exchange 5.5 organization to Exchange 2003.
3. Remove the Exchange 5.5 servers and switch the Exchange 2003 organization to native mode.

My recommendation, if you're going to use this method:

1. Move to the intermediary Exchange 5.5 server (running Windows 2000 Server) using the Move-Mailbox method, and transfer all public folders and connectors.
2. Confirm that it's working by shutting down the Exchange services on the original Exchange box.
3. Wipe the original Exchange box clean and reinstall with Windows Server 2003.
4. Run through the Exchange Deployment tools to install the first Exchange 2003 server in a 5.5 organization.
5. Migrate all boxes, public folders, and connectors to the new Exchange server.
6. Shut down the intermediary server and make sure everything works.

Of course, make sure you have a full and verified backup of every involved server before performing each of the above steps. Depending on the size of your Exchange store, this could possibly be done in one (albeit long) night. If you give the rebuild Exchange server a different name, however, you'll have to manually redirect all clients' Outlook settings to the new server name.