Skip to content

Connection Profile Management

Create a New Connection Profile

  1. Go to Configuration > Workspace > Connection Profile

  2. Click Add

  3. Choose From Template to create a profile by cloning a template or create a blank profile

  4. Provide all the required information and enable or disable all required settings in different sections

  5. Once all configurations are done, click Add Profile

The new profile will be added and Administrator can assign the new profile to devices from Device Settings dialog or using button Assign Profile in Endpoints

Edit Connection Profile

  1. Go to Connection Profiles

  2. Select the connection profile and click Edit

  3. Update the required configurations and click Update

Delete Connection Profile

  1. Go to Connection Profiles
  2. Select the connection profile and click Delete

  3. Click Delete and confirm.

Connection Profile will be deleted and will be removed from Connection Profile section in Setup

Note

  • Default Profile cannot be deleted.

  • On deletion, connection profile with any existing references will display appropriate error and will not get deleted until all the references are deleted completely.

Copy a Connection Profile

  1. Select a Connection Profile

  2. Choose Copy to clone a profile to create a new one.

  3. Provide name for new profile

New profile will be added and can be used

Reset a Connection Profile

In case connection profile is system generated or defined using pre-defined templates, the connection profiles can be reset to defaults. To reset a connection profile:

  1. Select connection profile (Default Profile -- System generated, or profiles created from system defined templates)

  2. Click Reset Profile and confirm

Selected profile will be reset to its defaults

Connection Profile Assignment and Fallback Model

In HyWorks v3.3, a connection profile can be assigned to multiple objects to have maximum granularity while providing application or desktop sessions to the clients. Following objects can be assigned with connection profile in respective sections:

  1. Endpoints:

    1. Default Settings: To all devices using default settings

    2. Group Settings: To a group of devices using Group settings

    3. Device Settings: To individual devices using Device Settings

  2. Entitlements:

    1. Users: To assign connection profile to different users, assignment can be done from Entitlements -> Users section

    2. User Groups: To assign connection profile to a group of users, Entitlements -> Groups section can be used

    3. OUs: To assign connection profile to an OU, Entitlements -> OUs section can be used

    4. Pools: User based shared hosted desktop pools can be assigned with specific connection profiles from Entitlements -> Pools section.

  3. Desktop Pools: To use any specific connection profile for a desktop pool, connection profile can be assigned to a desktop pool as well. Desktop pools can be assigned with connection profile from Add/Edit Desktop Pool wizard.

  4. Applications: Applications can also be assigned with specific connection profile while being added or being modified in Add Application or Edit Application wizard respectively.

Connection Profile Fallback Model

Connection Profile fallback model in HyWorks defines, the priority order in which connection profile can be applied. Connection profiles are used to define two types of attributes for a session:

  1. Session timeouts

  2. Connection parameters

Session timeouts are derived from connection profile applied to user, whereas connection attributes for application or desktop sessions are derived from connection profile applied to application session or desktop session.

Connection Profile priorities are calculated in the following manner based on the type of client from where user is logging-in:

Connection profile are used in following priority order:

User Session Application Session Desktop Session
Assigned to User Assigned to Application Assigned to Desktop Pool
Assigned to Group Assigned to User Assigned to User
Assigned to OU Assigned to Group Assigned to User Group
Assigned to Device (*Only when desktop client is being used to login) Assigned to OU Assigned to OU
Assigned to Device Group (**Only when desktop client is being used to login) Assigned to Device (**Only when desktop client is being used to login) Assigned to Device (*Only when desktop client is being used to access)
Organization Default Settings (For HyLite based logon) Assigned to Device Group (**Only when desktop client is being used to login) Organization Default Settings (For HyLite based access) Assigned to Device Group (**Only when desktop client is being used to login) Organization Default Connection Profile (For HyLite based access)

Let us try to understand this priority order using an example:

User-1 is member of group-2 and both are path of OU-3. User-1 is assigned with an application app-4 and desktop pool-5 and the connection profiles are assigned in following manner:

  1. User-1 -> Profile-1

  2. Group-2 -> Profile-2

  3. OU-3 -> Profile-3

  4. App-4 -> Profile-4

  5. Pool-5 -> Profile-5

Connection Profile Assignments and Precedence:

The connection profiles will be assigned to

  1. The user session and all remote session timeouts will be managed though connection profile assigned to user i.e. Profile-1 (as User is having highest priority), which means if profile-1 is having idle timeout as 5 minutes, then user sessions and remote sessions will be marked idle on inactivity of 5 minutes, though other connection profiles have some other timeouts defined for them.

  2. While accessing the application app-4, the applied connection profile on remote session will be Profile-4 as application is having higher precedence over user, but this won't change the user session connection profile which is already using Profile-1 and the session timeouts for app session will be used from the profile assigned to user session.

Important

​1. Connection Profile assigned to application takes precedence while setting up the remote session only when

1.  When Shell mode is enabled, the connection setting assigned to the application is used. 
If no connection is assigned to the application, then the connection profile assigned to the user will be used.

2.  In RemoteApp mode, the application session is the first from that session host server, else the remote app will use the         connection profile being assigned to first application.

3.  Now if the user accesses the desktop from the assigned pool, remote session environment will be decided by the user assigned connection profile (having the high precedence over pool) and the session timeouts for the remote session will also be defined from user assigned connection profile.

Connection Profile Assignment in Conflicting Situations

In following cases, conflicting situation occurs where the user is being assigned with two connection profiles.

  1. In case user is member of two groups and both groups are assigned with different connection profiles

Applied Connection Profile: In such cases, controller randomly

selects the connection profiles and assigns it to the user.

Connection Profile using Advance Configurations

Some Advance Configurations for connection profile. These are as follows.

  • Connection Profile Tab Control: Allow to perform Disabled Edit operation on connection profile tabs. Default value is False.

  • Disable Edit On Connection Profile Tabs: Disables Edit operation on Connection Profile Tabs for all users (except Super Admin Role). Tab number needs to be entered with comma separated. Default value is 2.

    1. This configuration depend upon Connection Profile Tab Control.

    2. If Connection Profile Tab Control set as a true than this configuration will work other wise not.

    3. For example 2,5 - It means tab number 2 which is Experience Tab and tab number 5 which is Advanced Settings

​ got disabled while editing connection profile.

Advance Configurations

Advance configurations available on HyWorks Controller Management Console -> Host Management > System > Advance Config

  • UI Control: Connection Profile related configurations available in UI Control Group.