Session experience

Application launch time

Use the session prelaunch feature to reduce application launch time during normal or high traffic periods, thus providing users with a better experience. The prelaunch feature allows to create a prelaunch session. Prelaunch session is created when a user logs on to Citrix Workspace app, or at a scheduled time if the user has signed in.

The prelaunch session reduces the launch time of the first application. When a user adds new account connection to Citrix Workspace app for Windows, session prelaunch doesn’t take effect until the next session. The default application ctxprelaunch.exe is running in the session, but it is not visible to you.

For more information, see session prelaunch and session linger guidance in the Citrix Virtual Apps and Desktops article titled Manage delivery groups.

Session prelaunch is disabled by default. To enable session prelaunch, specify the ENABLEPRELAUNCH=true parameter on the Workspace command line or set the EnablePreLaunch registry key to true. The default setting, null, means that prelaunch is disabled.

Note:

If the client machine has been configured to support Domain Passthrough (SSON) authentication, prelaunch is automatically enabled. If you want to use Domain Pass-through (SSON) without prelaunch, set the EnablePreLaunch registry key value to false.

The registry locations are:

• HKEY_LOCAL_MACHINE\Software\[Wow6432Node\]Citrix\\Dazzle

• HKEY_CURRENT_USER\Software\Citrix\Dazzle

There are two types of prelaunch:

• Just-in-time prelaunch- prelaunch starts immediately after the user’s credentials are authenticated whether it is a high-traffic period. Typically used for normal traffic periods. A user can trigger just-in-time prelaunch by restarting the Citrix Workspace app.
• Scheduled prelaunch- prelaunch starts at a scheduled time. Scheduled prelaunch starts only when the user device is already running and authenticated. If those two conditions are not met when the scheduled prelaunch time arrives, a session does not launch. To share network and server load, the session launches within a window when it is scheduled. For example, if the scheduled prelaunch is scheduled for 13:45, the session actually launches between 13:15 and 13:45. Typically used for high-traffic periods.

Configuring prelaunch on a Citrix Virtual Apps server consists of:

• creating, modifying, or deleting prelaunch applications, and
• updating user policy settings that control the prelaunch application.

You cannot customize the prelaunch feature using the receiver.admx file. However, you can change the prelaunch configuration by modifying registry values. Registry values can be modified during or after Citrix Workspace app for Windows installation.

• The HKEY_LOCAL_MACHINE values are written during client installation.
• The HKEY_CURRENT_USER values enable you to provide different users on the same machine with different settings. Users can change the HKEY_CURRENT_USER values without administrative permission. You can provide your users with scripts to change the values.

HKEY_LOCAL_MACHINE registry values:

For 64-bit Windows operating systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client\Prelaunch

For 32-bit Windows operating systems: HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client\Prelaunch

Name: UserOverride Type: REG_DWORD

Values:

0 - Use the HKEY_LOCAL_MACHINE values even if HKEY_CURRENT_USER values are also present.

1 - Use the HKEY_CURRENT_USER values if they exist; otherwise, use the HKEY_LOCAL_MACHINE values.

Name: State Type: REG_DWORD

Values:

0 - Disable prelaunch.

1 - Enable just-in-time prelaunch. (prelaunch starts after the user’s credentials are authenticated.)

2 - Enable scheduled prelaunch. (prelaunch starts at the time configured for Schedule.)

Name: Schedule Type: REG_DWORD

Value:

The time (24-hour format) and days of a week for the scheduled prelaunch entered in the following format:

HKEY_CURRENT_USER registry values:

HKEY_CURRENT_USER\SOFTWARE\Citrix\ICA Client\Prelaunch

The State and Schedule keys have the same values as for HKEY_LOCAL_MACHINE.

Desktop Viewer

Different enterprises might have different corporate needs. Your requirements for the way users access virtual desktops might vary from user to user and as your corporate needs evolve. The user experience of connecting to virtual desktops and the extent at which the user can configure the connections depend Citrix Workspace app for Windows setup.

Use the desktop viewer when users need to interact with their virtual desktop. The user’s virtual desktop can be a published virtual desktop, or a shared or dedicated desktop. In this access scenario, the Desktop Viewer toolbar functionality allows the user to open a virtual desktop in a window and pan and scale that desktop inside their local desktop. Users can set preferences and work on more than one desktop using multiple Citrix Virtual Apps and Desktops and Citrix DaaS connections on the same user device.

Note:

Use Citrix Workspace app to change the screen resolution on their virtual desktops. You can’t change Screen Resolution using the Windows Control Panel.

Keyboard input in Desktop Viewer

In Desktop Viewer sessions, the Windows logo key+L is directed to the local computer.

Ctrl+Alt+Delete is directed to the local computer.

Key presses that activate certain Microsoft accessibility features, for example, Sticky Keys, Filter Keys, and Toggle Keys are normally directed to the local computer.

As an accessibility feature of the Desktop Viewer, pressing Ctrl+Alt+Break displays the Desktop Viewer toolbar buttons in a pop-up window.

Ctrl+Esc is sent to the remote, virtual desktop.

Note:

By default, if the Desktop Viewer is maximized, Alt+Tab switches focus between windows inside the session. If the Desktop Viewer is displayed in a window, Alt+Tab switches focus between windows outside the session.

Hotkey sequences are key combinations designed by Citrix. Hotkey sequences are, for example, the Ctrl+F1 sequence reproduces Ctrl+Alt+Delete, and Shift+F2 switches applications between full-screen and windowed mode.

Note:

You can’t use hotkey sequences with virtual desktops displayed in the Desktop Viewer, that is, with virtual apps and desktops sessions. However, you can use them with published applications, that is, with virtual apps sessions.

Prevent the desktop viewer window from dimming

If you have multiple Desktop Viewer windows, by default the desktops that are not active are dimmed. If users want to view multiple desktops simultaneously, information on them might be unreadable. You can disable the default behavior and prevent the Desktop Viewer window from dimming by editing the Registry editor.

Caution

Editing the registry incorrectly can cause serious problems that might require you to reinstall your Operating system. Citrix cannot guarantee that problems resulting from the incorrect use of the Registry Editor can be solved. Use the Registry Editor at your own risk. Be sure to back up the registry before you edit it

• On the user device, create a REG_DWORD entry called DisableDimming in one of the following keys, depending on whether you want to prevent dimming for the current user of the device or the device itself. An entry exists if the Desktop Viewer has been used on the device:

  • HKEY_CURRENT_USER\Software\Citrix\XenDesktop\DesktopViewer
  • HKEY_LOCAL_MACHINE\Software\Citrix\XenDesktop\DesktopViewer

Optionally, instead of controlling dimming, you can define a local policy by creating the same REG_WORD entry in one of the following keys:

• HKEY_CURRENT_USER\Software\Policies\Citrix\XenDesktop\DesktopViewer
• HKEY_LOCAL_MACHINE\Software\Policies\Citrix\XenDesktop\DesktopViewer

Before using these keys, check whether the Citrix Virtual Apps and Desktops and Citrix DaaS administrator has set a policy for this feature.

Set the entry to any non-zero value such as 1 or true.

If no entries are specified or the entry is set to 0, the Desktop Viewer window is dimmed. If multiple entries are specified, the following precedence is used. The first entry in this list and its value determine whether the window is dimmed:

1. HKEY_CURRENT_USER\Software\Policies\Citrix\…
2. HKEY_LOCAL_MACHINE\Software\Policies\Citrix\…
3. HKEY_CURRENT_USER\Software\Citrix\…
4. HKEY_LOCAL_MACHINE\Software\Citrix\…

Status indicator time-out

You can change the amount of time the status indicator displays when a user is launching a session.

To alter the time-out period, do the following steps:

1. Launch the Registry Editor.
2. Navigate to the following path:
   • On a 64-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA CLIENT\Engine
   • On a 32-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA CLIENT\Engine\
3. Create a registry key as follows:
   • Type: REG_DWORD
   • Name: SI INACTIVE MS
   • Value: 4, if you want the status indicator to disappear sooner.

When you configure this key, the status indicator might appear and disappear frequently. This behavior is as designed. To suppress the status indicator, do the following:

1. Launch the Registry Editor.
2. Navigate to the following path:
   • On a 64-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA CLIENT\
   • On a 32-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA CLIENT\

3. Create a registry key as follows:

   • Type: REG_DWORD
   • Name: NotificationDelay
   • Value: Any value in millisecond (for example, 120000)

Improved virtual apps and desktops reconnection experience

Citrix Workspace 2302 release provides an enhanced user experience while reconnecting to virtual apps and desktops from which you got disconnected.

When Citrix Workspace app attempts to refresh the disconnected Citrix Workspace app or start new virtual apps or desktops as a part of the Workspace Control feature, the following prompt appears:

Click Restore to reconnect to open new and disconnected virtual apps and desktops. If you want to start only newly selected apps and desktops, click Cancel.

You can also select Remember my preference to apply the selected preference for the next login. To reset your selected preferences, you must reset Citrix Workspace app.

The preceding new Restore session? prompt appears only if:

• the user tries to start an app belonging to a workspace store,
• admin policies or app config settings are not configured for the Workspace Control feature,
• Workspace Control Reconnect options are set to default on the client.

Note:

Reconnect settings in the Reconnect Options takes precedence over the preferences set in the dialog box. For more information, see Configure reconnect options using Advanced Preferences dialog.

Sustainability initiative from Citrix Workspace app

For native launch

From Citrix Workspace app 2309 version onwards, when this feature is enabled, a prompt is displayed to sign out from the desktop session when a user closes a virtual desktop. This feature might help conserve energy if there are Windows OS policies that are used to shutdown VMs when no users are logged in.

To enable this feature, do the following:

1. Navigate to Citrix Studio.
2. Click Delivery Groups from the left navigation pane.
3. Select the required VDA from the Delivery Group section.
4. Click the Edit icon. The Edit Delivery Group page appears.
5. Click Desktops from the left navigation pane.
6. Select the required VDA where you must add the keywords.
7. Click Edit. The Edit Desktop page appears.
8. Set the LogoffOnClose keyword to true in the Description field.

9. Click OK. The following dialog box appears when you close the virtual desktop:

   

Customizing the text in the Save energy screen

You can also customize the text in the Save energy screen.

1. Follow steps 1–8 in the preceding section.

2. Set the PromptMessage keyword to the required text in the Description field.

   Example:

   KEYWORDS:LogoffOnClose=true PromptMessage="Do you want to Log off?"
   <!--NeedCopy-->
   

   

   The keywords are assigned by default for new desktop machines assigned to the group. For existing desktop machines, you must run the following powershell commands for changes to apply:

   $dg = Get-BrokerDesktopGroup -Name '<group name>' -Property 'Name','Uid'
   
   $apr = @( Get-BrokerAssignmentPolicyRule -DesktopGroupUid $dg.Uid -Property 'Description' )
   
   Get-BrokerMachine -DesktopGroupUid $dg.Uid -IsAssigned $true | Set-BrokerMachine -Description $apr[0].Description
   <!--NeedCopy-->
   

   With this PowerShell script, it is possible to have multiple assignment policy rules for a single Delivery Group. Using Citrix Studio also, you can configure multiple Assignment policy rules, each with unique description value and possible set of different keywords.

3. Click OK. The following dialog box appears when you close the virtual desktop.

   

For hybrid cloud launch

To enable this feature, do the following:

1. Navigate to Citrix Studio.
2. Click Delivery Groups from the left navigation pane.
3. Select the required VDA from the Delivery Group section.
4. Click the Edit icon. The Edit Delivery Group page appears.
5. Click Desktops from the left navigation pane.
6. Select the required VDA where you must add the keywords.
7. Click Edit. The Edit Desktop page appears.
8. Set the ICA-LogOffOnClose keyword to true in the Description field.

9. Click OK. The following dialog box appears when you close the virtual desktop:

   

Customize the text on the Save energy screen

You can also customize the text that appears on the Save energy screen.

1. Follow steps 1–8 in the preceding section.

2. Set the ICA-PromptMessage keyword to the required text in the Description field.

   Note:

   The maximum number of characters allowed in the Description field is 200.

   Example:

   KEYWORDS:ICA-LogOffOnClose=true ICA-PromptMessage="Do you want to Log off?"
   <!--NeedCopy-->
   

   

   The keywords are assigned by default for new desktop machines assigned to the group. For existing desktop machines, you must run the following PowerShell commands for changes to apply:

   $dg = Get-BrokerDesktopGroup -Name '<group name>' -Property 'Name','Uid'
   
   $apr = @( Get-BrokerAssignmentPolicyRule -DesktopGroupUid $dg.Uid -Property 'Description' )
   
   Get-BrokerMachine -DesktopGroupUid $dg.Uid -IsAssigned $true | Set-BrokerMachine -Description $apr[0].Description
   <!--NeedCopy-->
   

   With this PowerShell script, it’s possible to have multiple assignment policy rules for a single Delivery Group. Using Citrix Studio also, you can configure multiple Assignment policy rules, each with a unique description value, and a possible set of different keywords.

3. Click OK. The following dialog box appears when you close the virtual desktop.

   

Manage workspace control reconnect

Workspace control lets applications follow users as they move between devices. For example, workspace control enables clinicians in hospitals to move from workstation to workstation without having to restart their applications on each device. For Citrix Workspace app, you manage workspace control on client devices using the Global App Config Service, Group Policy or modifying the registry.

Caution:

Editing the registry incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix can’t guarantee that problems resulting from the incorrect use of the Registry Editor can be solved. Use the Registry Editor at your own risk. Be sure to back up the registry before you edit it.

Create WSCReconnectModeUser and modify the existing registry key WSCReconnectMode in the Master Desktop Image or in the Citrix Virtual Apps server. The published desktop can change the behavior of the Citrix Workspace app.

WSCReconnectMode key settings for Citrix Workspace app:

• 0 = do not reconnect to any existing sessions
• 1 = reconnect on application launch
• 2 = reconnect on application refresh
• 3 = reconnect on application launch or refresh
• 4 = reconnect when Citrix Workspace interface opens
• 8 = reconnect on Windows sign-on
• 11 = combination of both 3 and 8

Disable workspace control

To disable workspace control, create the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle (64-bit)

HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\\Dazzle (32-bit)

Name: WSCReconnectModeUser

Type: REG_SZ

Value data: 0

Modify the following key from the default value of 3 to zero

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle (64-bit)

HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Dazzle (32-bit)

Name: WSCReconnectMode

Type: REG_SZ

Value data: 0

Note:

You can also set the WSCReconnectAll key to false if you don’t want to create a key.

Registry keys for 32-bit machines

Registry key: WSCSupported

Value: True

Key path:

-  HKEY_CURRENT_USER\Software\Citrix\Dazzle
-  HKEY_CURRENT_USER\Software\Citrix\Receiver\SR\Store" + primaryStoreID +\Properties
-  HKEY_LOCAL_MACHINE\Software\Policies\Citrix\Dazzle
-  HKEY_LOCAL_MACHINE\Software\Citrix\Dazzle

Registry key: WSCReconnectAll

Value: True

Key path:

- `HKEY_CURRENT_USER\Software\Citrix\Dazzle`
- `HKEY_CURRENT_USER\Software\Citrix\Receiver\SR\Store" + primaryStoreID + \Properties`
- `HKEY_LOCAL_MACHINE\Software\Policies\Citrix\Dazzle`
- `HKEY_LOCAL_MACHINe\Software\Citrix\Dazzle`

Registry key: WSCReconnectMode

Value: 3

Key path:

-  HKEY_CURRENT_USER\Software\Citrix\Dazzle
-  HKEY_CURRENT_USER\Software\Citrix\Receiver\SR\Store" + primaryStoreID +\Properties
-  HKEY_LOCAL_MACHINE\Software\Policies\Citrix\Dazzle
-  HKEY_LOCAL_MACHINE\Software\Citrix\Dazzle

Registry key: WSCReconnectModeUser

Value: The registry isn’t created during installation.

Key path:

- HKEY_CURRENT_USER\Software\Citrix\Dazzle
- HKEY_CURRENT_USER\Software\Citrix\Receiver\SR\Store" + primaryStoreID+\Properties
- HKEY_LOCAL_MACHINE\Software\Policies\Citrix\Dazzle
- HKEY_LOCAL_MACHINE\Software\Citrix\Dazzle

Registry keys for 64-bit machines

Registry key: WSCSupported

Value: True

Key path:

- HKEY_CURRENT_USER\Software\Citrix\Dazzle
- HKEY_CURRENT_USER\Software\Citrix\Receiver\SR\Store" + primaryStoreID +\Properties
- HKEY_LOCAL_MACHINE\Software\Wow6432Node\Policies\Citrix\Dazzle
- HKEY_LOCAL_MACHINE\Software\Wow6432Node\Citrix\Dazzle

Registry key: WSCReconnectAll

Value: True

Key path:

-  HKEY_CURRENT_USER\Software\Citrix\Dazzle
-  HKEY_CURRENT_USER\Software\Citrix\Receiver\SR\Store" + primaryStoreID + \Properties
-  HKEY_LOCAL_MACHINE\Software\Wow6432Node\Policies\Citrix\Dazzle
-  HKEY_LOCAL_MACHINE\Software\Wow6432Node\Citrix\Dazzle

Registry key: WSCReconnectMode

Value: 3

Key path:

-  HKEY_CURRENT_USER\Software\Citrix\Dazzle
-  HKEY_CURRENT_USER\Software\Citrix\Receiver\SR\Store" + primaryStoreID +\Properties
-  HKEY_LOCAL_MACHINE\Software\Wow6432Node\Policies\Citrix\Dazzle
-  HKEY_LOCAL_MACHINE\Software\Wow6432Node\Citrix\Dazzle

Registry key: WSCReconnectModeUser

Value: The registry isn’t created during installation.

Key path:

- HKEY_CURRENT_USER\Software\Citrix\Dazzle
- HKEY_CURRENT_USER\Software\Citrix\Receiver\SR\Store" + primaryStoreID+\Properties
- HKEY_LOCAL_MACHINE\Software\Wow6432Node\Policies\Citrix\Dazzle
- HKEY_LOCAL_MACHINE\Software\Wow6432Node\Citrix\Dazzle