Citrix states:

Desktop Delivery Controller 2.0 Readme

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

Desktop Delivery Controller 2.0

Readme

Readme Version: 1.0

This document describes known issues in this release of Desktop Delivery Controller. For information about how to install and use the product, see the Desktop Delivery Controller Administrator's Guide.

Known Issues in this Release

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

• Installation Issues
• Other Known Issues
• Licensing Issues

Installation Issues

If you install the Virtual Desktop Agent on a computer running Microsoft Vista with no service packs installed and also without .NET Framework 3.5 installed, .NET Framework 3.5 is installed and the computer then restarts automatically. After you have logged on, you must resume the Virtual Desktop Agent installation manually. [189331]

Installing Desktop Delivery Controller on 64-bit operating systems fails when you are using Oracle 10g as an external database. To use the Oracle 10g (or previous) client with 64-bit operating systems, you must install Desktop Delivery Controller in a folder that has a name without parentheses, unlike the Program Files (x86) folder. To change the default installation path, you must start the installer from the command-line prompt as follows: Setup.exe -showui. This workaround is not necessary with the Oracle 11g client. [189762}

[Back to installation issues contents]

Other Known Issues

Windows Media Player can still be heard after muting audio on the virtual desktop. Edit the Windows Media Player speaker device properties to select playback through "DirectSound: Citrix Audio Driver (emulated)" rather than "Default DirectSound Device". Then restart Media Player and the volume control works as expected. [183076]

Under some conditions users can connect to a virtual desktop that is in the process of shutting down. To avoid this, put desktops into maintenance mode before using the Access Management Console to change their power state. [188997]

If there is a network outage that lasts longer than the session reliability time-out value in the client (15 - 60 seconds depending on the access method) but is less than the session reliability time-out configured for the Virtual Desktop Agent (3 minutes by default), the user cannot reconnect to the session using the Reconnect option in either Program Neighborhood Agent or Web Interface: the error message "There are no sessions to reconnect to" appears. The user can either force a connection back to the session by relaunching the desktop, or wait longer than the session reliability time-out value before trying to reconnect. [189043]

During a network outage with session reliability enabled, users who continue to click or type in their virtual desktop may become disconnected from their session when the network resumes. They can reconnect to their session in the usual way, as if they had intentionally disconnected. They can avoid this issue by not providing input to the virtual desktop until the network connection is resumed and the session has fully caught up with any updates stored during the outage. [189145]

If a port number above 65355 is used for session reliability, an error is reported in the Windows Event Log on any virtual desktop that attempts to register with the controller. Further connections to the desktop are not possible until a port number between 1 and 65355 is selected and the desktop is restarted. [189023]

On Microsoft Vista, switching to full-screen mode in a command-line window results in the command-line window appearing full-screen on the physical console, and the user's session freezing. The contents of the command-line window are visible on the console, but there are no access security issues because the keyboard and mouse do not work on the console window. To recover, the user must switch back to window mode by pressing ALT +ENTER again in the session. [189074]

On Microsoft Vista, the user's default printer does not get tagged as the default printer in the session. [189077]

On Microsoft Vista, the Provisioning Server client is unable to connect to the vDisk if the WANScaler client is installed on the same VM. [190713]

Client for Linux users cannot connect through to virtual desktops through the default XenDesktop Services site if the desktop group name is longer than 15 characters. To avoid this issue, create desktop groups with names of 15 characters or fewer. [189412]

Endpoints running the Client for Linux may fail to connect (connection immediately drops) if the endpoint machine name and/or the desktop group name are lengthy strings. If you experience this issue, reduce the length of the endpoint machine name or desktop group name such that their total combined length is 29 characters or less. [191440]

Microsoft Internet Explorer suffers with screen flicker in Terminal Services client sessions. For information about how to resolve the issue, see http://support.microsoft.com/kb/271246. The article refers to Internet Explorer versions 5.5 and 6.0. The Internet Explorer 6.0 workaround also applies to Internet Explorer 7.0. [189767]

If the user drags an application playing video, the virtual desktop may enter a non-responsive state from which it will recover after some minutes. The user may need to reconnect to the session after the recovery because the client may time out during this period. The problem is more likely to occur if the desktop is being accessed over a WAN or internet connection with high latency. To avoid this issue, users should switch off the display of window contents while dragging. [191059]

The Virtual Desktop Agent is incompatible with Citrix Password Manager. [186710]

Do not use XenApp management consoles (Access Management Console and Presentation Server
Console) to manage XenDesktop farms, otherwise serious errors may occur. [190795]

If you use Edgesight to monitor delivery controllers, note that it monitors sessions connected to the console of the controller, not connections brokered by the controller to desktops. [190804]

Desktop Delivery Controller has a service that listens on TCP port 2598. This port is not required. Citrix recommends that you configure firewalls on delivery controllers to block inbound traffic to this port. [191106]

The Bandwidth tab is present on the Printer Management page of the Presentation Server Console, but this functionality is not available for XenDesktop. [191114]

The Export to File and Import from File buttons are truncated on the Virtual Desktops page of the Create Desktop Group wizard for Korean, Traditional Chinese and Simplified Chinese 64-bit servers. Suggested workarounds are:

• Use hotkeys Alt+X for Export to File and Alt+P for Import from File
• Create an empty desktop group without importing virtual desktops. If you then navigate to the property pages for the desktop group, the Export to File and Import from File buttons are available. [189389]

Farm names cannot contain double-byte characters on 32-bit MUI servers. You must limit farm names to Roman characters. [189637]

[Back to known issues contents]

Licensing Issues

Installation Issues

Note that if you install Citrix Licensing through the Desktop Delivery Controller Autorun.exe or Setup.exe files, as recommended, some of the issues listed below will not occur.

When typing an installation path for the license server, use ASCII characters only; otherwise, the License Management Console may not launch. [173746, 180337]

Installing the Citrix License Server Version 11.5 on a Windows 2000 Server cluster fails. There is no workaround at this time. [186461]

After installing the Citrix License Server on a Windows Server 2008 cluster, the cluster resources are not visible in the Cluster Manager user interface. To view the status of the services, use the cluster resource tools from a command prompt. [171118]

To install Citrix Licensing using Active Directory, you must apply the ActiveDirectoryLicensingInstallSupport.mst transform file. [76996]

During the installation of the Citrix License Server Version 11.5, ensure that you enter the port numbers correctly within the displayed range. If you append any additional characters to the port number or enter anything other than numerical characters, the install will continue, the license files will be updated with the incorrect port number, and the license server will not be able to communicate. [184329]

When configuring the product-side setting for the license server name, do not use localhost. Use the host name, IP address, or FQDN instead. [165986]

After the licensing components are installed and the Citrix Licensing service restarts, two copies of the license server (lmgrd.exe) are launched. This occurs with license server versions 11.1, 11.3, and 11.5. This is "as designed". Two lmgrd.exe processes exist during normal execution. [182151]

Before you perform an unattended installation of Citrix Licensing you must install the JRE version supported by the licensing components (1.5.0_15). To install the JRE from the command line, type: jre-1_5_0_15-windows-i586-p.exe /lang=1033 /v"/qn REBOOT=ReallySuppress REBOOTPROMPT=Suppress ADDLOCAL=ALLWEBSTARTICON=0 AUTOUPDATECHECK=0 IEXPLORER=1 MOZILLA=1. When you perform the unattended installation of Citrix Licensing, specify the CTX_USE_EXISTING_JRE property with a value of ‘YES’ . [83379, 150474]

On Windows Server 2003 operating systems, when you attempt to install the Citrix License Server, the installation fails and error 1935 appears in the System Windows Event Log.  This issue is caused during the installation of Microsoft MSXML that is installed as part of the license server installation. To resolve this issue, install MSXML 4.0 SP2 from the Microsoft Download Center and then rerun the license server installation. [171653]

License Management Console Issues

When typing an installation path for the license server, use ASCII characters only; otherwise, the License Management Console may not launch. [173746]

After using the License Management Console to copy the license to the license server, the license does not appear in the License Management Console. Although the license does not appear, the license is copied successfully but is not recognized by the license server. Restart the Citrix License Management Console and the Citrix Licensing services to reread the file. [175275] 

If you are running an English version of a Windows operating system with a Japanese, Simplified Chinese, Traditional Chinese, or Korean supplemental language pack installed, you cannot log on to the License Management Console using a user name with multibyte characters. [82831]

When generating reports, make sure you click the Cancel button to close the License Management Console. If you do not click Cancel, reports continue running. To stop reports from generating after closing the console, restart the Citrix License Management Console service. [86689]

Generating product reports with the Percent Installed Licenses data type causes the reporting engine to lock. The License Management Console continues operating after the reporting engine locks. However, you must restart the Citrix License Management Console service before you can generate any further reports. [107210]

In the Options file, the GROUPCASEINSENSITIVE command (Options file) is not supported.

The following message appears in the lmgrd_debug log: "Non-activation-capable daemon activation invoked with non-client-request event type." Ignore this message.

When you launch the License Management Console on a Windows 2000 Server operating system and have the JRE version 1.6.0_05 installed, the License Management Console does not launch. This occurs due to the JRE 1.6.0_05 version's dependency on MSVCR71.dll. To solve this issue, copy the MSVCR71.dll file from the C:\Program Files\Java\jre1.6.0_05\bin\ directory to the C:\Program Files\Java\jre1.6.0_05\bin\client directory, restart the Citrix License Management Console service, then re-launch the License Management Console. [189359]

License Server Issues

On the Windows Server 2003 platform, an application error message appears when you attempt to shut down the license server. Ignore this message, or stop the Citrix Licensing service before you shut down the license server. [175449]

The following message appears in the Event Log Viewer: "(1224) Client/server comm version mismatch. The client and server programs are running potentially incompatible versions of FLEXnet comm software." This is an informational message indicating that an older version of the Citrix product is communicating with a newer version of the Citrix License Server. Ignore this message.

More than one Citrix startup license can be checked out by one Citrix product from a particular (Citrix) server. This may be caused by a problem with the Citrix.startup.lic license file. See article CTX113090 in the Citrix Knowledge Center for a new Citrix.startup.lic file and instructions for installing the new file.

[Back to licensing contents]

Documentation Errata

Desktop Delivery Controller Administrator's Guide

Page 78: Disconnect timer default settings are incorrectly documented. By default, the disconnect timer is
disabled for pre-assigned or assigned-on-first-use desktop groups and enabled for pooled desktop groups. The default setting is 1440 minutes (24 hours). [190662]

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.