W
Will
I need to install a temporary NT4 BDC controller in order to migrate some
ancient hardware that runs the PDC of an NT4 domain to Windows 2000 and
Active Directory. The problem I have is that when doing the installation
of NT4 on new hardware, DHCP fails when I select BDC as the install type.
However if I try to install an NT4 member server, then DHCP works just fine
and the install proceeds without a hitch. The server boots and works on
the network just fine.
NT4 member servers cannot be upgraded to become BDCs. You must re-run the
entire Windows NT4 install and specify BDC as your target for the install.
So what would cause this odd behavior, and is there anything I can do that
would defer the need to bring the network up until some point after the
overall install is finished? I'm sure I could get DHCP to work fine once
the BDC install is complete, but it cannot complete because DHCP won't work
during the BDC install. It's a catch 22 and I don't see a way out.
Any ideas?
ancient hardware that runs the PDC of an NT4 domain to Windows 2000 and
Active Directory. The problem I have is that when doing the installation
of NT4 on new hardware, DHCP fails when I select BDC as the install type.
However if I try to install an NT4 member server, then DHCP works just fine
and the install proceeds without a hitch. The server boots and works on
the network just fine.
NT4 member servers cannot be upgraded to become BDCs. You must re-run the
entire Windows NT4 install and specify BDC as your target for the install.
So what would cause this odd behavior, and is there anything I can do that
would defer the need to bring the network up until some point after the
overall install is finished? I'm sure I could get DHCP to work fine once
the BDC install is complete, but it cannot complete because DHCP won't work
during the BDC install. It's a catch 22 and I don't see a way out.
Any ideas?