I have an rds farm with three rds_host servers. I have defined three domain user groups for sage_sales, sage_admin and sage_outside.
I have three collections pointing to the three rds host servers; sage_sales, sage_admin and sage_outside.
In my tests:
When I setup a user Joe in the Domain user manager, and make him a member of the sage_admin group, he can log into the RDWEB portal by entering his domain.user/password and clicking sign in. He is presented with the collection icon as shown below.
![]()
Clicking on the Sage_Admin icon takes the user to a successful remote session on the correct rds host configured for sage_admin users.
When my test user Joe is a member of two groups (sales_group and admin_group), he is presented with two collection icons after signing into the rdweb portal as shown below:
![]()
However Joe can only connect using the Sage_Admin icon. When clicking the Sage_Sales icon, the following error dialog is displayed.
![]()
What is happening here? I can't find any difference in the group rights.
Does the Set Primary Group in the Domain User settings effect which icons are available in an rdweb session?
Comments on these configuration options would help. What a battle!!