DSC supports applying DSC configurations locally and remotely using the Start-DSCConfiguration cmdlet. This cmdlet handles both the copying of the MOF file to the target node and telling DSC to execute the MOF on the target node.

Start-DSCConfiguration can be invoked interactively as well as be run in the background. Interactive executions are run as we are watching and are able to show verbose output as each step in the DSC configuration happens. Background executions are PowerShell jobs that do not block your shell so that you can do other things while the job runs. This means you can use this cmdlet to push a DSC configuration and then walk away or continue to use your current PowerShell console session to do other things as it executes on the target node.

All output from the DSC configuration execution is logged by DSC, and the Start-DSCConfiguration cmdlet can show this information if configured. By default, it displays only the error and completion information, but it can be configured to yield verbose output using the Verbose parameter.

It is important to note that Start-DSCConfiguration does not perform the execution itself; the DSC service does this on the target node. This means nothing is tied to you, your shell, or your session. Your current console session could stop or go away and the execution would still run. This allows a set it and forget it workflow where you push a configuration and walk away to do other things while it runs and then come back and find the results of the execution ready and waiting for you.