This is the built-in help made by Microsoft for the command 'New-ADDCCloneConfigFile', in PowerShell version 3 - as retrieved from
Windows version 'Microsoft Windows Server 2012 Standard' PowerShell help files on 2016-06-23.
For PowerShell version 3 and up, where you have Update-Help, this command was run just before creating the web pages from the help files.
Performs prerequisite checks for cloning a domain controller and generates a clone configuration file if all checks succeed.
New-ADDCCloneConfigFile [-CloneComputerName <String>] [-IPv4DNSResolver <String[]>] [-Path <String>] [-SiteName <String>] [<CommonParameters>]
New-ADDCCloneConfigFile [-AlternateWINSServer <String>] [-CloneComputerName <String>] [-IPv4DefaultGateway <String>] [-Path <String>]
[-PreferredWINSServer <String>] [-SiteName <String>] -IPv4Address <String> -IPv4DNSResolver <String[]> -IPv4SubnetMask <String> -Static
[<SwitchParameter>] [<CommonParameters>]
New-ADDCCloneConfigFile [-AlternateWINSServer <String>] [-CloneComputerName <String>] [-IPv4Address <String>] [-IPv4DefaultGateway <String>]
[-IPv4DNSResolver <String[]>] [-IPv4SubnetMask <String>] [-IPv6DNSResolver <String[]>] [-PreferredWINSServer <String>] [-SiteName <String>]
[-Static [<SwitchParameter>]] -Offline [<SwitchParameter>] -Path <String> [<CommonParameters>]
New-ADDCCloneConfigFile [-CloneComputerName <String>] [-IPv6DNSResolver <String[]>] [-Path <String>] [-SiteName <String>] [<CommonParameters>]
New-ADDCCloneConfigFile [-CloneComputerName <String>] [-Path <String>] [-SiteName <String>] -IPv6DNSResolver <String[]> -Static
[<SwitchParameter>] [<CommonParameters>]
The New-DCCloneConfigFile cmdlet performs prerequisite checks for cloning a domain controller (DC) when run locally on the DC being prepared
for cloning. This cmdlet generates a clone configuration file, DCCloneConfig.xml, at an appropriate location, if all prerequisite checks
succeed.
There are two mode of operation for this cmdlet, depending on where it is executed. When run on the domain controller that is being prepared
for cloning, it will run the following pre-requisite checks to make sure this DC is adequately prepared for cloning:
(1) Is the PDC emulator FSMO role hosted on a DC running Windows Server 2012?
(2) Is this computer authorized for DC cloning (i.e. is the computer a member of the Cloneable Domain Controllers group)?
(3) Are all program and services listed in the output of the Get-ADDCCloningExcludedApplicationList cmdlet captured in
CustomDCCloneAllowList.xml?
If these pre-requisite checks all pass, the New-DCCloneConfigFile cmdlet will generate a DCCloneConfig.xml file at a suitable location based
on the parameter values supplied. This cmdlet can also be run from a client (with RSAT) and used to generate a DCCloneConfig.xml against
offline media of the DC being cloned, however, none of the pre-requisite checks will be performed in this usage mode. This usage is intended
to generate DCCloneConfig.xml files with specific configuration values for each clone on copies of the offline media.
<
Online Version: http://go.microsoft.com/fwlink/?LinkId=246280
Get-ADDCCloningExcludedApplicationList
<
-------------------------- EXAMPLE 1 --------------------------
PS C:\>New-ADDCCloneConfigFile –Static -IPv4Address "10.0.0.2" -IPv4DNSResolver "10.0.0.1" -IPv4SubnetMask "255.255.255.0" -CloneComputerName
"VirtualDC2" -IPv4DefaultGateway "10.0.0.3" -PreferredWINSServer "10.0.0.1" -SiteName "REDMOND"
Creates a clone domain controller named VirtualDC2 with a static IPv4 address.
-------------------------- EXAMPLE 2 --------------------------
PS C:\>New-ADDCCloneConfigFile -Static -CloneComputerName "Clone1" -IPv6DNSResolver "FEC0:0:0:FFFF::1"
Creates a clone domain controller named Clone1 with a static IPv6 settings.
-------------------------- EXAMPLE 3 --------------------------
PS C:\>New-ADDCCloneConfigFile -AlternateWINSServer "10.0.0.3" -CloneComputerName "Clone2"-IPv4DNSResolver "10.0.0.1" -PreferredWINSServer
"10.0.0.1"
Creates a clone domain controller named Clone2 with dynamic IPv4 settings.
-------------------------- EXAMPLE 4 --------------------------
PS C:\>New-ADDCCloneConfigFile -IPv6DNSResolver "FEC0:0:0:FFFF::1" -SiteName "REDMOND"
Creates a clone domain controller with dynamic IPv6 settings.
-------------------------- EXAMPLE 5 --------------------------
PS C:\>New-ADDCCloneConfigFile –Static -IPv4Address "10.0.0.2" -IPv4DNSResolver "10.0.0.1" -IPv4SubnetMask "255.255.255.0" -Static
-IPv6DNSResolver "FEC0:0:0:FFFF::1" -CloneComputerName "Clone2" -PreferredWINSServer "10.0.0.1"
Creates a clone domain controller named Clone2 with static IPv4 and static IPv6 settings.
-------------------------- EXAMPLE 6 --------------------------
PS C:\>New-ADDCCloneConfigFile -IPv4Address "10.0.0.2" -IPv4DNSResolver "10.0.0.1" -IPv4SubnetMask "255.255.255.0" -IPv4DefaultGateway
"10.0.0.3" -IPv6DNSResolver "FEC0:0:0:FFFF::1"
Creates a clone domain controller named Clone2 with static IPv4 and dynamic IPv6 settings.
-------------------------- EXAMPLE 7 --------------------------
PS C:\>New-ADDCCloneConfigFile –Static -IPv6DNSResolver "FEC0:0:0:FFFF::1" -CloneComputerName "Clone1" -PreferredWINSServer "10.0.0.1"
-SiteName "REDMOND"
Creates a clone domain controller named Clone1 with dynamic IPv4 and static IPv6 settings.
-------------------------- EXAMPLE 8 --------------------------
PS C:\>New-ADDCCloneConfigFile -IPv4DNSResolver "10.0.0.1" -IPv6DNSResolver "FEC0:0:0:FFFF::1"
Creates a clone domain controller with dynamic IPv4 and dynamic IPv6 settings.
-------------------------- EXAMPLE 9 --------------------------
PS C:\>New-DCCloneConfig –Offline –CloneComputerName CloneDC1 –SiteName REDMOND –Path F:\Windows\NTDS -Force
Creates a clone domain controller named CloneDC1 in offline mode, in a site called "REDMOND" with a dynamic IPv4 address. This command also
uses the -Force parameter to force overwrite of any previous DCCloneConfig.xml file created at the specified path (F:\Windows\NTDS).