djwork

I have also hit this issue and it is very serious for my company as we need to sequence installation of packages for a successful server build. @pauby This issue...

This bug repeated consistently on 2016, I worked around it by putting the call to Register-PSSessionConfiguration within a PSJob, waiting for 10 seconds, setting $global:DSCMachineStatus = 1 at the end...

@jnury That's what I did [DscResource()] class JeaEndpoint { ## The mandatory endpoint name. Use 'Microsoft.PowerShell' by default. [DscProperty(Key)] [string] $EndpointName = 'Microsoft.PowerShell' ## The mandatory role definition map to...

Note, this is still an issue on PowerShell 5.1 on Windows 2019 and the workaround of setting HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System:DSCAutomationHostEnabled to 0 seems to cause problems continuing to apply DSC settings after...

same issue on Remove-HVPool

@raandree Tried to read through the [C#](https://github.com/PowerShell/PowerShell/blob/5f3dd938b792e1a395fd011ac1461246db7c0e1f/src/System.Management.Automation/engine/remoting/commands/CustomShellCommands.cs) I couldn't follow how NoServiceRestart is used at all in those functions

After trying this DSC in anger, I recommend adding a RebootOnWinRMHang switch to JeaSessionConfiguation, users can then set it to true if desired