This is the built-in help made by Microsoft for the command 'Enable-DscDebug', in PowerShell version 5 - as retrieved from
Windows version 'Microsoft Windows Server 2012 R2 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.
Start debugging of all DSC resources.
Enable-DscDebug [-AsJob] [-BreakAll] [-CimSession <CimSession[]>] [-ThrottleLimit [<Int32>]] [-Confirm] [-WhatIf] [<CommonParameters>]
The Enable-DscDebug cmdlet enables Desired State Configuration (DSC) resource debugging by the DSC engine, which is also known as the Local Configuration Manager (LCM). By
default, all resource instances break into the debugger.
<
Online Version: http://go.microsoft.com/fwlink/?LinkId=627545
Windows PowerShell Desired State Configuration Overview
Disable-DscDebug
Get-DscConfiguration
Get-DscConfigurationStatus
Restore-DscConfiguration
Start-DscConfiguration
Test-DscConfiguration
<
Example 1: Start debugging
PS C:\>Enable-DscDebug -BreakAll
This command indicates to the DSC engine or LCM to start resource debugging. The next time the configuration is run, the process enters the debugger.
Example 2: Start remote debugging
PS C:\>Enable-DscDebug -BreakAll -CimSession DeploymentServer
This command indicates to the DSC engine of the remote computer to start resource debugging.