Upgrade/Move 5.5. to 2003 Exchange

Hello - I have two AD controllers, Exchange 5.5 is on the old one (Win2K)  I would like to relocate Exchange to our newer server and keep the old box as a secondary domain controller.  Not sure how to proceed on this one - have to do the upgrade tonight..   I typically use EXMERGE, but not sure how I would populate the AD object with the Exchange stuff and all that.  Does it move over easy?  Or should I upgrade the 5.5 to 2003 then work on moving it?  Please help
Who is Participating?
Computer101Connect With a Mentor Commented:
PAQed with points refunded (500)

EE Admin
tmostowyAuthor Commented:
We are thinking this way to go..
(1) move 5.5. to the faster box AD controller (the current box is P2, 256RAM)
(2) Change all outlook clients to point to new box
(3) - After all is well, do an in-place upgrade...

So the new question is how easy is it to move a 5.5 server?  May have to use EXMERGE for sure now
are you planning on putting exhange on a DC as well?
tmostowyAuthor Commented:
yes.  Both servers are DC, one is new (Win 2003) the other is old (Win 2000 w/ Exchange 5.5).  The old box will simply do DC tasks (once I move Exchange to the other box).
tmostowyAuthor Commented:
Please close this case.  I never got an answer from experts-exchange.  Below, I documented how I hooked this issue in case anybody runs across this...

** Upgrade from 5.5 to 2003 Exchange while relocating to a new server **

- in preparation for disaster, I backed up all mailboxes to a PST using EXMERGE
- second, I logged onto a user WS and exports all public folders into PST's as well.
- I am over cautious when it comes to backing up Exchange as you can see.  By creating a PST, This avoids me ever having to use the tools or having to call MS.
- Load the AD Connector ont he 5.5 server.  (from the EX 2003 CD - under tools, run setup)
- run AD Connector MMC from the 5.5. server (start, programs, exchange, etc)
- use the Wizard for NO DOWN TIME
- create 2 connectors (or connections) - 1 for user mailboxes, the other for public folders, start the copy.
- when the copy is complete, you need to change the Outlook at all users.  You could hook this through a reg command in the logon script, but I found that Outlook is weak and somtimes need a new profile.  So I went to all users, added a new profile to the new server for Exchange and made it the default.  Good to go.
- Here is the tricky part....   SMTP goes through your old 5.5 server until you kill the connections in the AD connector.
- To make it 100% reliant off itself and kill 5.5 services, follow the online documentation at MS for the final steps.  
- This worked like a charm and we migrated over 20GB in under 8 hours - whole project soup to nuts..
- Take care....

Todd Mostowy
<contact details removed, -red, EE Page Editor>
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.