Hi Admin,
Hope you're doing well.
From my point of view, place all domain controllers within the same Hyper-V cluster. This ensures that the Active Directory infrastructure remains highly available and minimizes the risk of split-brain scenarios. Since Active Directory replication relies heavily on network connectivity, keeping DCs within the same cluster helps maintain a consistent replication topology. At the same time, deploy DNS servers alongside the Active Directory domain controllers within the same Hyper-V cluster. DNS is tightly integrated with Active Directory, and having DNS servers in close proximity to domain controllers helps ensure fast and reliable name resolution for AD-related services.
Similar to domain controllers, place all Certificate Authority servers within the same Hyper-V cluster to maintain high availability. CA servers typically handle critical functions related to certificate issuance and management, so ensuring their availability is crucial for the overall security infrastructure.
For DHCP servers, it's advisable to deploy them in separate Hyper-V clusters to distribute the load and avoid a single point of failure. However, if DHCP failover is configured at the DHCP server level, you can place the DHCP servers in the same Hyper-V cluster for redundancy.
Operation master roles such as RID master, schema master, PDC emulator, infrastructure master, and domain naming master are critical for Active Directory operations. It's recommended to distribute these roles across multiple domain controllers within the same Hyper-V cluster to ensure redundancy and fault tolerance.
In addition, if you have file servers with Scale-Out File Server (SOFS) clustering, deploy them in a separate Hyper-V cluster dedicated to file server workloads. This helps optimize storage performance and scalability for file sharing services.
Best Regards