I service and troubleshoot the internal network at the company I work for. The DHCP service was migrated last month
from a non-native virtual domain controller running Windows Server 2008 Standard w/o Hyper-V to an identical machine (A DC running Windows Server 2008 Standard w/o Hyper-V) that is physical rather than virtual. My supervisor wanted the DHCP service shifted
to a physical machine so avoid boot issues with the virtual during each restart cycle/maintenance period. Recently, my supervisor inquired about having two DHCP servers for redundancy.
Both servers are required to remain on the same network. An OS upgrade is not an option at this time. The current reservations are scattered throughout the address pool and cannot be changed for various reasons (10.215.1.120/24 - 10.215.1.185/24 is an equivalent example pool to the network in question). There are over 50 hosts, and about 30 reservations. Split-scope is not an option. Clustering seems viable, but I'm uncertain about how that will work with one machine being a virtual host. Static assignment is an option, however arduous.
What Redundancy/Failover options do I have? Am I doomed to static assignment, or is there another viable option?
Both servers are required to remain on the same network. An OS upgrade is not an option at this time. The current reservations are scattered throughout the address pool and cannot be changed for various reasons (10.215.1.120/24 - 10.215.1.185/24 is an equivalent example pool to the network in question). There are over 50 hosts, and about 30 reservations. Split-scope is not an option. Clustering seems viable, but I'm uncertain about how that will work with one machine being a virtual host. Static assignment is an option, however arduous.
What Redundancy/Failover options do I have? Am I doomed to static assignment, or is there another viable option?