Improving the user experience
You can improve your users’ experience with the following supported features:
You can set preferences by clicking Preferences on the Citrix Receiver menu. You can control how desktops are displayed, connect to different applications and desktops, and manage file and device access.
To manage an account
To access desktops and applications, you need an account with XenDeskop or XenApp. Your IT help desk might ask you to add an account to Citrix Receiver for this purpose. Or they might ask you to use a different NetScaler Gateway or Access Gateway server for an existing account. You can also remove accounts from Citrix Receiver.
- On the Accounts page of the Preferences dialog box, do one of the following:
- To add an account, click Add. Your help desk may alternatively provide a provisioning file with account information that you can use to create an account.
- To change details of a store that the account uses, such as the default gateway, click Edit.
- To remove an account, click Remove.
- Follow the on-screen prompts. You may be required to authenticate to the server.
To change how you see your desktops
This feature is not available with Citrix XenApp for UNIX sessions.
You can display desktops across the entire screen on your user device (full screen mode), which is the default, or in a separate window (windowed mode).
- On the General page of the Preferences dialog box, select a mode using the “Display desktop in” option.
Receiver for Linux now has the You can enable Desktop Viewer toolbar functionality so it is possible dynamically modify the window configuration of your remote session from the original settings specified by the configuration mentioned here.
Different enterprises have different corporate needs. Your requirements for the way users access virtual desktops may vary from user to user and may vary as your corporate needs evolve. The user experience of connecting to virtual desktops and the extent of user involvement in configuring the connections depend on how you set up Receiver for Linux.
Use the Desktop Viewer when users 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 switch a session between windowed and full-screen session window, including multi-monitor support for the intersected monitors. Users can switch between desktop sessions and work with more than one desktop using multiple XenDesktop connections on the same user device. Buttons to minimize all desktop sessions, send the Ctrl+Alt+Del sequence, disconnect, and log off the session are provided to manage a user’s session conveniently.
As an accessibility feature of the Desktop Viewer, pressing Ctrl+Alt+Break displays the Desktop Viewer toolbar buttons in a pop-up window.
See the Linux OEM guide for advanced configuration entries to enable or disable Desktop Viewer or change the accessibility key sequence.
To reconnect sessions automatically
Citrix Receiver can reconnect to desktops and applications that you become disconnected from (for example, if there is a network infrastructure issue):
- On the General page of the Preferences dialog box, select an option in Reconnect apps and desktops.
To control how local files are accessed
A virtual desktop or application may need to access files on your device. You can control the extent to which this happens.
- On the File Access page of the Preferences dialog box, select a mapped drive and then one of the following options:
- Read and write - Allow the desktop or application to read and write to local files.
- Read only - Allow the desktop or application to read but not write to local files.
- No access - Do not allow the desktop or application to access local files.
- Ask me each time - Display a prompt each time the desktop or application needs to access local files.
- If you selected one of the options that grants access to local files, you can additionally save time when browsing to locations on your user device. Click Add, specify the location, and select a drive to map to it.
To set up a microphone or webcam
You can change the way a virtual desktop or application accesses your local microphone or webcam:
On the Mic & Webcam page of the Preferences dialog box, select one of the following options:
- Use my microphone and webcam - Allow the microphone and webcam to be used by the desktop or application.
- Don’t use my microphone or webcam - Do not allow the microphone or webcam to be used by the desktop or application.
To set up Flash Player
You can choose how Flash content is displayed. This content is normally displayed in Flash Player and includes video, animation, and applications:
On the Flash page of the Preferences dialog box, select one of the following options:
- Optimize content - Improve playback quality at the risk of reducing security.
- Don’t optimize content - Provide basic playback quality without reducing security.
- Ask me each time - Prompt me each time Flash content is displayed.
Configuring ClearType font smoothing
ClearType font smoothing (also known as subpixel font rendering) improves the quality of displayed fonts beyond that available through traditional font smoothing or anti-aliasing. You can turn this feature on or off. Or you specify the type of smoothing by editing the following setting in [WFClient] section of the appropriate configuration file:
FontSmoothingType = number
where number can take one of the following values:
|0||The local preference on the device is used. This value is defined by the FontSmoothingTypePref setting.|
|3||ClearType (horizontal subpixel) smoothing|
Both standard smoothing and ClearType smoothing can increase Receiver’s bandwidth requirements.
Important: The server can configure FontSmoothingType through the ICA file. This takes precedence over the value set in [WFClient]. If the server sets the value to 0, the local preference is determined by another setting in the [WFClient]:
FontSmoothingTypePref = number
where number can take one of the following values:
|3||ClearType (horizontal subpixel) smoothing (default)|
Configuring special folder redirection
In this context, there are only two special folders for each user:
- The user’s Desktop folder
- The user’s Documents folder (My Documents on Windows XP)
Special folder redirection enables you to specify the locations of a user’s special folders so that these remain fixed across different server types and server farm configurations. It is important if, for example, a mobile user logs on to servers in different server farms. For static, desk-based workstations, where the user can log on to servers that reside in a single server farm, special folder redirection is rarely necessary.
To configure special folder redirection
A two-part procedure is as follows. First, you enable special folder redirection by making an entry in module.ini; then you specify the folder locations in the [WFClient] section, as described here:
Add the following text to module.ini (for example, $ICAROOT/config/module.ini):
SFRAllowed = True
Add the following text to the [WFClient] section (for example, $HOME/.ICAClient/wfclient.ini):
DocumentsFolder = documents
DesktopFolder = desktop
where documents and desktop are the UNIX filenames, including the full path, of the directories to use as the users Documents and Desktop folders respectively. For example:
DesktopFolder = $HOME/.ICAClient/desktop
- You can specify any component in the path as an environment variable, for example, $HOME.
- Specify values for both parameters.
- The directories you specify must be available through client device mapping. That is, the directory must be in the subtree of a mapped client device.
- Use the drive letters C or higher.
Setting up server-client content redirection
Server-client content redirection enables administrators to specify that URLs in a published application are opened using a local application. For example, opening a link to a webpage while using Microsoft Outlook in a session opens the required file using the browser on the user device. Server-client content redirection enables administrators to allocate Citrix resources more efficiently, thereby providing users with better performance.
The following types of URL can be redirected:
- HTTP (Hypertext Transfer Protocol)
- HTTPS (Secure Hypertext Transfer Protocol)
- RTSP (Real Player)
- RTSPU (Real Player)
- PNM (Older Real Players)
If Citrix Receiver does not have an appropriate application or cannot directly access the content, the URL is opened using the server application.
Server-client content redirection is configured on the server and enabled by default in Citrix Receiver if the path includes RealPlayer and at least one of Firefox, Mozilla, or Netscape.
For more information about RealPlayer for Linux, see http://www.real.com/resources/unix/.
To enable server-client content redirection if RealPlayer and a browser are not in the path
Open the configuration file wfclient.ini.
In the [Browser] section, modify the following settings:
where path is the directory where the browser executable is located and command is the name of the executable used to handle redirected browser URLs, appended with the URL sent by the server. For example:
This setting specifies the following:
- The nslaunch utility is run to push the URL into an existing browser window
- Each browser in the list is tried in turn until content can be displayed successfully
In the [Player] section, modify the following settings:
where path is the directory where the RealPlayer executable is located and command is the name of the executable used to handle the redirected multimedia URLs, appended with the URL sent by the server.
Save and close the file.
For both Path settings, you need only specify the directory where the browser and RealPlayer executables reside. You do not need to specify the full path to the executables. For example, in the [Browser] section, Path might be set to /usr/X11R6/bin rather than /usr/X11R6/bin/netscape. In addition, you can specify multiple directory names as a colon-separated list. If these settings are not specified, the user’s current $PATH is used.
To turn off server-client content redirection from Receiver
- Open the configuration file module.ini.
- Change the CREnabled setting to Off.
- Save and close the file.
Controlling keyboard behavior
To generate a remote Ctrl+Alt+Delete key combination:
- Decide which key combination creates the Ctrl+Alt+Delete combination on the remote virtual desktop.
- In the WFClient section of the appropriate configuration file, configure UseCtrlAltEnd accordingly:
- True means that Ctrl+Alt+End passes the Ctrl+Alt+Delete combination to the remote desktop.
- False (default) means that Ctrl+Alt+Enter passes the Ctrl+Alt+Delete combination to the remote desktop.
The Citrix Receiver package includes a helper application, xcapture, to assist with the exchange of graphical data between the server clipboard and non-ICCCM-compliant X Windows applications on the X desktop. Users can use xcapture to:
- Capture dialog boxes or screen areas and copy them between the user device desktop (including non-ICCCM-compliant applications) and an application running in a connection window
- Copy graphics between a connection window and X graphics manipulation utilities xmag or xv
To start xcapture from the command line
At the command prompt, type /opt/Citrix/ICAClient/util/xcapture and press ENTER (where /opt/Citrix/ICAClient is the directory in which you installed Receiver).
To copy from the user device desktop
- From the xcapture dialog box, click From Screen. The cursor changes to a crosshair.
- Choose from the following tasks:
- Select a window. Move the cursor over the window you want to copy and click the middle mouse button.
- Select a region. Hold down the left mouse button and drag the cursor to select the area you want to copy.
- Cancel the selection. Click the right mouse button. While dragging, you can cancel the selection by clicking the right button before releasing the middle or left mouse button.
- From the xcapture dialog box, click To ICA. The xcapture button changes color to show that it is processing the information.
- When the transfer is complete, use the appropriate paste command in an application launched from the connection window.
To copy from xv to an application in a connection window
- From xv, copy the information.
- From the xcapture dialog box, click From XV and then click To ICA. The xcapture button changes color to show that it is processing the information.
- When the transfer is complete, use the appropriate paste command in an application launched from the connection window.
To copy from an application in the connection window to xv
- From the application in a connection window, copy the information.
- From the xcapture dialog box, click From ICA and then click To XV. The xcapture button changes color to show that it is processing the information.
- When the transfer is complete, paste the information into xv.
Reconnecting users automatically
This topic describes the HDX Broadcast auto-client reconnection feature. Citrix recommends that you use this feature with the HDX Broadcast session reliability feature.
Users can be disconnected from their sessions because of unreliable networks, highly variable network latency, or range limitations of wireless devices. With the HDX Broadcast auto-client reconnection feature, Citrix Receiver can detect unintended disconnections of sessions and reconnect users to the affected sessions automatically.
When this feature is enabled on the server, users do not have to reconnect manually to continue working. Citrix Receiver attempts to reconnect to the session a set number of times until there is a successful reconnection or the user cancels the reconnection attempts. If user authentication is required, a dialog box requesting credentials appears to a user during automatic reconnection. Automatic reconnection does not occur if users exit applications without logging off. Users can reconnect only to disconnected sessions.
By default, Citrix Receiver waits 30 seconds before attempting to reconnect to a disconnected session and attempts to reconnect to that session three times.
When connecting through an AccessGateway, ACR is not available. To protect against network dropouts, ensure that Session Reliability is enabled both on the Server and Client, as well as configured on the AccessGateway.
For instructions on configuring HDX Broadcast auto-client reconnection, see your XenApp and XenDesktop documentation.
Ensure session reliability
This topic describes the HDX Broadcast session reliability feature, which is enabled by default.
With HDX Broadcast session reliability, users continue to see a published application’s window if the connection to the application experiences an interruption. For example, wireless users entering a tunnel may lose their connection when they enter the tunnel and regain it when they emerge on the other side. During the downtime, all of the user’s data, key presses, and other interactions are stored, and the application appears frozen. When the connection is re-established, these interactions are replayed into the application.
When auto-client reconnection and session reliability are configured, session reliability takes precedence if there is a connection problem. Session reliability attempts to re-establish a connection to the existing session. It might take up to 25 seconds to detect a connection problem. And then takes a configurable period (the default is 180 seconds) to attempt the reconnection. If session reliability fails to reconnect, then auto-client reconnect attempts to reconnect.
If HDX Broadcast session reliability is enabled, the default port used for session communication switches from 1494 to 2598.
Citrix Receiver users cannot override the server settings. For more information, see the XenApp and XenDesktop documentation.
HDX Broadcast session reliability requires that another feature, Common Gateway Protocol, is enabled (using policy settings) on the server. Disabling Common Gateway Protocol also disables HDX Broadcast session reliability.
Relative Mouse support provides an option to interpret the mouse position in a relative rather than absolute manner. This capability is required for applications that demand relative mouse input rather than absolute.
This feature is available only in sessions running on XenApp or XenDesktop 7.8 (or later). It is disabled by default.
To enable the feature:
In the file $HOME/.ICAClient/wfclient.ini, in the section [WFClient], add the entry RelativeMouse=1.
This step enables the feature but keeps it inactive until you activate it.
Refer to the section Alternative Relative Mouse values for additional information about enabling relative mouse features.
To activate the feature:
After the feature is enabled, type Ctrl/F12 again to synchronize the server pointer position with the client. The server and client pointer positions are not synchronized when using Relative Mouse.
To deactivate the feature:
The feature is also switched off when a session window loses focus.
Alternative Relative Mouse values
Alternatively, consider using the following values for RelativeMouse:
- RelativeMouse=2 Enables the feature and activates it whenever a session window gains focus.
- RelativeMouse=3 Enables, activates, and keeps the feature activated always.
- RelativeMouse=4 Enables or disables the feature when the client-side mouse pointer is hidden or shown. This mode is suitable for automatically enabling or disabling relative mouse for first-person gaming-style application interfaces.
To change the keyboard commands, add settings like:
The supported values for RelativemouseOnChar and RelativemouseOffChar are listed under [Hotkey Keys] in the config/module.ini file in the Citrix Receiver installation tree. The values for RelativeMouseOnShift and RelativeMouseOffShift set the modifier keys to be used and are listed under the [Hotkey Shift States] heading.