Validate every prerequisite before cloning a virtualized domain controller

Treat this document as a focused evidence review: Validate every prerequisite before cloning a virtualized domain controller. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Virtualized Domain Controller Deployment and Configuration from Microsoft supports the following bounded statements:

• Virtualized DC deployment has explicit platform requirements and critical caveats. The research record locates this support at Sections: Platform Requirements; Critical Caveats.
• The cloning workflow includes validating the hypervisor and verifying the PDC emulator role holder. The research record locates this support at Sections: Step 1 – Validate the Hypervisor; Step 2 – Verify the PDCE FSMO role.

Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles and the conditions the source actually describes.

What the source does not establish

Use only with supported hypervisors and versions; do not generalize cloning steps to ordinary VM copies. No current deployment state or change approval follows from the source alone. Validate Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity, and treat examples or options as conditional inputs rather than defaults.

Applicability questions

• For source statement 1 at Sections: Platform Requirements; Critical Caveats, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Sections: Step 1 – Validate the Hypervisor; Step 2 – Verify the PDCE FSMO role, 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. Use a two-person review for the source interpretation and the resulting operational decision. 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

Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Sections: Platform Requirements; Critical Caveats; Sections: Step 1 – Validate the Hypervisor; Step 2 – Verify the PDCE FSMO role. Favor directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests, linked to stable identifiers, time, and operator.

Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.

Official references

• Virtualized Domain Controller Deployment and Configuration — Microsoft