• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 272
  • Last Modified:

2000 ad to 2003 ad migration

Environment:  2000 AD server, Exchange 2003, 55 workstations
I upgraded the Exchange 5.5 to 2003 last week.  This week i will remove the Exchange 5.5 and remove that server as a DC....

I need to swing over the 2000 ad to a temporary server than add four hard drives plus sata card  to the existing 2000 AD.  The existing SCSI card and hard rives will be moved to assigned a d drive so the data is still recoverable.  I will install the new 2003 OS on the sata drives and than DCPromo that server from the temp.  I will seize the roles on the temp server than clean them up (removing old 2000 server name) making that one to have the 5FSMO and GC.  Rebuild the old 2000 server with 2003 and assign it the same name so workstations will not know the difference.  This is a slight modification from the Jeff Middleton Swing migration, if anyone is familiar with that method.

My question is can i just transfer(instead of seize) the roles to the temp server, do some cleanup and than get the 5FSMO and GC back to the old server once installed with 2003 Server?  I am use to doing this kind of migration from SBS 2000 to SBS 2003. The whole thing is keeping the same server name on the newly restructured server..

How would one do this migration, remember I do have Exchange 2003 server on a separate box????

Third item  is to install Exchange 2007 on separate box on separate night...  i will post in different group

  • 4
1 Solution
If the main question is how to move the roles back and forth, that is straight forward.  However, I'm not sure I would do everything in that order.  I would likely do the following:

1. Install the ad updates on the 2000 server to support 2003 servers.
2. Install the 2003 server and promote to a DC.
3. Make the new server a Global Catalog server.
4. Install and configure the new Exchange 2007 server into the existing exchange organization and migrate the mailboxes.  Leave the old server running exchange 2003 till you are positive all users have logged in on the new server and had their outlook updated with the new server pointer.
5. Repoint your forwarders on your firewall for smtp and pop if necessary.
6. Uninstall exchange from the old mail server.
7. DCPromo down the server to not be a domain controller.  This will automatically move the roles to the temp server.
8.  Document your shares and share permissions on the old server and disjoin your old server from the domain.
9.  Disconnect your scsi drives for safety sake and install your new sata drives in the server.
10.  Install windows, apply all updates, reconnect the scsi drives, recreate the shares and DCPromo the box.
11.  Either DCPromo down the temp server to move the roles back or manually migrate the roles bac by using NTDSutil.  If you are not familier with NTDSutil, there is a good tutorial at:
petvesAuthor Commented:
Sounds good..... I will try tonight
petvesAuthor Commented:
I am going to just upgrade AD for tonight.  Doing Ex2007 another evening...
petvesAuthor Commented:
I will be bring the newly installed 2003 server up again with the same name as when it was 2000 server.  Would transferring the roles to the temp server be fine?????  Once new box is up I would transfer them back by demoting the temp server?????
petvesAuthor Commented:
Does the Exchange 2003 Server have to be on SP2 before I do the install of Exchange 2007.  I wanted to install 2007 on the separate server and get everything up and running than move over mailboxes at 5pm...
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.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

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