administration
536 TopicsAVD Forced log off by user
My suggestion for a feature request is to add a logoff/force-logoff option in both the web client and AVD client at a minimum. Right now, if a user logs into a host and they hit a black screen or any other type of error they are stuck to that host until the session is force logged off by an admin or they hit the logoff timeout that an admin sets. This would save frustration and productivity loss for a user that would have to wait for an admin to help. This is especially needed for companies that support around the clock teams.[Enterprise Customer Feedback] - AVD Forced Log Off
After going over the issue with support, we couldn't find a solution that an end user can self-service themselves to rectify when an AVD session host is having a performance issue. The host session VM booted up per our scaling policy at 7:45 a.m. and immediately had a User Profile service error. When the first attempted session connection occurred about 15 minutes later, it failed to load the session and only left the user with a black screen. Disconnecting and relaunching the session still placed them in the session hung session. We employ a disconnected session log-off policy of 120 total minutes. It would take at least 2 hours without user interaction for a session to fully terminate. There is no way a user can force log off their session in either the web client or Azure Virtual Desktop client. The only option available is to disconnect but it maintains the session live in the backend. My suggestion for a feature request is to add a logoff/force-logoff option in both the web client and AVD client at a minimum. And, an option for the end user to avoid a new session connection to the host that was having the issue. This might limit productivity time loss as IT works on rectifying the issue. (most likely a reboot of the session host machine).2.6KViews1like2Comments