Skip to content

SHD and Application Delivery in Workgroup

HyWorks supports workgroup deployment but as workgroup environment does not have any centralized authentication mechanism and users exist locally on session host servers, specific configurations are required.

Session Host Server -- User Mapping

  1. In workgroup environment as users are not centrally managed thus user accounts must be created on all possible session host servers from where SHD sessions or application access is provided. This is done byg initiating user creation process in HyWorks as explained in Built-In Directory Server and Local User Management section. Also check Authentication Domain configuration details for Built-in user authentication.

  2. By aligning users with session teams HyWorks check whether user exist on target session host server or not.

  3. While publishing applications only session host servers are considered and thus it is not known if assigned users exist in session host server or not.

  4. On user logon, HyWorks checks whether the application that is published from the session host server is the member of session team to which user is added. While adding users from management console or using CSV administrator should specify specific session teams.

What does it mean:

In case a user account is not created on a session host server, but the user has access to an application published from that RDS server, the application will not be visible to the user.

HyWorks v3.0 or later supports mapping of user with session host server and application, where user will be displayed only those applications which are coming for session host server to which the user belongs. For example,

  • An organization has 4 session teams with each session team having 1 session host server

  • User1 belong to Team1 (SHS1) so the user account is created (synched) only with SHS1

  • App1 is published from all session host servers

  • App2 is available only on SHS1

  • App3 is available on SHS2, SHS3 and SHS4

  • User is assigned all applications; App1, App2 and App3

When User1 logs in, user will see icons for only App1 and App2, as User belongs to SHS1 and applications App1 and App2 are from SHS1. Also, when user1 will access App1, its session will only come from SHS1 not from SHS2, SHS3 or SHS4.