Reboot machine rather than WinRM service?

[ChrisLGardner]

Based on the discussion in this issue and the problems caused by this bug, should we be flagging the machine for a reboot as part of registering a session configuration rather than restarting the WinRM service?

In a test environment I've been effected by that bug even though I haven't changed the Path while testing the SessionConfiguration resource, rebooting the machine feels cleaner and doesn't completely stop the rest of a DSC configuration from applying if the LCM is flagged to not reboot automatically.

[devonfury]

I'd like to second this. I've been invoking the JeaSessionConfiguation resource using Chef and that fact that it restarts the WinRM service causes an error. Thankfully, it appears to be a non-terminating error. If possible, I think that it would definitely be better to simply flag for a reboot instead of restarting the WinRM service.

[raandree]

I was facing this issue in the last weeks and played with 'Unregister-PSSessionConfiguration' and 'Register-PSSessionConfiguration' a bit. It seems to me that the 'NoServiceRestart' switch is ignored most of the time and the WinRM service restarts despite 'NoServiceRestart' is present. This makes this issue pretty hard to solve.

[djwork]

@raandree Tried to read through the C# I couldn't follow how NoServiceRestart is used at all in those functions

[djwork]

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