Your network contains a Hyper-V host named Host1 that runs Windows Server 2012. Host1
contains a virtual machine named DC1. DC1 is a domain controller that runs Windows
Server 2012.
You plan to clone DC1.
You need to recommend which steps are required to prepare DC1 to be cloned.
What should you include in the recommendation? (Each correct answer presents part of the
solution. Choose all that apply.)
A.
Run dcpromo.exe /adv.
B.
Create a file named Dccloneconfig.xml.
C.
Add DC1 to the Cloneable Domain Controllers group.
D.
Run sysprep.exe /oobe.
E.
Run New-VirtualDiskClone.
Explanation:
http://blogs.technet.com/b/askpfeplat/archive/2012/10/01/virtual-domain-controller-cloning-inwindowsserver-2012.aspx
DCCloneConfig.xml is an XML configuration file that contains all of the settings the cloned
DC will take when it boots. This includes network settings, DNS, WINS, AD site name, new
DC name and more. This file can be generated in a few different ways.
There’s a new group in town. It’s called Cloneable Domain Controllers and you can find it in
the Users container. Membership in this group dictates whether a DC can or cannot be
cloned. This group has some permissions set on the domain head that should not be
removed. Removing these permissions will cause cloning to fail. Also, as a best practice,
DCs shouldn’t be added to the group until you plan to clone and DCs should be removed
from the group once cloning is complete. Cloned DCs will also end up in the Cloneable
Domain Controllers group. Make sure to remove those as well
No one think about D? Run sysprep.exe /oobe.
Should you prepare the VM being cloned?
in Server 2012 sysprep.exe /oobe is automatically run.