Discussion Locked

Move PDC to BDC of other domain

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I need a BDC in a domain, but can't install NT as a BDC on the server because the NICs I have available don't work until SP4 is installed, and to create a BDC the NIC has to work during initial installation. Can I install NT as a PDC of a new domain, then after getting the NIC to work change the domain to the existing one?

9 replies

by nettek

You cannot install an NT Primary Domain Controller in its own domain, add it to a different domain that already has a PDC, and then rename the domain.

I have never heard of a NIC card not working until service pack 4 is installed. What kind of NIC card is it?

Would it not be easier to buy a cheapo $30 nic to use to connect to the domain? Then after you install the latest SP, you can then install the NIC you want.

by johnnyextreme

The NICs that don't work so far are DFE530TX from DLink, and an NE2000 Compatible. I've installed NT Server as a member using the DFE530TX but the card wasn't recognized and didn't work until SP4 was installed.

by koan

I believe you can replacing a nic card will save you time and hassel of going about joining an existing domain later on. In terms of the NIC not working until sp4 is installed, can you just get the newest driver for the nic and see if that works?

by koan

I believe by replacing a nic card will save you time and hassel of going about joining an existing domain later on. In terms of the NIC not working until sp4 is installed, can you just get the newest driver for the nic and see if that works?

by integrity

You cannot once you have setup a PDC then change that PDC to be a PDC in a different Domain, in order to move a PDC with NT4 you would have to reinstall the OS, there is an alternative however:

You can install the the server as a Member server (another description is an Application server), to do this simply choose to install the server as a member server during installation, a Member server does not have a copy of the SAM database from the current PDC, it holds its own fully writable version. To get around the NIC problem when installing the server as a member server you can choose to use the MS Loopback adapter, since the NIC does not have to be operational in order to join the domain.
Once you have the server up and running you canthen install whatever SP you need and install the correct driver for your NIC, once this has been done you can then configure the protocols that are needed in your network. (remove the Loopback adapter at this point)
The last step is to attach the server to the existing domain as a BDC, simply attach the server to the point set out for it then upgrade it from member server to BDC in the domain of your choice, at this point the server will contact the PDC of the domain obtain a copy of the SAM databse and its finished.

Recap:
Install NT4 server as a member server.
During installation you do not need the NIC plugged into any point, use the MS Loopback adapter in the NIC list.
Install SP4.
Install your NIC driver and configure the protocols.
Attach your member server to the network and upgrade from Member Server to BDC.

Hope this helps you.

I would also advise you to get a new set of NICs for your network as you must either be using very old ones or using unknown ones, 3COM, DLink etc are the usual NICs that I use.

by johnnyextreme

Going from a member server to a BDC is not an upgrade, it is a reinstall. See http://support.microsoft.com/default.aspx?scid=kb;EN-US;q193219 and would be the same as starting from where I am now. The DLink DFE530TX doesn't work until SP4 is installed. An NE2000 compatible card is recognized during install but the server still can't contact the domain controller during install. I will try other network cards I have around until one works.

This discussion is closed to new replies.