User ends up on different RDS host than the one specified for the application in Awingu

0 users found this article helpful

Symptoms

When a user launches an application session, they do not end up on the Remote Desktop Services (RDS) host that is configured in the application's settings in Awingu.

Instead, the end up on a different RDS host.

Cause

In case there is an RDS Broker configured, the RDS host may refer the incoming request to the RDS broker instead.

Resolution

On the Microsoft Windows RDS host:

Apply this group policy:

Computer Configuration / Administrative Templates / Windows Components / Remote Desktop Services / Remote Desktop Session Host / Use RD Connection Broker Load Balancing: set to disabled.

If setting the group policy doesn't resolve the issue, check this registry key.
It should be set to disabled.

Registry Hive HKEY_LOCAL_MACHINE
Registry Path SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services
Value Name ParticipateInLoadBalancing
Value Type REG_DWORD
Enabled Value 1
Disabled Value 0

Was this article helpful?

Tell us how we can improve it.