Block WinRM operations during servicing
The WinRM service starts normally and accepts requests during component servicing operations (eg, "Working on Updates", "Working on Features" screens after a post-update/feature-change reboot). This causes problems for configuration management in cases where the servicing process triggers further reboots, especially since there doesn't appear to be a documented way to determine that servicing is underway. WinRM should either wait to accept requests until servicing is complete, or a way for third-party tools to determine that servicing is underway from Powershell should be documented.
Matt Davis
shared this idea
3 comments
-
Matt Davis
commented
(doesn't look like I have the ability to edit the original text or change the title)
-
Matt Davis
commented
Sorry- I never saw this comment until the "Survey" status change (/me checks the "send email on comments" flag.)
Yeah, focusing on the "is there servicing happening" part would definitely be better than nothing.
Thanks!
-
I would like to re-name this item to focus on the request for a way to determine if servicing is underway. This seems like it could be achievable, & I would mark it as a Survey item to gauge interest.
The recommendation to block WinRM during servicing would result in some very bad behaviors, particularly during a rollback. That particular request would have to be declined.
If this is OK, pls reply or simply modify the title.
