Jul 24 2019 08:54 AM
Jul 24 2019 08:54 AM
Hi, I am seeing very slow speeds when browsing and opening files/folders on my local C drive when connected to a windows virtual desktop. When in file explorer on the virtual desktop, it takes up to 20 seconds to display all folders in my C drive when I click on the local C drive from my own machine. I only have 24 folders in my C drive. This issue is manifesting in different forms also, in relation to an in-house application which can create excel files on the local C drive and write records to those files. This is extremely slow. Latency to the Azure region is definitely not the issue and internet connection speed is good. Increasing the VM size to DS8 V3 makes no difference. Has anyone experienced this issue or is there a network bandwidth limit or throughput setting that can be changed? It is making the app unusable at present. Thanks.
Jul 25 2019 03:06 AM
Can anyone explain the network routing that takes place in relation to the load balancer setup in Windows Virtual Desktop? I suspect that the slow connection speeds are down to the specific WVD setup as we have plenty of "normal" Azure VMs (not in the WVD hostpool) where we don't see any slowness at all. Thanks in advance!
Jul 25 2019 08:16 AM
Could the slowness be attributed to the control-plane for WVD being located in east US 2 currently, whereas my resources are located in North Europe? I read somewhere that your performance using a host pool outside of the US might vary until the control plane is added to other regions...
Oct 04 2019 12:18 PM
We had this issue and it turned out to be the mapped drives on the local PC slowly passing through to the WVD session and therefore slowing down the loading of the local drives on the WVD host.
You can disable this using drivestoredirect:s: switch on the hostpool via PS
Nov 08 2019 05:04 AM
@Rg035 The connection/browsing speed between local PC and session host VM has increased considerably since WVD went into general release. I am assuming that the improvement is down to the control plane for WVD being created in my region (North Europe). During public preview, the control plane was in East US 2 and my session host VMs were in North Europe, which introduced latency.