Forum Discussion
Solved
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 ...
I already thought about setting up a RDS GW myself, and let that server broker / load balance / gateway the WVD sessions. Too bad Server 2019 GW does not support Windows 10 multi-session as workers for the farm.
The last few weeks I was checking for disconnects for this command:
Get-RdsDiagnosticActivities -Outcome Failure -starttime 13-03-2020 -detailed -tenant <<TENANTNAME>> | sort-object endtime | ft
Now it suddenly gives me this error:
Get-RdsDiagnosticActivities : There were no activities found.
Does anyone else have this too?
The last few weeks I was checking for disconnects for this command:
Get-RdsDiagnosticActivities -Outcome Failure -starttime 13-03-2020 -detailed -tenant <<TENANTNAME>> | sort-object endtime | ft
Now it suddenly gives me this error:
Get-RdsDiagnosticActivities : There were no activities found.
Does anyone else have this too?
Haven't tested the cmdlet, but my feedback is the same, issue still persists.
I rebooted all hosts yesterday evening. After hours feedback was very good, unfortunately office hours started again and latency went up.
I rebooted all hosts yesterday evening. After hours feedback was very good, unfortunately office hours started again and latency went up.
It's everwhere (at least in West EU) again. Raised the ticket with MS back to A.
I'm reverting back to Vanilla-RDP on the same infrastructure while MS fixes this. The problem isn't present on the same Azure infrastructure over standard RDP, not using the WVD Gateway. All you need to do is reconfigure the client if you're running a single server WVD deployment. Oh, and grant Remote Desktop access on the Win10 Multiuser Box. For multiple server deployments I haven't found a solution yet except forego Load Balancing and point individual groups of users to individual machines. What a mess
Here also. Very, very slow connection.
