I originally asked this question on stack overflow and was referred here.
Using Hyper-V I built a private windows domain which is fenced off from our main network. Ultimately I want to provision this domain for others to use for dev and test, so they can be domain admin.
My problem is this: the domain controller has the DHCP service running. If someone deploys the domain to their Hyper-V host and mistakenly connects it to the main network, the DHCP service will start assigning bad IP configurations.
I would like to prevent this situation. I considered writing a service to wrap dhcploc, this service would then stop the local DHCP service if a remote DHCP server can be found. This is really damage limitation, since the rogue DHCP server would still have a small window of opportunity.
Is there is a better/simpler alternative that would acheive the objective? Are there any caveats I should be aware of?