Jan 19 2022 10:06 AM
Jan 19 2022 10:06 AM
I'm seeing a lot of disconnects in my hostpools.
Just in the last 24 hours, a user had the following
The connection from the client to the Windows Virtual Desktop service was terminated unexpectedly. (24 times)
The network connection between the Windows Virtual Desktop client and the service was unexpectedly interrupted. (50 times)
So far the Azure infrastructure is good. No issues with the session hosts. This issue is affecting 20 users out of 700.
Is there any way I can investigate deeper to get more knowledge on what is going on? The LogAnalytics is only giving partial information
Jan 25 2022 02:21 AM
Feb 22 2022 12:38 PM
Any news on this? I have just about the same issue. Users in the US and India. If session goes idle for more than an error, user can't reconnect and has to be logged out.
Log Analytics show a high rate of "The network connection between the Windows Virtual Desktop client and the service was unexpectedly interrupted."
Feb 23 2022 11:23 AM
Feb 23 2022 11:24 AM
Feb 23 2022 10:59 PM
Feb 24 2022 12:30 PM
Feb 24 2022 01:39 PM
Feb 24 2022 10:53 PM
Feb 25 2022 12:42 AM - edited Feb 25 2022 11:33 AM
Double reply. Sorry for that, correct one posted below.
Feb 25 2022 02:12 AM - edited Feb 25 2022 11:35 AM
We had struggles with this issue for one of our customers for quite a while.
1 hostpool with 4 AVD-hosts, ca 50 users.
A mix of both Remoteapps and Full Desktop. Not every user had the issue, but at least half of them suffered from it every other day, multiple times a day.
We found that when you install ”Remote Desktop Client” on a PC, there is a Scheduled Task created that refreshes your AVD feed every 4 hours or so.
And when looking in Azure Insights Monitor I could see that some of the users got the: ConnectionFailedClientDisconnect (-2147467259) error exactly 4 hours apart. But some had it more frequently. It was not adding up..
Seems like when you close MSRDC, and the scheduled task runs, it also tries to update MSRDC if there’s an update available.
The customer who had this issue were not local admins on their computers. So if they had closed the MSRDC window and the Scheduled task ran, they would get disconnected with no warnings or error messages. And Azure Insight Monitoring would capture the ConnectionFailedClientDisconnect (-2147467259) error with the same timestamp as the scheduled task had been executed.
So our solution was the following:
We did not make the users local admins on their computers, but we reinstalled Remote Desktop Client and choose the ”per-user” option (Install only for me) instead of the ”per-machine” install as we had done before.
And then we created a GPO with the registry Key>
The customer has not had the issue since. And the MSRDC client autoupdates with no issues even that the users are not local admins.
Hope this can help others out there.
Feb 27 2022 11:34 PM
Mar 01 2022 04:18 AM - edited Mar 01 2022 04:19 AM
Unfortunately not. We are going to roll out Windows 10 session hosts for the impacted customers, since we are experiencing more problems on 11 AVD than just the random disconnects.
I have been able to do some short testing with a newer recent deployment of Windows 11 multi-sesion in AVD, where I am not getting any disconnects so far with my testing method. But I haven't done enough testing to conclude that it might have been fixed with a newer version of the W11 AVD image.