Some time ago we implemented an Active Directory installation. Our NT4
DHCP server was not part of the upgrade, but now we want to move DHCP
The NT4 DHCP server is not a member of the AD.
We installed the DHCP service onto the AD-BDC, setup the scope,
authorized the server, turned off the old DHCP server, activated the
scope on the new DHCP server, and got nothing. It does show that it
sees requests, and is on the same subnet as the scope it is trying to
provide. It just doesn't answer the call to duty.
We tried using the registry edit to turn off rogue detection, but that
has had no impact. All related servers and clients have been rebooted
numerous times. We also saw, much too late, the words from MS:
"For the directory authorization process to work properly, it is
and necessary that the first DHCP server introduced onto your network
participate in the Active Directory service. This requires that the
be installed as either a domain controller or a member server. When you
are either planning for or actively deploying Active Directory
important that you do not elect to install your first DHCP server
as a stand-alone server."
My question is... how do you contend with the situation where you DID
have a DHCP server that was a stand-alone server before any other DHCP
servers were in AD? Reinstalling AD isn't a very good option.