Use VM-Generation ID and DCCloneConfig.xml to separate cloning from restore

Use this document to resolve one bounded operational decision: Use VM-Generation ID and DCCloneConfig.xml to separate cloning from restore. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Virtualized Domain Controller Architecture from Microsoft supports the following bounded statements:

• At boot, AD DS compares the hypervisor-provided VM-Generation ID with the value stored in NTDS.DIT; a mismatch resets the invocation ID and discards the RID pool. The research record locates this support at Virtualized domain controller cloning architecture > Overview.
• When the IDs differ, DCCloneConfig.xml selects cloning; without that file the domain controller follows snapshot-restoration processing, while a clone file without a host VM-Generation ID causes a DSRM boot. The research record locates this support at Virtualized domain controller cloning architecture > Cloning Detailed Processing > step 2.

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

Applies to Windows Server 2016, 2019, 2022, and 2025 with the documented hypervisor behavior; this architecture is not a backup or recovery runbook. 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 Virtualized domain controller cloning architecture > Overview, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Virtualized domain controller cloning architecture > Cloning Detailed Processing > step 2, 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.

If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity and sanitize protected material before retention.

Verification and evidence

Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Virtualized domain controller cloning architecture > Overview; Virtualized domain controller cloning architecture > Cloning Detailed Processing > step 2. 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.

Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.

Official references

• Virtualized Domain Controller Architecture — Microsoft