We had an interesting scenario when the RDAgentBootLoader service stopped on a session host. This resulted in the host being flagged as "unavaileble" on the AVD broker and some users were getting loggin errors. This is all as expected when this happens. The simple fix is to start the service manually and it became available again. For some reason Windows didn't recover the service.
We have Autoheal enabled with:
"Host is broken if AVD agent status is: unavailable" and "Has no active sessions"
There were 3 active sessions at the time so autoheal didn't trigger as expected as we don't want the active people to get kicked out.
I wonder could there be some extra logic added to autoheal to maybe try to start/restart the RDAgent and RDAgentBootLoader services using a powershell script if the VM is online but unavailable and has active sessions.
Comments (0 comments)