Jun 28 2023 07:48 AM - edited Jun 28 2023 07:49 AM
I have a customer which is experiencing multiple issue working with AVD through the Remote Desktop Client. These issues have been reported for a few months and we have looked into them. Some got sorted out or got solved in new version of the Remote Desktop Client (or with newer Azure stack). But we still have some open issues which we cannot solve because it looks to be bugs in the Remote Desktop Client itself.
Before I start summing up the problems I will describe the environment.
User
A user works on their company owned and Intune managed device, an example is a Lenovo with i5 (11th), 16 GB of RAM running OS Windows 10 Enterprise 22H2 (build 19045.2965). We are using Windows Defender as anti-virus program. And the Intune deployed Remote Desktop Client version 1.2.4240.0. There were earlier versions installed but moving to the newer one did not solve the issues.
The user works with local Office applications, Adobe Acrobat, Edge, etc. For the multiple business application the user AVD Published application. That’s where the issues start.
AVD environment
They have 25 machines in AVD with Windows 11 Enterprise multisession installed. Today they have 121 sessions (106 active) running on Standard D4ds v5 Azure virtual machines. They do not use the public preview RDP shortpath. They connect form multiple locations throughout the Netherlands.
Issues
What have we done
At this moment there is one user testing the full desktop instead of using published applications. I think focus, rendering, etc. will be better or even not exist in full desktop. But this customer needs the AVD published applications.
I have already made a Microsoft Support case but thought might as well post it here seeing allot of people may have ran into these issues.
Jun 29 2023 06:04 AM - edited Jun 29 2023 06:05 AM
Hi Paul,
The Remote App issues that I encountered could solved by this registry workaround:
Key: HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RdpCloudStackSettings
Value: RAILDVCActivateThreshold
Type: REG_DWORD
Data: 0
Microsoft has requested internally for a permanent fix on SXS.
All other AVD issues last months were related to:
- the lastest FSLogix builds. As a workaround I keep al my customer's session hosts on FSLogix 2201 hotfix 2 (2.9.8228.50276)
- RDP shortpath. As a workaround I enforce TCP connections on the client-side
Jun 29 2023 01:57 PM
Aug 30 2023 06:33 AM
Sep 06 2023 01:12 AM - edited Sep 06 2023 01:12 AM
@PowerToThePeople This did not solve any of the problems, MS never responded to the MS case. I will be making new one through our group CSP account. This will speed up things.