Forum Discussion
Consistent Thin Client Disconnection from WVD Pool
Hello we have been experiencing some random but consistent disconnects from our WVD Pool. We have roughly 10 users and have been getting different event viewer logs for when they disconnect. We have Thin Clients on Windows 10 version 1607. When the users disconnect it will happen multiple times per day, however some days they do not disconnect. Attached are the event viewer logs
148 Replies
Sbarnet Hi, we are also experiencing these issues for two weeks now (50 user environment).
- Happens from multiple locations (so independent of network or ISP).
- Happens on both Windows 10 and HTML5 clients.
- Seems to happen completely random.
- Problem so far not related to a particular WVD host in the pool.
- Some days no problems at all, the next day it could me 80+ disconnects on one day.
- It seems to be related to a session. When user A gets is in the morning, chances are high he will get it multiple time a day, until he completely logs off and on again, so a completely new sessions is build up.
Already have a Microsoft case running for this, but so far no solution, or not even a cause. I suspect Azure's WVD gateway, but can't prove this yet.
Does anyone else experience this in the West Europe region?
Greets, Marco
Marco Brouwer We are also facing same issue, even some of the active sessions got terminated all of suddenly. Not able to access further. Same West Europe.
VanellySha : Please review review diagnostics for the failed connection and match with troubleshooting guidance in our documentation: https://docs.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-set-up-overview
If you can't resolve the issue recommend to raise a support ticket.
Marco Brouwer we have the same problem at a client environment. It is really unworkable and we have a support case running for a few weeks still not resolved, sending in network traces almost every day but no real solution yet.
In my LAB I was able to reproduce it when we use the Azure NAT Gateway on the WVD subnet, removing the NAT gateway fixed the issue in my LAB, but for the client it did not fix the issue.
This client environment is running on WVD Classic (Fall release), next week I am going to migrate it to WVD Spring Release in the hope it will work more stable.
It is not really a WVD issue in general, we have clients that have no issues at all.
The issue is also Disconnect and auto-reconnect, it takes about 10-30 seconds each reconnect. Customer is using USB based smartcards for some authentication in an application. In every reconnect the application crashes because the smartcards is unreachable for all that time.
Region: West Europe.
Do you use an Azure NAT Gateway on the WVD subnet?
- Hi Stefan,
One of customers complained yesterday about several disconnects / reconnects. Reporting users where not on same WVD host, some working from home, some from 4G, some from the office. The only common component in that situation is the WVD gateway service, managed by Azure.
They use WVD classic in combination with a standard load balancer (for the purpose of having a static outgoing public ip), not Azure NAT gateway (load balancer is cheaper).
We have another customer on WVDv2, also with same load balancer configuration, no problems reported.
So I guess that if there is a connection between our issues, is has something to do with NATting the traffic on classic WVD, not with the new NAT GW product in particular.
To be honest, I still believe in the (unproved) theory that Azure WVD has 1001 gateway / broker servers, and it just depends on the fact if your Azure tenant gets assigned to a buggy one or something like that. Or that some WVD gw has some problems for an x period of time, or gets overloaded and customers are fe assigned to a different gateway cluster by hand of some non instant process.
In the history of this post, multiple people complain about "waves of disconnects" in the same period of time in the same Azure region, but not all of them at once. That would strengthen this theory.
But no way Microsoft would ever admit to something like that :). For us, I find the flow of traffic / WVD sessions within the by Azure managed part of WVD (brokering / gateway) a big unknown foggy cloud. You don't get enough information from the configurable logging to pinpoint / prove that something goes wrong in there and on what server in their big cluster.
When you contact MS support, your case goes from team to team, and they always point the finger to anything but themselves, although I provide "proof" that the problem is not on our side. If it's not on my side, on whose side is it then?
Also, they disabled reading WVD logging with powershell permanently around April due to "performance problems", that was actually confirmed by MS to me. Sure, you can now read the same logs with log analytics in Azure, but the reason provided for disabling these Powershell command remains "performance problems". Hmmm...
Please post your MS case number here, so Microsoft can bundle multiple cases into one big issue they can't ignore.
Greets
Marco Brouwer We've been having the same issue for about a week and a half. We have about 100 users on WVD. Last week everyone got kicked off and unable to connect. I log them off via the WVDAdmin tool and they can get back in.
Today we had a similar issue but only a had full of users got the sessions kicked off. I believe also this has to do with the WVD Session Gateway.
Thanks for the heads up! We do not experience the same. When we are disconnected, users auto-reconnect, or they connect again to their session manually.
- Sometimes it happens just for one user.
- Sometimes it happens for multiple users simultaneously (but not all). Those users are not (always) on same WVD host, and not on same client network / ISP (we have a few clients connecting from a 4G LTE router to rule out the customers network or ISP).
- Today it happened for all logged users at once, for the first time.
What really sticks out, is that is seems connected to particular sessions. User A get kicks out today 4 times, but tomorrow he's fine. Instead, user B gets kicked out tomorrow multiple times.
We asked users to completely log off and and log back in again after experiencing a disconnect, that "seems" to help. They don't get kicked out again that day.
You almost should say that a "new" session is being brokered / load balancing through another server in the Azure gateway cluster, which does not have the problem of disconnecting users at random.
Do you have contact with Microsoft about this? Can you tell me what troubleshooting steps have been taken so far?
We have the same random disconnects from a WVD Pool
- Which Remote Desktop app version are you currently using? Had the same issue before with previous version.
