Citrix Desktop Receiver Embedded Edition Release Note

Citrix states:

Citrix Desktop Receiver Embedded Edition Release Note

Document ID: CTX116539   /   Created On: May 19, 2008   /   Updated On: Jun 12, 2008
Average Rating: not yet rated

productFamilyKey3 = "xd"; topics3 = ""; productFamilyKey = productFamilyKey3.replace("/","--") + "/"; topics = topics3.replace("/","--") + "/";

Citrix Desktop Receiver Embedded Edition

Release Note

Contents

Overview of this Release

This document describes version 10.250 of the Citrix Desktop Receiver Embedded Edition, the client package that supports the Citrix XenDesktop product in addition to the Citrix XenApp product. This client package is based on and extends version 10.200 of the Citrix Presentation Server Clients for Windows.

This document is intended for system administrators and describes the system requirements, installation instructions, the new features of the client, how to use those features, and known issues.

If you are installing the clients as part of a XenDesktop deployment, note that the software contained in this release is available on the installation media for Desktop Delivery Controller for XenDesktop. Remember to visit the download Web site to check for the latest client releases.

This release includes new features designed for connections to virtual desktops created with Desktop Delivery Controller. This document focuses on those features.

The Citrix Desktop Receiver Embedded Edition includes the following clients:

  • Program Neighborhood Agent
  • The Web Client

Program Neighborhood, another client included in previous versions of the Citrix Presentation Server Clients for Windows, is also included in the release but does not support virtual desktop connections.

When used to access virtual desktops, Program Neighborhood Agent and the Web Client differ in terms of:

  • The access method by which virtual desktops are delivered to users
  • The extent of user involvement in configuring, administering, and managing the clients
  • Support for the Desktop Delivery Controller feature set

Users view and control the desktops either in full-screen-only mode or using a new user interface, the Citrix Desktop Toolbar. To decide which of these options best suits your deployment and to understand the user experience of connecting to desktops created with Desktop Delivery Controller, read the chapter called "Planning the User Experience" in the Desktop Delivery Controller Administrator's Guide.

System Requirements

  • Standard PC architecture, as required for the operating system.
  • 64-bit or 32-bit editions of the following operating systems: Windows Vista, Windows XP Professional (Service Pack 2 or later for 32-bit edition), Windows XP Embedded, Windows Server 2003, and Windows 2000 Professional (latest Service Pack).
  • Supported operating systems vary by feature:
    • Desktops running in full-screen-only mode are supported on Windows XP Professional (except the 64-bit edition) and Windows XP Embedded on domain-joined endpoints.
    • The Citrix Desktop Toolbar feature is supported on Windows Vista, Windows XP Professional, Windows XP Embedded, Windows 2000 Professional, and Windows Server 2003.
  • Available memory as recommended for the operating system by Microsoft.
  • Internet Explorer Version 6.0 or 7.0; Mozilla Firefox 2.0. On the 64-bit editions of Windows XP Professional and Windows Vista running Internet Explorer, the Web Client is supported only when Internet Explorer is running in 32-bit mode.
  • Microsoft mouse or 100% compatible mouse.
  • VGA or SVGA video adapter with color monitor.
  • Windows-compatible sound card for sound support (optional).
  • For network connections to a server farm, a network interface card (NIC) and the appropriate network transport software are required.

Supported connection methods and network transports are as follows.

Protocol Program Neighborhood Agent Web Client
TCP/IP+HTTP X X
SSL/TLS+HTTPS X X
TCP/IP   X

For information about configuring the clients to use SSL or TLS to secure communications, see the Clients for Windows 10.x Administrator's Guide.

Other Documents You Should Read

This document is the only one created specifically for this version of the Citrix Desktop Receiver Embedded Edition. This client package supports connections to desktops created with Desktop Delivery Controller. So, if you use that component of the Citrix XenDesktop product, we also recommend reading the Desktop Delivery Controller Administrator's
Guide
, which includes a description of how users experience the connection to desktops, information about configuring that product to customize the user experience, and supported features.

The Clients for Windows 10.x Administrator's Guide describes the features included in the last major release of the clients and how to configure them.

Consult the Citrix XenApp documentation for information on that product, and instructions on using its features.

New Features in this Release

The Citrix Desktop Receiver Embedded Edition contains all of the Independent Computing Architecture (ICA) features in version 10.200 of the Citrix Presentation Server Clients for Windows. Connections to virtual desktops support many of these features, including several SpeedScreen technologies and the Universal Printer Driver. All supported features are listed in the Desktop Delivery Controller Administrator's Guide. In addition, the installation packages now use an improved compression method resulting in smaller file sizes.

The following new features are included in this release.

Full-Screen-Only Mode

Desktops running in full-screen-only mode are remote, virtual desktops that look and work like local ones. After a user logs on, the virtual desktop starts, is displayed across the entire screen, and automatically resizes to fit the local monitor. The user can create and save work normally, use the mouse and keyboard in the usual way, and access network resources and most types of external device. All mouse input and keyboard input (apart from CTRL+ALT+DEL and Windows logo key+L) is directed to the virtual desktop. Once configured with Desktop Delivery Controller, the user's locale settings on the local computer (such as the time zone and keyboard locale) are used on the virtual desktop.

When the user has completed their work and logs off, they are automatically logged off the local computer as well as the virtual desktop. In this way, the user experiences the logoff as a completely local operation.

Desktops in full-screen-only mode differ from those accessed with the Citrix Desktop Toolbar in two ways:

  • The user experience of full-screen-only mode mimics a local desktop because the virtual desktop always occupies the entire screen.
  • For full-screen-only desktops, administrators must run a second installer on the endpoint after running DesktopReceiverEmbedded-1.msi. For more information on this installer, see the installation instructions.

Citrix Desktop Toolbar

The Citrix Desktop Toolbar is a new user interface that is included with the Web Client, Program Neighborhood Agent, and the Citrix Desktop Receiver. Desktops are displayed within the Citrix Desktop Toolbar window, which appears after the connection to a desktop has been established. Users can control their virtual desktops and customize the display of the window to suit their needs.

With the Citrix Desktop Toolbar, users can:

  • Switch desktops
  • Resize and scale desktops
  • Change the screen resolution of their desktops

Users can also customize where and how the Citrix Desktop Toolbar is displayed on the screen, and can minimize the space it occupies by switching from full-bar mode to mini-bar mode. To understand the user experience of this new component, read the chapter called "Planning the User Experience" in the Desktop Delivery Controller Administrator's Guide.

Dynamic Client Drive Mapping

Dynamic Client Drive Mapping extends the Client Drive Mapping feature in previous releases. It enables virtual desktops to access USB drives, such as USB flash drives, configured on the endpoint. It is the virtual desktop, not the local one, that is responsible for controlling USB drives and displaying them in the user interface.

When a USB drive is connected to an endpoint, it is automatically mounted and freely accessible. The exceptions to this are USB U3 devices, non-U3 encrypted devices, and card readers, which are not supported. For any given USB drive, the same drive letter is used by both the virtual and the local desktop as long as the virtual and local drive letters do not conflict.

Note: USB drives are treated as network drives. For this reason, users cannot check, reformat, or perform other local operations on them.

Support for Multiple Monitors

Virtual desktops in full-screen-only mode can be viewed on up to eight monitors with identical screen resolutions of up to 1024 × 768 per monitor (at 24 bits per pixel) working together to simulate a single, large screen. Since one virtual desktop can contain many open application windows, multimonitor users may find this feature useful because it allows them to reposition the windows across more than one monitor.

Alternatively, multimonitor users with multiple virtual desktops may find it useful to view each instance of the Citrix Desktop Toolbar (displaying each desktop) on a dedicated monitor.

Desktops Menu Folder

A new menu folder called Desktops has been added to the Program Neighborhood Agent menu, which is available in the notification area. The folder contains shortcuts to virtual desktops. The Applications folder is still present and contains shortcuts to virtual applications.

Installing the Clients

For quicker and easier roll-out across multiple endpoint devices on a network, you can package the client installation files using the msiexec.exe /a command. For more information about packaging the installation this way, see the Clients for Windows 10.x Administrator's Guide. You may also want to consult your Active Directory documentation for more information on rolling out software installations.

To install the clients using an MSI package, the Windows Installer Service must be installed on the endpoint device. This service is present by default on systems running Windows Vista, Windows XP, and Windows Server 2003.

Important Installation Information

Before installation, decide which clients your users will need and which site types they require access to. The chapter called "Planning the User Experience" in the Desktop Delivery Controller Administrator's Guide describes the clients, site types, and possible connection scenarios.

You cannot upgrade to this version of the clients, or install earlier versions, without first removing any that are currently installed.

The installation instructions in this topic refer to a package called DesktopReceiverEmbedded-1.msi. If your users only require the Citrix Desktop Toolbar, you can use DesktopReceiver.msi (which replaces Icaweb.cab and ica32web.msi in previous releases). These MSI packages are also available on the Desktop Delivery Controller installation media.

Make sure you consult the known issues in this release and the documentation for the Citrix products that you are intending to use with the clients. Product readmes and other pre-installation documentation may contain useful and late-breaking advice on installation.

If you use Active Directory to install full-screen-only desktops, be aware that no account can log on to the base operating
system after installation other than the system account used for the installation. This is because only the system account is excluded from the replacement shell used by full-screen-only desktops: the replacement shell is applied to all other accounts. For more information, see User Accounts for Full-Screen-Only Mode Installations.

To install the clients

Whether installation takes place using a package that you create or directly from an installer, the steps you follow vary depending on how users access virtual desktops: through the Citrix Desktop Toolbar or in full-screen-only mode. To install the Citrix Desktop Toolbar (and to set up access to virtual applications) on a single endpoint, you need only complete the Citrix Presentation Server Client (XenDesktop) Setup wizard (or the Citrix Desktop Receiver Setup wizard if you are performing the installation from your Desktop Delivery Controller installation media), not the remaining steps in this procedure. Those steps are required if you are setting up access to desktops in full-screen-only mode.

  1. Log on to the endpoint computer as a user who is a member of the local Administrators group.
  2. On your Desktop Delivery Controller installation media, navigate to the Clients\ica32 folder and double-click DesktopReceiverEmbedded-1.msi. Alternatively, download that installer file from the XenDesktop product pages of the Citrix Web site, and double-click the downloaded file. The Citrix Presentation Server Client (XenDesktop) Setup wizard appears.
  3. If required, in the Select Language dialog box, select your language from the drop-down list and click OK.
  4. On the Welcome page of the Setup wizard, click Next. A series of information pages and dialog boxes prompt you to select configuration options.
  5. On the License Agreement page, read and accept the Citrix license agreement and click Next.
  6. On the Select Client page, select the clients that you want to install and click Next. Note the following:
    • If you are connecting the endpoint to a desktop using a XenDesktop Services site, select Program Neighborhood Agent.
    • Program Neighborhood does not support access to desktops created with Desktop Delivery Controller.
  7. On the Server Address page, enter the URL of the site where your virtual desktops or applications are located and click Next. URLs for XenDesktop Services sites take the form http://servername/Citrix/PNAgent/config.xml. For secure connections, use the https:// protocol identifier instead of http://. If you are using hardware or software for load balancing or failover, you can enter a load-balanced address.

    Important : If you are using the endpoint to display a full-screen-only desktop, check that the URL you enter is correct and do not leave the Server Address field empty. If the URL is incorrectly typed, or you leave the field empty and the user does not enter a valid URL when prompted after installation, no virtual desktop or local desktop will be available.

  8. On the Select Program Folder page, specify the name of a new program folder that is added to users' Start menu. Click Next.
  9. On the Client Name page, specify a unique name for the endpoint. Servers use the endpoint name to manage system resources. By default, the full computer name is used. If you do not assign a unique name to each endpoint device, device mapping and resource publishing may not operate correctly.

    Important: The name must be less than 20 bytes and cannot contain the following characters: \ / : * ? " < > | , . ( ) [ ].

  10. If you are installing Program Neighborhood, select appropriate options on the Program Neighborhood Options page.
  11. On the Use Local Name and Password page, click Yes if you want to enable pass-through authentication. This avoids users having to log on to Program Neighborhood Agent each time they access their virtual desktops. For full-screen-only desktops, you must enable pass-through authentication on this page (and you must also enable it using the Access Management Console for the XenDesktop Services site that you specified earlier in this procedure).
  12. On the Ready to install page, check the installation summary. Click Back to modify any settings or Next to complete the Citrix Presentation Server Client (XenDesktop) Setup wizard. This step installs the Citrix Desktop Toolbar components.

    Important: Carry out the remaining steps only if you are setting up access to desktops in full-screen-only mode.

  13. On the endpoint device, switch to a local administrator account.
  14. Download the appropriate language version of the full-screen-only desktop client installer (for example, DesktopReceiverEmbedded-2_en.msi ) from the XenDesktop product pages of the Citrix Web site and double-click the downloaded file. Alternatively, on your Desktop Delivery Controller installation media, navigate to the Clients\ica32 folder and double-click that client installer. The Citrix Full-Screen Only Desktop Client wizard appears.
  15. On the License Agreement page, read and accept the Citrix license agreement and click Install. The Installation Progress page appears.
  16. In the Installation Completed dialog box, click Close.
  17. When prompted, restart the endpoint computer. If you have been granted access to a full-screen-only desktop and you log in as a domain user, the computer will restart in full-screen-only mode.

User Accounts for Full-Screen-Only Mode Installations

Program Neighborhood Agent uses a replacement shell to provide full-screen-only mode functionality. However, during the replacement, Program Neighborhood Agent excludes the account that was used during installation. This allows that account to be used later to administer the endpoint device; for example, to remove client components. The account is excluded from the shell replacement by making it use the default Microsoft Windows Explorer shell, Explorer.exe. To avoid this exclusion from affecting other endpoints in your environment, Citrix recommends using a local administrator account on the endpoint device. Alternatively, if you have a custom shell, you can change the appropriate Group Policy Object to use your shell and not Explorer.exe. However, note that Citrix does not recommend the use of custom shells with full-screen-only desktops. Customized shells can be used to control the user experience, but they may adversely affect the replacement shell, resulting in unexpected behavior such as users being presented with a local desktop, not a virtual one, or no shell being applied.

Removing the Clients

To remove a client, run the Add/Remove Programs utility from the Control Panel on Windows XP, Windows 2000, or Windows Server 2003. On Windows XP Embedded, right-click the installer file and select Uninstall. Run the Programs and Features utility from the Control Panel on Windows Vista. Alternatively, if a client was installed using a Windows Installer package, you can run the Citrix Presentation Server Client (XenDesktop) Setup wizard and select the Remove option.

The Citrix Desktop Receiver Embedded Edition is listed in Add/Remove Programs as Citrix Presentation Server Client (XenDesktop). The full-screen-only-mode
components are listed as Citrix Full-Screen-Only Desktop Client. If client software was installed using DesktopReceiver.msi, it is listed as Citrix Desktop Receiver.

Using the New Features

This section describes how to use the new features in this release. Where necessary, it also contains other information that users may need to be aware of.

For information on how you or your users configure and use other aspects of the clients, see the Clients for Windows 10.x Administrator's Guide.

Accessing Virtual Desktops

Users access desktops in full-screen-only mode by logging on to their local computer and following the on-screen prompts. Users access other types of virtual desktop using the Citrix Desktop Toolbar, which they obtain either from a XenDesktop Web site that you make available or by installing the Web Client, Program Neighborhood Agent, or the Citrix Desktop Receiver on their local computer. Typical connection scenarios are described in the chapter called "Planning the User Experience" in the Desktop Delivery Controller Administrator's Guide.

Virtual desktops cannot be accessed if they are already in use locally or remotely.

If you do not use proxy servers in your environment, correct the Internet Explorer proxy settings on any endpoints running Internet Explorer 7.0 on Windows XP. By default, this configuration automatically detects proxy settings. If proxy servers are not used, users will experience unnecessary delays during the detection process. For instructions on changing the proxy settings, consult your Internet Explorer documentation. Alternatively, you can change proxy settings using the Web Interface. For more information, consult the Web Interface Administrator's Guide.

Using the Citrix Desktop Toolbar

After installation, no configuration of the Citrix Desktop Toolbar is required, but be aware that using seamless windows (an existing feature available with XenApp connections) may reduce connection speeds to virtual desktops. Therefore, users should be discouraged from switching the Citrix Desktop Toolbar to and from seamless mode, or setting Window size to Seamless in Program Neighborhood Agent's Options dialog box.

Resizing changes are saved to the endpoint device or roaming profile (if set up), and are used the next time the user connects to the desktop.

When used with multiple monitors, note that the Citrix Desktop Toolbar maximizes to any monitor it overlaps, so to maximize it across two monitors, drag the Toolbar across both monitors and then click the Maximize button on the window.

Users can right-click to view a virtual desktop's properties and change some properties (such as font size), but they cannot change the desktop's size this way. Users should also be aware that their local desktop color scheme is not adopted by the virtual desktop.

Users can achieve most of the following tasks with buttons on the Citrix Desktop Toolbar. For accessibility reasons, the alternative use of the Citrix Desktop Toolbar menu is described here. The Citrix Desktop Toolbar menu is the drop-down menu located next to the Citrix logo on the toolbar. It can be accessed using the CTRL+ALT+BREAK keyboard shortcut. The Desktop Delivery Controller Administrator's Guide describes the appearance and use of the Citrix Desktop Toolbar.

To scale a virtual desktop so it fits exactly in the Citrix Desktop Toolbar

Scaling a virtual desktop this way allows you to quickly see the entire desktop. This can be useful when you are working on your local desktop but want to monitor the virtual desktop using a small Citrix Desktop Toolbar window (for example, you just want to watch the progress of an installation on the remote computer).

  • On the Citrix Desktop Toolbar menu, click Scale to Fit. If the virtual desktop resolution does not match your local desktop (for example, you logged on from a computer with a bigger monitor), you are prompted to resize the virtual desktop.

Note: After clicking Scale to Fit, the shape of the Citrix Desktop Toolbar window is fixed. To change the shape, first click Actual Size.

To change the resolution of a virtual desktop so it fits exactly in the Citrix Desktop Toolbar

Once you have the Citrix Desktop Toolbar window positioned and sized correctly, changing the resolution sharpens the desktop image and displays the entire desktop. Changing the resolution of a virtual desktop removes scroll bars and any blurring, but the position of desktop icons may change and the desktop's background graphic may appear distorted.

  • On the Citrix Desktop Toolbar menu, click Change Resolution and then OK when asked to confirm.

Note: When viewed across multiple monitors, the Citrix Desktop Toolbar displays desktops differently compared to those running in full-screen-only mode. With the Citrix Desktop Toolbar, the virtual desktop’s taskbar spans all monitors.

To display a virtual desktop at its actual size on the remote computer

Viewing a desktop at its size on the remote computer reproduces the exact display of the desktop in the Citrix Desktop Toolbar. This can be useful when examining content such as detailed graphics. Desktop scaling and the position of icons on the virtual desktop do not change relative to the remote desktop, but if the Citrix Desktop Toolbar window is smaller than the remote desktop, you have to use scroll bars to view the entire desktop.

  1. On the Citrix Desktop Toolbar menu, click Actual Size.
  2. Click Fit Desktop to Window to remove any scroll bars or white border around the virtual desktop.

To move the Citrix Desktop Toolbar to another edge of the screen

  • With the Citrix Desktop Toolbar maximized, click on any part of the Citrix Desktop Toolbar that is not a control and drag it to the left, right, or bottom edge of the screen. The toolbar is repositioned next to that edge.

To fix the Citrix Desktop Toolbar in one location on the screen

  • On the Citrix Desktop Toolbar, click the desktop name. The Citrix Desktop Toolbar is pinned to the top of the screen and cannot be dragged to another location. Clicking the name again allows you to move the Citrix Desktop Toolbar elsewhere.

To display the mini-bar

In mini-bar mode, the Citrix Desktop Toolbar menu and some buttons are not available but the Citrix Desktop Toolbar occupies less screen space.

  • On the Citrix Desktop Toolbar, click the Mini-Bar button. Clicking the Full-Bar button displays all of the buttons again.

To hide the Citrix Desktop Toolbar

Hide the toolbar when you don't need to use the controls on it and want to maximize screen space.

  • With the Citrix Desktop Toolbar window maximized, click Autohide. The toolbar disappears, except for a small handle. When you move your mouse pointer near the handle, the toolbar reappears. Clicking Pin keeps the toolbar visible at all times.

To switch to another desktop

If you have been set up with access to other desktops, their names appear at the top of the Citrix Desktop Toolbar menu.

  • On the Citrix Desktop Toolbar menu, click the name of the desktop you want to switch to. After a short time, the new desktop appears in the Citrix Desktop Toolbar.

To log off
from a virtual computer, shut it down, or lock its screen

The actions that you can take on the virtual computer depend on how your access rights were set up by your Desktop Delivery Controller administrator.

  1. On the Citrix Desktop Toolbar menu, click Send CTRL+ALT+DEL.
  2. Choose the action that you want to perform and follow the on-screen prompts.

To disconnect from the virtual desktop

  1. Save your work on the virtual desktop.
  2. On the Citrix Desktop Toolbar menu, click Close (Disconnect).

Using Desktops in Full-Screen-Only Mode

Administrators should note the following concerning desktops running in full-screen-only mode:

  • After client installation, no endpoint configuration is required
  • You should only grant access to one desktop per user
  • Multiple desktops running on one endpoint are not supported

There is little user interface associated with desktops running in full-screen-only mode. Messages are displayed keeping the user informed while connections to virtual desktops are in progress and for other state changes; for example, while the desktop is closing down. When users complete their work, their closedown actions have varying effects depending on the location of their physical machine (local or remote) and the configuration applied by their Desktop Delivery Controller administrator (whether logging off, shutting down, and so on, are allowed).

For security reasons, screensavers that automatically lock either local or virtual desktops should not be used. If a screensaver is activated on a virtual desktop, for example, it may give the false impression that the local desktop is locked.

The effects of closedown and lock actions on local computers and remote computers (physical or virtual) are as follows. Depending on how the logoff and standby actions are performed, different results may be experienced. Consult the Known Issues in this Release topic for important information on these actions and the hibernate action.

User action Result

Logoff

Logs the user off the virtual desktop and local computer and returns them to the local logon dialog box.

Shutdown

Shuts down the virtual desktop and local computer.

Restart

Restarts the virtual desktop and local computer, and returns the user to the local logon dialog box.

Standby

Puts the virtual desktop in the standby state. The Resume action returns the user to the local logon dialog box.

Lock computer Locks the virtual desktop and returns the user to the local Computer Locked dialog box.

Standby and lock actions on the local computer do not affect the virtual desktop, but its behavior in response to a local logoff is configurable by Desktop Delivery Controller administrators, as is the effect of the idle state on local computers.

Using USB Drives

Access to local USB drives is enabled by default. If you wish to prevent user access to USB drives, disable the appropriate policy in the Presentation Server Console. For instructions on this topic, see the Desktop Delivery Controller Administrator's Guide.

Typically, a user inserts a USB drive on their endpoint device and it is recognized by all of the virtual desktops to which the user is connected. Using Windows Explorer, the user can copy files to and from the virtual desktop (as if it were local) and between desktop sessions (as if the drive was mounted on each desktop). Users should follow the procedure in this section for removing USB drives safely.

Note: USB drives are treated as network drives. For this reason, users cannot check, reformat, or perform other local operations on them. The options for these tasks on the shortcut menu in Windows Explorer are non-operational.

To remove a local USB drive from a desktop in full-screen-only mode

  1. On the virtual desktop, right-click the drive in Windows Explorer and click Disconnect.
  2. Remove the USB drive from the local computer.

Do not use the Safely Remove Hardware command in the notification area to remove the drive. Doing so may cause errors.

To remove a local USB drive safely when using the Citrix Desktop Toolbar

  1. Minimize the Citrix Desktop Toolbar.
  2. Double-click the Safely Remove Hardware command in the notification area and follow the on-screen instructions.
  3. When prompted, remove the USB drive from the local computer.

Other Factors Affecting the User Experience

This section contains recommendations and describes aspects of the user experience that may be important to users who connect to virtual desktops. You may also want to familiarize yourself with these topics if, in addition to virtual desktops, your users connect to applications published with Citrix XenApp.

Connections, Sessions, and Devices

Connections to desktops created with Citrix XenDesktop support workspace control. This feature (not enabled by default) allows users to roam. That is, they can disconnect from a virtual desktop accessed through one endpoint and reconnect to the same desktop through another. If the user remains connected through the first endpoint when they connect through the second, the same session is used for the new connection. Be aware that this is slightly different from how workspace control operates with applications published with Citrix XenApp, where the second connection creates a new session.

From within a desktop session, users cannot connect to the same desktop. Attempting to do so will disconnect the existing desktop session. Therefore, Citrix recommends:

  • Administrators should not configure the clients on a desktop to point to a site that publishes the same desktop
  • Users should not browse to a site that hosts the same desktop if the site is configured to automatically reconnect users to existing sessions
  • Users should not browse to a site that hosts the same desktop and try to launch it

From within a desktop session, users cannot connect to a second desktop in a different virtual desktop group. Only a single connection is supported between an endpoint and a virtual desktop, so a second user cannot connect to a virtual desktop if it is already in use.

Be aware that a user who logs on locally to a computer that is acting as a virtual desktop blocks connections to that desktop.

If your users connect to virtual applications (published with XenApp) from within a virtual desktop and your organization has a separate XenApp administrator, Citrix recommends working with them to define device mapping such that desktop devices are mapped consistently within desktop and application sessions. Because local drives are displayed as network drives in desktop sessions, the XenApp administrator needs to change the drive mapping policy to include network drives.

Drives mapped on endpoint devices are unmapped when XenDesktop sessions are disconnected.

Keyboard Input

When you use a virtual desktop, all key presses are directed to it (not the local computer) with the following exceptions.

When you use a desktop in full-screen-only mode,
pressing CTRL+ALT+DELETE (or CTRL+F1 on computers running Windows Vista) displays a message that tells you how to send this key combination to the virtual desktop.

The CTRL+ALT+BREAK keyboard shortcut opens the Citrix Desktop Toolbar menu.

StickyKeys key presses are always sent to the local computer. StickyKeys is a Microsoft feature that is activated by pressing the left SHIFT key five times sequentially. You can turn off StickyKeys, but only by disabling all accessibility options in Windows using a Group Policy Object.

Printing

Printing through Citrix XenDesktop and Citrix XenApp sessions is slightly different.

On a Windows computer, the Printers and Faxes window displays a list of configured printers. The printer names used in application sessions (for printer output from applications published with XenApp) include a session identifier. However, printer names used in desktop sessions do not include any session identifier.

Unlike Citrix XenApp, the Universal Printer Driver used in Citrix XenDesktop reinstates a user's default printer when they disconnect from a virtual desktop. This improves usability if the user later logs on to the computer locally.

Printer drivers can be replicated (using the Presentation Server Console) between servers but not between desktops in a Citrix XenDesktop deployment.

Known Issues in this Release

The following is a list of known issues in this release. Read this information carefully before installing the clients.

Installation Issues

The Desktop Receiver Embedded Edition Part 2 setup wizard fails on the 64-bit edition of Windows XP Professional Service Pack 2. The wizard can be used on all other supported operating systems as defined in the System Requirements topic. [#183440]

If you have used this or an earlier release to install the Web Client (or your Desktop Delivery Controller installation media to install the Citrix Desktop Receiver), you cannot use DesktopReceiverEmbedded-1.msi to install any of the other client components (Program Neighborhood Agent or Program Neighborhood). You must first remove the Web Client or Citrix Desktop Receiver (which installs the Citrix Desktop Toolbar), and then install or reinstall all of the required components. [#173290]

If you package DesktopReceiverEmbedded-1.msi using the msiexec.exe /a command, note that a Citrix folder and an empty subfolder called Application are created by default. [#186318]

After installing the Citrix Desktop Receiver from DesktopReceiver.msi and logging on as a domain user with local administration privileges, the client detection feature of Web Interface does not work when you use the Firefox browser to access virtual desktops. If you are running Windows Vista with User Account Control switched on, you can avoid this issue by installing the Web Client from DesktopReceiverEmbedded-1.msi instead of installing the Citrix Desktop Receiver from DesktopReceiver.msi. [#182781]

Citrix does not recommend the use of custom shells with full-screen-only desktops. If you use a custom shell whose intended users include local administrators, the system should apply the shell whenever local administrators log on. However, when they log on after removing full-screen-only desktop components, the shell is not used, which may result in unexpected behavior. This issue is not observed with users other than local administrators. [#189076]

You cannot upgrade to this version of the clients, or install earlier versions, without first removing any that are currently installed. If the full-screen-only desktop components are present and you choose to upgrade without first removing the installed clients, unexpected behavior may result. For example, the screen may turn black except for the Start menu and taskbar, which remain visible. After restarting the endpoint device (as prompted at the end of installation), normal behavior is restored (for example, the endpoint’s desktop is displayed properly). [#189015]

To install the DesktopReceiver.msi package for all users on Windows Vista, you must temporarily disable User Account Control (UAC), and then enable it again afterwards. [#191170]

Other Known Issues

After starting an application or a virtual desktop, the following error messages might appear in the Event Log. The presence of these messages does not affect the performance of the clients:

Event Type:	Error
Event Source: SideBySide
Event Category: None
Event ID: 59
Description:
Generate Activation Context failed for C:\PROGRA~1\Citrix\ICACLI~1\MFC80.DLL.
Reference error message: The operation completed successfully.
Event Type:	Error
Event Source: SideBySide
Event Category: None
Event ID: 58
Description:
Syntax error in manifest or policy file "C:\PROGRA~1\Citrix\ICACLI~1\Microsoft.VC80.MFCLOC.MANIFEST" on line 5.
Event Type:	Error
Event Source: SideBySide
Event Category: None
Event ID: 34
Description:
Component identity found in manifest does not match the identity of the component requested

The error messages result from file manifest issues with Visual Studio 2005 Service Pack 1; they do not mean that the launch attempts failed. You can prevent the messages from appearing by installing the following Microsoft Visual C++ 2005 Redistributable Packages:

[#178763, 190365]

When installed on Windows XP Embedded Service Pack 2 on certain devices, the Citrix Desktop Toolbar fails to connect to virtual desktops. This is due to a missing .dll file. This issue is not observed when using other supported operating systems or when accessing virtual desktops in full-screen-only mode. [#185486]

Pass-through authentication does not work when you use the Remote Desktop Protocol (RDP) to connect from an endpoint to a virtual desktop through a computer that is running in full-screen-only mode on Windows XP Professional with Service Pack 2. You can connect to the virtual desktop but your credentials are not passed through from the endpoint. Instead, you are asked to authenticate twice. Pass-through authentication also fails on Windows XP Professional with Service Pack 3, but in this case error messages are displayed and no connection is formed. [#185548, 185549]

If you use the Citrix Desktop Toolbar window in full-screen mode, Windows key combinations (for example, ALT+TAB) are not sent to the virtual desktop. As a workaround, select the On the remote desktop option from the Apply Windows key combinations control on the Session Options page in Program Neighborhood Agent's Options dialog box. Alternatively, set the equivalent option in the Web Interface. This workaround ensures all key combinations are sent to the remote machine. As a separate
issue, if you change the Citrix Desktop Toolbar from full-screen to window mode, the next keystroke is sent to the local computer. All further keystrokes are sent to the virtual desktop. There is no workaround for this issue. [#191438]

Connections to workstations fail if you configure the Web Interface to use pass-through authentication. When configuring the Web Interface using the Access Management Console, you must change the logon authority to Explicit so that users must enter their credentials on the Web Interface login page. [#170696]

The Log Off Sessions option on the Program Neighborhood Agent menu does not log off virtual desktops sessions. They are disconnected but not logged off. That option functions correctly with XenApp sessions. Users should log off the virtual desktop (for example, using the Start menu) rather than using the client to do so. Alternatively, Desktop Delivery Controller administrators can configure connection timers to automatically log off disconnected sessions. [#176769]

The Citrix Desktop Toolbar may stop responding when you try to maximize it across multiple monitors that have different screens resolutions. Citrix recommends using the same resolution for each monitor. [#178459]

In rare circumstances, Utility Manager can be used to access the physical computer running a virtual desktop in full-screen-only mode. To prevent such access, Citrix recommends disabling Utility Manager. For instructions on this, see your Microsoft documentation. [#184069]

When using multiple monitors, each must have the same screen resolution. If different resolutions are used, the Citrix Desktop Toolbar window may not resize correctly across the monitors and the virtual desktop may be displayed incorrectly. [#185794]

No session information about virtual desktops is displayed when you right-click the Program Neighborhood Agent icon in the notification area and click Connection Center. After logging off from a virtual desktop session and closing Program Neighborhood Agent, the Connection Center icon is still displayed in the notification area. You can safely right-click the icon and click Terminate Connection Center. [#186997, 172742]

On Windows Vista, using the Aero mouse pointer theme degrades the performance of virtual desktop sessions. This theme is turned off by default by the Virtual Desktop Agent (the set of components installed on virtual desktops) each time the user logs in, but it can be turned on again by users for the duration of their session. [#189424]

When logging off a full-screen-only desktop, different logoff methods have slightly different effects. Logging off using the Windows Security dialog box (for example, by clicking CTRL+ALT+DELETE) disconnects the virtual desktop session, leaving it in the In Use state in the Access Management Console; the user is not logged off. Logging off using the Shut Down Windows dialog box (for example, by clicking Start > Shut Down) does not ask for confirmation but does close the session, leaving it in the Idle state; the user is logged off. Using the Log Off Windows dialog box (by clicking Start > Log Off) asks for confirmation and closes the session; the user is logged off. [#187428]

Shutting down or restarting using the Windows Security dialog box (for example, by clicking CTRL+ALT+DELETE) shuts down or restarts the local computer but not the virtual desktop. The desktop session is left in the In Use state in the Access Management Console, and the user is not logged off from the virtual desktop. Other methods of shutting down or restarting (such as clicking Start > Shut Down) work correctly. [#187808]

Allowing users to hibernate the virtual desktop can cause undesirable behavior and should be avoided. Use Active Directory policies appropriately to prevent users from hibernating virtual desktops. [#185614]

Very occasionally, maximizing the Citrix Desktop Toolbar window by clicking its taskbar button does not work. This issue also occurs whenever you minimize the window while a connection is being established. You can maximize the window by right-clicking it and clicking Restore. [#189252, 190047]

When the Citrix Access Gateway Advanced Edition is used with XenDesktop, reconnected desktop sessions are not displayed in the Citrix Desktop Toolbar due to an issue with workspace control. For example, after a user has logged on to Access Gateway and disconnected from a desktop session, on reconnection the desktop is displayed full-screen or in an ICA session window (depending on the administrator's Access Gateway settings). This issue is confined to reconnected sessions and does not occur when users first start a desktop session, or with other editions of Access Gateway. As a workaround, you can disable workspace control in Access Gateway or add the ConnectionBar=1 setting to the Access Gateway default ICA file, which forces all sessions (including those used for resources published with Citrix XenApp) to use the Citrix Desktop Toolbar. For more information on these workarounds, see your Access Gateway documentation. [#185387]

Some text in the Citrix Desktop Receiver Embedded Edition user interface, including the Help, refers to the Citrix Presentation Server Clients for Windows and to Citrix Presentation Server Client (XenDesktop).

Citrix Systems, Inc.
851 West Cypress Creek Road
Fort Lauderdale, Florida 33309 USA
954-267-3000

http://www.citrix.com/

Copyright © 2008 Citrix Systems, Inc.


This document applies to:

  • XenDesktop 2.0 x32

 



Primary links

Custom Search

Who's new

  • japhabept
  • Rullydery
  • eagenorce
  • rittaarier
  • swasseZex

Who's online

There are currently 0 users and 3 guests online.

KrissysCorner.com RuthSwensonLaw.com CreativeLizardProductions.com

DISCLAIMER:

None of this has anything to do with us, someone else is responsible for the entire thing, and we have no idea who or why. We do not know anything about it. It may be alien life forms for all we know: we haven't a clue. You cannot blame us for anything that may result from your visit. That was entirely your own personal choice, made by you of your own volition, and without our knowledge. We do not, after all, have any control over you and cannot by any stretch of the imagination be expected to accept or acknowledge, be it legally or morally, any accountability for decisions made by you on an independent basis, utilizing your own free will, and without our intervention. We are therefore in no way, shape, or form answerable to anyone for any consequences arising from the aforementioned or indeed any other actions, similar or otherwise, because it was not us that did, or did not do anything. It is not even remotely our fault, and we are in no way prepared or willing to accept any liability, not even slightly, ever. We are, in fact completely and utterly blameless, in that it is definitely not our concern, and no blame can possibly be laid at our doorstep, even if we had one, the possession of which we hereby reserve as being entirely our own free choice. The onus is not on us at all, and furthermore, never has been. The entire matter is wholly beyond our control, and completely out of our hands, each of which are washed scrupulously clean of the whole business. We are not accountable for anything at all, and we hereby categorically deny all responsibility for all that has ever, or will ever happen. Our innocence is therefore wholly beyond doubt and absolutely unimpeachable, and so cannot, under even the remotest or unlikeliest circumstances, be brought into question. By clicking either on a link on this site, clicking on a link that leads to this site, or by arriving at this site by natural or supernatural means, you are in effect accepting responsibility for the fact that it is all entirely your own fault, down to the most miniscule detail, and that you are wholly accountable for whatever outcome may arise as a consequence of the aforementioned action or actions insofar as they were undertaken personally by you on an entirely voluntary basis and without any persuasion, coercion or influence from any party or parties other than yourself. Don't come sniveling to us, we are only figments of your imagination. I also agree that if I am ever with a contributor to this website during mealtimes I agree to pay for any super-sizing of their meal, or at least a nice dessert or one of those foo-foo drinks with an umbrella or a monkey. By admitting to have seen the worthless spineless drivel on this website (also known as content)

I Agree Wholeheartedly and Without Reservation to the above. (Except maybe for that part about the monkey.)

All Your Base Are Belong To Us.

Soylent Green Is People!

Never make a bet with a Sicilian when Death is on the Line!

No. Really, I do agree.