Rebuild Exchange Server

I have a custom intel server box with the works from 6 years ago.  This server is the primary DC and Exchange 2000 box for a pretty large company.  Believe me, when I saw it, I was in shock.  I want to move both services to a new box.  What do you think is the best route? Here's what I was going to do.  

1. On current 'old' server perform a windows NT backup of the system state.
2. I have a brand new server with everything, the works...
3. Load Windows 2000 Server - their IT and Management Departments want to stay with Windows 2000 - there was no convincing them.
4. Run all service packs and sercurity updates.
5. On the new server load up DC services and add it to the domain.
6. Move over the roles to this server and run an authoritive update - they want to remain with Windows 2000 Server.
7. Install Exchange 2000 Server with /disasterrecovery switch????
8. Copy priv1.edb & .stm and pub1.edb and .stm to the new Exchange directory under mdbdata????

After all this is done, I have a second new server that will be added to the domain for further reduncy.

What do you guys think? Maybe there is another method? Another route? Longer but safer route? Shorter but more risker route?
Rob DuranSystems Network EngineerAsked:
Who is Participating?
 
redseatechnologiesCommented:
Hi BygRob,

There are a few ways to do this, but I would only really consider the following;

You could simply swing over to the new server -> http://www.amset.info/exchange/migration.asp
This would be similar to what you have listed above, with the following differences;

1 wouldn't be necessary
3 would be to REALLY try to get them onto windows 2003 and exchange 2003 (with software assurance if you can) if not, it is a shame, but by no means essential.
5 would be "join the server to the domain and then make it a DC"
6 would be simply "transfer all FSMO roles over to the new server"
7 and 8 would be from the above guide
9 would be (after the above is done) uninstall the old exchange server
10 would be dcpromo the old server out of the network

Or you could do my preferred option, a total server restore.

Backup the existing server, shut it down, and then test out the disaster recovery solution.  If the old server totally died, could you rebuild the network?  Rebuild the new server with the same name and then restore the system state and exchange data.

Upsides to that method are you get to test the Disaster Recovery solution, downside is that you will have downtime (of about a day, which should be on a weekend)

The first method, a swing migration, will have very little downtime for users, they will only need to be out of their mailboxes for it to be moved (which can be a very short period of time depending on the size of the mailbox?)

Hope that helps,

-red
0
 
Rob DuranSystems Network EngineerAuthor Commented:
I am doing all this on Saturday.  I can bring them down.  
0
 
Rob DuranSystems Network EngineerAuthor Commented:
When you say "transfer all FSMO roles" that is simply just going and changing the operations master in the Active Directory Users and Computers?
0
 
redseatechnologiesCommented:
That will get 3 of them, there are 2 more;

http://www.petri.co.il/transferring_fsmo_roles.htm

-red
0
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.