Define supported Hyper-V Replica use for domain-controller VMs

Use this document to resolve one bounded operational decision: Define supported Hyper-V Replica use for domain-controller VMs. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Support for using Hyper-V Replica for virtualized domain controllers from Microsoft supports the following bounded statements:

• Hyper-V Replica asynchronously replicates selected VMs across LAN or WAN links. The research record locates this support at Opening overview.
• The document distinguishes supported and unsupported scenarios and requires Windows Server 2012 or newer domain controllers. The research record locates this support at Sections: Windows Server 2012 or newer domain controllers required; Supported and unsupported scenarios.

These statements are the factual basis for this document. Do not extend them into a broader assurance. Review forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles only where the source and recorded environment align.

What the source does not establish

VM replication does not replace AD-aware backup, recovery planning, or replication-health monitoring. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity before translating the source into an operational decision.

Applicability questions

• For source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Sections: Windows Server 2012 or newer domain controllers required; Supported and unsupported scenarios, which observable configuration, record, or test can confirm applicability here?
• What inventory proves which parts of forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles are in and out of scope?
• Which condition in Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity must be healthy before evidence is trustworthy?
• What result would disprove the working assumption and return the issue to the owner?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles, observed and expected states, owner, and reason for deviation.

Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity, while excluding secrets and sensitive personal or topology data from ordinary tickets.

Verification and evidence

Build a reproducible chain from Opening overview; Sections: Windows Server 2012 or newer domain controllers required; Supported and unsupported scenarios to the observed environment. Useful domain evidence includes directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests; label every item with scope, timestamp, collector, and stable identifier.

Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.

Official references

• Support for using Hyper-V Replica for virtualized domain controllers — Microsoft