the bdc would become the first DC in the AD 2k domain.. no big deal really.. once in an AD2k environment there is no pdc and bdc.. just a bunch of domain controllers that replicate stuff.. that's all.. what is your bdc now will become the operations manager for the domain, which might raise some issues with your nt4 server, but I can't be sure.. all the Operations Master options can be changed once the upgrade is complete..which you'll probably want to do because your nt4 server is your primary one.. all of that can be changed in the Acitve Directory (users & comp's, Domain's and trust, Sites and Services mmc's)
Snooter "tis better to remain silent and be thought of as a fool..
then open your mouth and remove all doubt" Mark Twain
if you only have one BDC, synchronize the domain, unplug the DC from the network and upgrade your PDC to win2k. the new AD DC will handle all the requests the NT PCD did. It is also the Global Catalog Master, this means that it is really a PDC (if you take out the GCM from an AD domain, you will have the same problems you would have with no PDC in NT)
If your upgrade goes bad, unplug the win2k from the network, and plug the bdc in and promote it to PDC. If the upgrade is successfull, upgrade the BDC to an AD controller and you now have an AD domain.
but dont just follow these instructions, buy the MS windows 2k resource kit. It has very detailed info on how to do this.
You could also get the info from MS knowledge base.
Have a nice day Doomhamur
Network Engineer
"Certifications? we dont need no stinking certifiaction."
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.