Information Technology Reference
In-Depth Information
Supported Microsoft virtualization host platforms:
Microsoft Windows Server 2012 with Hyper-V feature
Microsoft Windows Server 2012 R2 with Hyper-V feature
Microsoft Windows Server 2012 Hyper-V Server
Microsoft Windows Server 2012 R2 Hyper-V Server
Microsoft Windows 8 with Hyper-V client feature
Microsoft Windows 8.1 with Hyper-V client feature
IMPORTANT
UNSUPPORTED RESTORES
Virtualized domain controllers do not support safe restores or cloning by manual copying
of VHDs over existing files or by VHD file restore using file backup or full disk backup
software.
preparing the source domain controller
After you verify that the environment meets the minimum requirements, you need to prepare
the source domain controller. The domain controller needs to be authorized for cloning by
making it a member of the Cloneable Domain Controllers security group in Active Directory.
You can use the Active Directory Administrative Center console, Active Directory Users and
Computers, or the Windows PowerShell ActiveDirectory module to assign the source domain
controller to the security group. The Windows PowerShell for this is the following:
Get-ADComputer <sourcedc> | Foreach-Object `
{Add-ADGroupMember -Identity "Cloneable Domain Controllers" $_.SamAccountName }
Identify any applications that will prevent cloning by running the
Get-ADDCCloningExclusionApplicationList cmdlet. Any applications or services identified
must be either removed or added to the CustomDCCloneAllowList.xml file. After you re-
move any services or applications that don't support cloning, you can use the -GenerateXML
parameter to create the CustomDCCloneAllowList.xml file. For example, on trey-rodc-03, I got
the following:
Get-ADDCCloningExcludedApplicationList
Name Type
---- ----
Vim 7.3 Program
HyperSnap 7 WoW64Program
Both programs are simple utilities used in writing this chapter: one to edit files and the
other to take screen shots. Neither one poses an issue with cloning, so I know I'm safe to add
them to the CustomDCCloneAllowList.xml file. So I ran the cmdlet again:
Get-ADDCCloningExcludedApplicationList -GenerateXML
The inclusion list was written to 'C:\Windows\NTDS\CustomDCCloneAllowList.xml'.
 
Search WWH ::




Custom Search