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, they end up on a different RD Session Host.
In case there is an RDS Broker configured (Microsoft back end), the RDS host may refer the incoming request to the RDS broker instead.
When on the Microsoft Windows Server infrastructure there is an RD Connection Broker configured, Awingu should also connect through this RD Connection Broker (using an rdscollection label) rather than directly to the RD Session Host (using an appserver label).
Was this article helpful?
Tell us how we can improve it.