Discussion Locked

Migration to Exchange 2000 Across Domain

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

We currently have an NT 4.0 Domain that has Exchange 5.5 running in it. We have created a new Windows 2000 Domain that we will eventually move to. I have done quite a bit of research with regard to migration but have found very little information on the best way to migrate 5.5 users mailboxes to the new Exchange 2000 box across domains. I would prefer that for now they remain in the NT 4.0 Domain and get access to the new mail server in the 2000 domain.

I have been experimenting with the ADC and Migration Wizard and have the basics down. Is there a way that both mail servers could be running at the same time in different domains synchonized so that I can move users gradually? I don't need the small details. An overview of the best process that allows gradual migration will serve me the best.

Dan Cassat

5 replies

by curlergirl

You can do this seamlessly - the Exchange users do not have to be in the same domain, only in the same Exchange site, as long as there is a working trust relationship between the two domains. I have done this in the past and it worked perfectly. First you have to set up your trust relationship, which you also have to set up to migrate users, so you might already have done this. You have to migrate your users first in order for this to work, but you can maintain their user accounts in both domains. Then, you set up your new Exchange 2000 server in the new domain but join the same Exchange site, so both servers are in the same site, regardless of domain membership. Then you move the mailboxes, public folders, etc., using the Active Directory Connector and other Exchange migration tools. When you're done moving everything, you can decommission the Exchange 5.5 server and remove it from the site. The users in the NT4 domain will still be able to connect to the new server, but this gives you an opportunity to migrate slowly and test the connections to be sure everything is working properly before you remove the old server. There are a couple of tech articles I've used that give good info on this. From the Technet web site (www.microsoft.com/technet), look up the article numbers: 316886 and 324318. Hope this helps!

by dcassat

This answer is exactly what I'm looking for. I haven't actually done the work yet but have a good understanding about the steps you outlined. Thank you for taking the time to provide such a concise answer!

by public

Be careful! I know you probably want to start a new domain name when you go to win2k. However remember, if you win2k pro or winnt 4.0 clients, when you log into the new domain name (with the same user names etc) Win2k pro will create (not sure about 4.0) NEW PROFILES. That means setting people up all over again all over the network. Because of this, my company stayed with the same domain name instead of going through that hell.

Just a heads up.

-me

This discussion is closed to new replies.