My network consists of an NT 4.0 PDC and a W2K member server. I would like to replace the PDC with a new W2K server running AD, however I still need to keep the old PDC on the network so once the new one is up and running I can transfer mailboxes and otehr information across into AD. The problem lies in that because the current member server is W2K and not running AD it cannot be promoted to a PDC or the PDC demoted to a member server as you need 1 PDC in a domain. Does anyone know what will happen if I build a brand new W2K server with AD and plug it into the network with the current PDC active (bearing in mind I have taken into concideration duplication DHCP, DNS, WINS, ip addresses etc etc). I am hoping that it will force an election and all my problems will be solved but I don't think it is going to be that easy. Your help is appreciated.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Replacing a PDC
- Thread starter treslayew
- Start date
Reefslayer
IS-IT--Management
sounds to me like you'd just end up with an active directory sitting next to an NT domain on your physical LAN.
This in itself might present you with a path forward.
I would consider building a second machine into your NT 4 domain as a BDC. You will then be protecting your current live environment by duplicating the SAM.
You would then be in a position to upgrade your existing pdc after taking the new bdc offline.
This of course assumes you're happy with the NT4 domain structure etc.
As an alternative you may like to consider using the ADMT (AD Migration tool)to copy user accounts AND sids into a newly defined AD which you could do in the scenario you decribe (If i'm reading it right!)This in turn would depend on migrating groups as well as accounts. You could then have a new AD with a new domain name etc , but retaining the old accounts. You would thus avoid permissions reworking..
Hope this is of some help..
This in itself might present you with a path forward.
I would consider building a second machine into your NT 4 domain as a BDC. You will then be protecting your current live environment by duplicating the SAM.
You would then be in a position to upgrade your existing pdc after taking the new bdc offline.
This of course assumes you're happy with the NT4 domain structure etc.
As an alternative you may like to consider using the ADMT (AD Migration tool)to copy user accounts AND sids into a newly defined AD which you could do in the scenario you decribe (If i'm reading it right!)This in turn would depend on migrating groups as well as accounts. You could then have a new AD with a new domain name etc , but retaining the old accounts. You would thus avoid permissions reworking..
Hope this is of some help..
In order to get the SAM database replicated correctly, you'll need to install NT server as a BDC on the member server, then promote it to PCD, then upgrade it to 2000. Read the help on your member server under "getting started with windows 2000" about migrating to 2000. You will also find additional resources and information in the tools that come on the 2000 disk designed to assist migration.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question