Are your Windows 11 22H2 users experiencing issues connecting to your Microsoft RDS Farm?
Disclaimer: Please research this issue and understand what you are doing. Please learn how to backup your registry. iLogix Computer Solutions can not be held accountable for any issues that you introduce into your organisation. We are IT guys, like you, and we want to make your life easier, this is why we are blogging this.
iLogix Computer Solutions recently helped a business solve a Microsoft Remote Desktop Connectivity issue.
Microsoft Remote Desktop Server gives users a virtual Windows Desktop where they can run applications. The desktop or App is delivered from a remote server. This is very useful if your users work remotely and need to access applications that are build around the client/server model. A good example of this would be an application that runs on a Windows PC and reads and writes to a Microsoft SQL Server database. The connection between the client App and the Database needs to be fast and reliable, such as a gigabit LAN, however the user works remotely. If a remote user tries to access the database over a Virtual Private Network (VPN) connection the experience is poor due to the limited bandwidth and there is a risk of database corruption.
One solution to this problem is to use Microsoft Remote Desktop Services. Microsoft Remote Desktop Services runs on Microsoft Windows Server and allows remote desktops and remote apps to be published to users. Microsoft Remote Desktop Services is a scalable solution which is architected around different Server roles within a Farm that work together to offer a solution for remote app delivery. Microsoft Remote Desktop Services is scalable meaning companies can add resources to servers such as memory and CPUs, this is scaling up, or by adding additional servers to the Farm, this is scaling out. The solution grows with your users and business demands.
In this deployment there are two Session Host Servers and two Connection Brokers. Clients connect to the Connection Brokers through a DNS Round Robin record and the connection is then brokered onto the RDS Session Host server that is the least utilised or if the user has an open session the users will be redirected back to it. This means that the Servers load balance inbound connections to optimise the user experience.
The following diagram helps us to visualise this.
The solution works well, except for two users that had installed Windows 11 update 22H2. The users would then, seemingly at random intervals, see the following hang.
After several attempts the connection would work. This was frustrating and caused the users a loss in productivity.
The solution is to disable UDP and only use TCP for RDS connections and this can be done by making a registry edit. This needs to be done on the Windows 11 22H2 PC with the issue, not the remote desktop server.
Open the Windows Registry Editor and go to the following tree:
HKEY_LOCAL_MACHINE \ SOFTWARE \ Policies \ Microsoft \ Windows NT \ Terminal Services \ Client
Look for fClientDisableUDP. If you can't find it, create a new DWORD entry and set its value to 1.
Restart your PC.
After this was done the users no longer experienced this issue.
Has this helped you ? we hope so.
iLogix Computer Solutions are Microsoft Certified. If you need our help please call us on 01252 962898.