Remove active directory from this computer without updating forest metadata
Below are the Windows Server 2012 cloning-specific events in the Directory Services event log, with notes and suggested resolutions for errors.has found a virtual domain controller cloning configuration file.A failed clone does not return to normal mode on its own on the next reboot; you must remove the DS Restore Mode boot flag in order to try cloning again.All of these steps require running as an elevated administrator.Attempts to add features or roles while in DSRM will not complete and leave the computer in an unstable state until it is booted normally.
By default, a Windows Server 2012 computer installation is a Server Core installation, which means there is no graphical interface and therefore, no way to run the local Event Viewer snap-in.
It can also be ignored on non-virtual Domain controllers. This occurs when a is found but a VM Generation-ID could not be found, such as when a file is found on a physical computer or on a hypervisor that does not support VM Generation-ID.
Rename attempt expected when booting a source VM back up, because the VM Generation ID has not changed.
The DC is hosted on a physical machine, a down-level version of Hyper-V, or a hypervisor that does not support the VM Generation ID.
Additional Data Failure code returned when checking VM Generation ID:%1A Generation ID change has been detected.
The critical elements to advanced troubleshooting of domain controller configuration are: The first and second are beyond the scope of this topic, but the third can be explained in some detail.