7 replies
by glennw
by joseph moore
You don't need 2 domains for this.
Yes, you CAN do it that way. You could set up the Win2K box (separate from your NT4 PDC) with Active Directory, running its own separate Domain (again, different from your NT4 Domain). You could then set up a 2-way Trust between the 2 Domains.
Then you can run ADMT (Active Directory Migration Tool) and migrate the NT4 users to Win2K AD. Then bring down the NT4 PDC, reformat it, and install Win2K and make it a member server of the AD Domain.
You could do it that way. Nothing wrong with that.
But, you could upgrade your NT4 PDC to Win2K. That will, during the upgrade, install/configure AD, and it will upgrade the NT4 users to users in AD. All this would run on the current NT4 PDC, which would, when done, be Win2K AD (and be the Global Catalogue server, as well as PDC emulator, and every other FMSO role).
You could then build the 2nd server, install Win2K on it, add it as a member server to your one single existing AD domain. THEN you could run DCPROMO on this new machine, and make it a 2nd Domain Controller of your single AD domain. (NOTE: in Win2K and AD, all Domain Controllers are basically equals; no Primary or Backups now.)
THEN you could TRANSFER all FMSO roles FROM the old NT4 (now Win2K) box TO the new Win2K box. Then run DCPROMO on the old box, and remove it as a domain controller, leaving it a member server.
So, 2 options there.
Have fun!
by joseph moore
BTW, guess I should have put my beer down!
It is not "FMSO" roles, it is FSMO -- Flexible Single Master Operation -- roles!
Oops!
Here's a Technet article talking about the different roles:
http://support.microsoft.com/?kbid=197132
by joseph moore
You can download the Windows 2000 Active Directory Migration Tool from this Microsoft page:
It also talks about the tool, how it works, etc.
by glennw
Is the Mirgation tool an extra tool option I must install.
Because I have'nt found it yet.
thanks for your help.
by chris..
ADMT 2.0 is indeed the tool if you are doing a parallel migration. If you are doing a in-place upgrade that gets more complicated as indicated in the above post.
1. Build the server as a NT4.0 BDC, pull the PDC off the network, promote BDC to PDC, conduct upgrade, rebuild old PDC.
by jlbpotter
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending