Forum Discussion
VM Connection very often gets disconnected
Hello!
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
62 Replies
- FBackeBrass Contributor
Hello nicolasriderelli
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>
HKLM\Software\Microsoft\MSRDC\Policies
Type: REG_DWORD
Name: AutomaticUpdates
Value: 2
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.- WesODOCopper ContributorEither as a machine or user based install, the MSRDC doesn't exist for us in HKLM. It exists in HKCU but not in HKLM. Would this not also work in HKCU?
Thanks
- FBackeBrass Contributor
Double reply. Sorry for that, correct one posted below.
- nicolasriderelliCopper ContributorThanks FBacke! Ill try with solution! Thanks for sharing this in detail!
- thejonksCopper Contributor
nicolasriderelli Intersted to find out whether this ressolved the issues. We are experiencing simialar problems with our WVD deployment
- Niels_KokBrass ContributorAre you using a NAT gateway in your network?
- nicolasriderelliCopper ContributorNo. No NAT. Internet is routed via Microsoft. I have a a peering to my hub VNET to access on-prem
- Niels_KokBrass ContributorHi Nicolas,
Are all AVD URLs available? You can check it by using the following link:
https://docs.microsoft.com/en-us/azure/virtual-desktop/safe-url-list
Thanks,
Niels
- JoacbeCopper ContributorHello,
Same here, users being disconnected several times a day, randomly, and targeting most of our users.
Receiving the same error with an associated error code -2147467259, every time the issue happens for a user, there are two logs entries generated, absolutely identical. No more luck to understand what is behind.
I had an incident opened by MS support to get more but haven't been contacted yet.- Mona GoldsteinCopper Contributor
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."
- nicolasriderelliCopper ContributorI get the same error. MS Support is saying that is the ISP, but a lot of users are using the same ISP and no issues.