Discussion Locked

NT/Exchange 5.5 to Win2k3/Exchange 2k3

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am currently running a small network of 2 servers:

PDC - NT 4 file/print server.
BDC - NT 4 with Exchange 5.5.

I want to migrate both servers to either Windows 2000 or Windows 2003 Server and migrate Exchange 5.5 mailboxes and custom public folders to either Exchange 2000 or Exchange 2003.

We will hopefully be acquiring a third server, identical to the first two, to help ease the transition.

1. Do you recommend going from NT 4 and Exchange 5.5 straight to 2003, to 2000 and then to 2003, or just to 2000?

2. Can you provide instructions or point me to a comprehensive guide (a book, a web site, a PDF, etc.) on performing this migration? I have yet to see a resource that specifically discusses moving from Exchange 5.5 on NT 4 to Exchange 2003 on Window 2003 Server.

11 replies

by bfilmfan

Migrate the NT4 BDC to Windows 2003.
Then install an Exchange 2003 server running on Windows 2003 into that forest.
Quest Microsoft Management Software (formerly Aelita) is probably the package I've used most with the least issues to accomplish this:
White papers here:
http://wm.quest.com/products/Exchange/

by instrumentality

Let me add one point to the above: down time is a DEFINITE issue.

Again, the BDC is running Exchange 5.5. Wouldn't it be a bit dangerous to take my one live Exchange server and directly upgrade the operating system? Correct me if I'm wrong, but that means no one gets e-mail until I 1) finish upgrading the server to Windows 2003 and 2) figure out how to get Exchange 5.5 to talk to AD? Also, isn't the general rule of thumb with Microsoft that you should do a fresh install whenever possible rather than upgrading an existing OS/application?

And you're saying to install Exchange 2003 on the third server after this?

And if my BDC gets upgraded to 2003, that means I've got an NT 4 PDC controlling a 2003 BDC. This isn't problematic?

by instrumentality

Thanks for that link. Looks pretty useful, but...

d. In the Move Mailbox pane, verify that Current Mailbox Store is the Exchange 5.5 computer and that the SERVER name is the name of the server that is running Microsoft Windows 2000 Server, and then select the storage group and the mailbox store that you want to move the user to.

I'm running Exchange 5.5 on NT 4, not Windows 2000 Server. Does this open up another can of worms?

Also, the swing method seems to be specifically referring to the Exchange side of things. It could be a pretty solid Phase 2, but I'm guessing that prior to this, I need to set up a brand new Windows 2003 server as my new PDC and somehow move my users and files over from my NT 4 file server (preferably with permissions preserved if possible).

If you can give me some insight on this aspect and also explain the Exchange 5.5/Windows 2000 Server issue, I think I'll be in pretty good shape.

by bfilmfan

The first issue to tackle is Exchange running on that domain controller. In the past, I've advised clients against that as it prevents the DC from being upgraded.

Since downtime is an issue, I see your choices as:

Install a new member server running Exchange and move the mail boxes to it. Start an upgrade of the domain controllers to Windows 2003. Leave the forest in Windows 2003 Interim. Set up the Active Directory Connector. Move the Exchange 5.5 server to the AD forest and then do an upgrade.

-OR-

Set up an AD forest with Exchange 2003 on new servers. Clone the user accounts to the AD forest with a migration tool. Migrate the mailboxes from the NT domain to the new AD forest.

Choice 2, while more expensive, does give you a fall back position in the event that you have issues with the AD account migration.

On the issue of downtime, there will be some loss of connectivity when you are moving mailboxes if you don't use a tool like Quest migration manager. This will allow synchronization between the old mail box to the new one, until such time as you have fully cut over Exchange.

by instrumentality

In scenario 2, are you talking about having *2* additional servers and setting one up with Windows 2003 Server as the DC and one with Exchange 2003 (not a DC)? I think we can get our hands on one new server but 2 is pretty much out of the question.

It's been suggested to me that I consider going with Small Business Server 2003, but that wasn't part of my original question so I'm going to post it separately in this forum.

by curlergirl

As you've already seen, there are lots of different answers to this questions. The way I'd recommend doing it is:

1. Get your third server and create a completely new Win2K3 AD domain. Set up a trust relationship between this domain and the NT domain. This will allow you to migrate users from the old NT domain to the new Win2K3 domain using the Active Directory Migration tool. This will allow your users to log on to both domains transparently, provided you use the same passwords and take care of any IP routing issues. In a small network like yours, what I would recommend is setting up the new 2K3 server as the DHCP server for the entire network so that all workstations get their IP settings from that server.

2. Once you've got the new domain set up, and users migrated, you can begin moving your old servers to the new domain. You can move your BDC first by upgrading it to Win2K3 and joining it to the new domain. Remember that your users will still be able to connect to Exchange 5.5 as long as your ADC is set up and configured to connect to Exchange 5.5. There are special procedures for doing this - I would recommend searching the Microsoft Technet website for how-to articles.

3. Now you are ready to upgrade Exchange 5.5 to Exchange 2003 in place on the same server. Again, follow the MS tech articles for the correct procedures.

Migrating workstations is easy - just unjoin the old domain and join the new one.

This is all doable without any expensive migration tools given you have a small network with a single domain and forest.

Hope this helps!

by instrumentality

OK. New server with Windows 2003 on a new domain. Got that. Then I will have a Windows 2003 Server box on its own domain, an NT 4 PDC on a separate domain, and an Exchange 5.5 box on the same domain as the PDC.

From there, you're saying I should *upgrade* the NT 4 PDC to 2003 and join it to the domain? You recommend upgrading over a fresh install? I'm not criticizing this idea; I just want to be clear.

What I've sort of pieced together from the advice I've been given here and elsewhere is that I should set up the new 2003 server on its own domain and establishing a trust between the old and new domains like you suggest.

However, what I envisioned from there was moving my directory structure off my NT4 PDC and over to the 2003 box, reformatting the NT 4 PDC, loading a fresh installation of Windows 2003 on it, and joining it to the other 2003 server's domain. From there I would load Exchange 2003 on the second Windows 2003 server and then migrate users and public folders over from the Exchange 5.5 server to the Exchange 2003 server.

Am I missing something here? Am I going to be hosing connectivity to my Exchange 5.5 box if I wipe out my NT 4 PDC or something?

by curlergirl

Answering your comments re: upgrading v. reinstall: what I was suggesting was upgrading your BDC, not your PDC. My reasoning was that it is easier to upgrade an Exchange server than to wipe it out and completely reinstall. However, you've given me a better thought - if you do what you suggested, your NT4 BDC with Exchange 5.5 becomes the NT4 PDC of your old domain. You take your NT4 PDC, disconnect it from the NT4 domain, and the BDC will get promoted to PDC. Then, you can wipe the PDC as you suggested, install Win2K3 and Exchange 2003 fresh, joining the new domain and the same Exchange site as the Exchange 5.5 server (two Exchange servers in different domains CAN be members of the same site). The Active Directory Connector will allow you to replicate between the old 5.5 and the new 2003 Exchange databases. This will actually be better, since you will have almost NO downtime on Exchange. You can get everything installed and configured, make sure it's communicating properly with the old Exchange 5.5 server, replicate your public folders, and then the only down time you have is when you are actually moving the mailboxes over. Again, I suggest you check Microsoft for tech articles - there were some very good ones for Win2K and Exchange 2K that I used when I did this going from NT4 to Win2K. There are things you need to watch out for, such as how to name your new domain and your new DNS zone, etc., that will affect what happens with Exchange as well.

Hope this helps!

by instrumentality

Thanks a lot for the detail...that pretty much spells everything out, including the sequence of promotion and joining and migration, which was the main variable I was still hazy on.

Now the main decision for me is whether to take this route or use Small Business Server. I will pick that up on my other discussion and close this one out.

This discussion is closed to new replies.