Forum Discussion
AVD - Disconnects throughout the day
Hi,
We have been running on a AVD environment for quite a while now, since a few months our client has been experiencing constant disconnects, sometimes there is a day they have no issues, then the next day they have 30 disconnects.
There isn't a specific error they get, they just lose the connection and can reconnect in 20-30 seconds. Everyone has issues with it, no specific users, no specific times.
A ticket with Microsoft has been opened 3 months ago and since then we haven't got any further hence why I thought I'd post something here to see if anyone has similiar issues.
Our Log Analytics workspace consists of the following errors lately;
ReverseConnectResponseTimeOut
ConnectionFailedServerDisconnect
ConnectionFailedClientDisconnect
We have a registry key added for the ConnectionBrokenMissedHeartbeatThresholdExceeded.
Our environment consists of the following;
File server which hosts FSLogix profiles on a 1TB Premium SSD
3x AVD Host E8s v5 with Premium OS Disks.
- The machines are part of the same vNet, only a different subnet,
- All the Remote Desktop Clients have been updated to the latest version (1.2.3770.0).
I saw someone mention the AVD Agents so the version we have of those are the following;
- RDS Infrastructure Agent 1.0.5555.1010 (Last update 6-12-2022)
- RDS SxS Network Stack 1.0.2208.17300 (Last update 29-10-2022)
The following has already been tested and worked out;
- New clean images build up from scratch
- Marketplace images for Session hosts
- Upgraded machine versions for performance
- Network traces
Im sure im missing quite some steps we also have taken because it has been quite the ongoing process.
jonathanmesaMicrosoft
- To be honest I have not tested this with the webclient and the client neither, they only make use of the RD Client. I will put this on the list.
- We have seen the same problem for a long time in Europe West. We have a open case with MS Support since august.
I don't believe the BrokenMissedHeartbeat registry key makes any difference (we had it in production for a while). It doesn't fix the problem, it will only give you less error-messages in your logs.
ConnectionFailedServerDisconnect is normally a problem on MS side and not on customer side like ConnectionFailedClientDisconnect. We have been in contact with another customer in the same region who see the mass-disconnects at the exact same time as us.
Do you have an open case with MS on this? If not, I think it is a good idea to have as many customers as possible to create a support ticket.- Hi Henrik,
We currently also have an open case with Microsoft on this, but we haven't gotten any further in the last months.
We also operate out of the West Europe region, sadly there is nothing we can pinpoint as the issue since it happens so randomly and doesn't generate many error messages where we can dig deeper.
The Heartbeat reg key was also another attempt to see if it fixes anything, sadly it didn't.
Hi ,
any resolution from MS ? Even I am facing similar issue in southeast and India region .
very often disconnects happening for users.
I have raised a case with MS also . They are investigating for last 2 months .txn
