This is the built-in help made by Microsoft for the command 'Get-ADDCCloningExcludedApplicationList', 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.
Returns the list of installed programs and services present on this domain controller that are not in the default or user defined inclusion list.
Get-ADDCCloningExcludedApplicationList [-Force [<SwitchParameter>]] [-Path <String>] -GenerateXml [<SwitchParameter>] [<CommonParameters>]
The Get-ADDCCloningExcludedApplicationList cmdlet searches the local domain controller for programs and services in the installed programs
database, the services control manager that are not specified in the default and user defined inclusion list. The applications in the
resulting list can be added to the user defined exclusion list if they are determined to support cloning. If the applications are not
cloneable, they should be removed from the source domain controller before the clone media is created. Any application that appears in cmdlet
output and is not included in the user defined inclusion list will force cloning to fail.
Once you have granted a source virtualized DC permissions to be cloned, the Get-ADDCCloningExcludedApplicationList cmdlet should be run a
first time with no additional parameters on the source virtualized domain controller to identify all programs or services that are to be
evaluated for cloning. Next, vet the returned list with your software vendors and remove any applications from the list that cannot be safely
cloned. Finally, you can run the Get-ADDCCloningExcludedApplicationList cmdlet again using the –GenerateXml parameter set to create the
CustomDCCloneAllowList.xml file.
The Get-ADDCCloningExcludedApplicationList cmdlet needs to be run before the New-ADDCCloneConfigFile cmdlet is used because if the
New-ADDCCloneConfigFile cmdlet detects an excluded application, it will not create a DCCloneConfig.xml file. For more information on virtual
domain controller cloning, see the guidance on ADDS virtualization at http://go.microsoft.com/fwlink/?LinkId=208030.
<
Online Version: http://go.microsoft.com/fwlink/?LinkID=216343
<
-------------------------- EXAMPLE 1 --------------------------
C:\PS>Get-ADDCCloningExcludedApplicationList
Description
-----------
Displays the excluded application list to the console. If there is already a CustomDCCloneAllowList.xml, this cmdlet displays the delta of
that list compared to the operating system (which may be nothing if the lists match).
-------------------------- EXAMPLE 2 --------------------------
C:\PS>Get-ADDCCloningExcludedApplicationList -GenerateXml -Path C:\Windows\NTDS -Force
Description
-----------
Generates the excluded application list as a file named CustomDCCloneAllowList.xml at the specified folder path (C:\Windows\NTDS) and forces
overwrite if a file by that name is found to already exist at that path location.