8 replies
by henrywi
by djf
by acattr
kill server1 pdc
make server2 bdc - new PDC
Install windows 2000 on server1
upgrade server2 to windows 2000
run dcpromo on server1 to make it a DC. also follow http://support.microsoft.com/default.aspx?scid=kb;en-us;Q255690 to move all FSMO roles to server1
run dcpromo on server2 to make it a member server while connected to network.
kill server2 and reinstall as BDC NT40 or clean windows 2000 DC.
by acattr
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q255690
remove spaces from link.
by djf
by timwalsh
Rules for Win2K and Active Direectory (AD):
1. An NT4 PDC CANNOT exist in a Win2K domain.
2. Win2K Domain Controllers (DCs) CANNOT exist in an NT4 domain.
3. To migrate an NT4 domain (to include users and other security related settigs), youMUST install Win2K (and AD) on the NT4 PDC.
4. NT4 BDCs can exist in a Win2K domain.
There are no work-arounds to these rules.
You could do the following:
1. Promote one of your BDCs to PDC (after forcing synchronization).
2. Remove youroriginal PDC from the network.
3. Install Win2K (and AD) on your new PDC (which will migrate all user information and security settings).
4. Wipe the drive and install Win2K on your original PDC.
5. Connect the Win2K server to the network, connect it to the new domain, and run dcpromo (wich will install AD and create another Win2K DC).
6. Transfer all AD FSMO roles to this DC if you want it to be your main DC (the PDC/BDC relationship doesn't exist in Win2K).
You will still lose all file permissions that existed on your original PDC. File permission relating to each computer reside on that computer. Ther is no cetralized database of file permissions for the domain.
by djf
by djf
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending