The Enable-DscDebug cmdlet enables Windows PowerShell 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.
Examples
Example 1: Start debugging
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.
Runs the cmdlet in a remote session or on a remote computer. Enter a computer name or a session
object, such as the output of a New-CimSession or
Get-CimSession cmdlet. The default is the current
session on the local computer.
Specifies the maximum number of concurrent operations that can be established to run the cmdlet. If
this parameter is omitted or a value of 0 is entered, then Windows PowerShell calculates an
optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the
computer. The throttle limit applies only to the current cmdlet, not to the session or to the
computer.
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable,
-InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable,
-ProgressAction, -Verbose, -WarningAction, and -WarningVariable. For more information, see
about_CommonParameters.
The source for this content can be found on GitHub, where you can also create and review issues and pull requests. For more information, see our contributor guide.