The new Maintenance Window has given our customer additional stability as we can now clearly control, when Microsoft is pushing updates to its various AVD agents to the session hosts.
While this issue has been mostly resolved now, a new "issue" surfaced. When we select to startup all machines during a maintenance window, at the end of the window a multitude of session hosts is stopped again.
During this stopping, we have observed timing issues where user connect to a session host that was marked to be shut down. This results in a loop for the user as he gets disconnected multiple times. (reconnecting, he gets logged in to the same VM that is shutting down)
Within the Shutdown VM logs, we have seen that the log off loops through for 6 times before shutting down the VM in the end.
It would be great to have some additional checks within this automated action to not shut down any VMs when user sessions are detected on any of these VMs. Of course, this should only apply at the end of the maintenance window and not for normal Shutdown VM tasks.
Comments (0 comments)