Product Documentation

Known issues

Oct 31, 2017

The following warning applies to any workaround that suggests changing a registry entry.

Warning

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

Install and upgrade with the original version 7.14 software

IMPORTANT: If you installed or upgraded your deployment with the original 7.14 XenApp and XenDesktop ISO and VDAs, you must download the 7.14.1 XenApp and XenDesktop ISOs and VDAs, and then upgrade your deployment.

Some of the following issues might occur with the original 7.14 software; they are resolved in version 7.14.1. The first item requires a manual intervention before the upgrade to 7.14.1. For more information about 7.14.1, see the important notice at the beginning of the What’s new article. 

  • If an upgrade stops with the message “Failed to upload database scripts,” and your site is inoperable, run the following PowerShell cmdlets on every Delivery Controller in your Site:

asnp citrix*
Get-TrustDBConnection (verifies you are fixing this issue)
Set-TrustDBConnection $null (value should already be NULL, but does no harm)
Get-ConfigDBConnection (not required, but does no harm)
$cs = Get-ConfigDBConnection
Set-TrustDBConnection –DBConnection $cs

After running the cmdlets on all Controllers, launch Studio and proceed with a manual database and site upgrade. 

After the database and site upgrade complete successfully, upgrade the Controllers and VDAs again, this time to version 7.14.1.

[#DNA-43730]

  • After an upgrade, Director displays a Central Configuration Service alert. Although this issue does not impact site operations, you must still upgrade again to version 7.14.1.

[#DNA-43728]

  • Published applications might fail to launch. Citrix Receiver does not move past the launching application stage. Resolution: Upgrade the Controllers and VDAs to version 7.14.1.

[#HDX-9224]

  • When using a machine catalog in Azure with write back cache enabled, VDAs fail to register with a Delivery Controller.  Resolution: Upgrade the Controllers and VDAs to version 7.14.1.

[#DNA-43545]

  • A Citrix Receiver logon delay occurs when the “Wait for printers to be created (server desktop)” policy setting is enabled. Resolution: Upgrade the Controllers and VDAs to version 7.14.1.

(#HDX-9358]

XenApp and XenDesktop

The XenApp and XenDesktop 7.14 release contains the following issues:

Install and upgrade

  • Group policies in Citrix Studio are missing if the UPM - Software\Microsoft\Speech_OneCore policy under Profile Management > Registry > Default Exclusions was configured before upgrading the Delivery Controller from 7.11 to 7.14, from 7.12 to 7.14, or from 7.13 to 7.14. As a workaround, remove the policy before upgrading the Delivery Controller. For more information, see Knowledge Center article CTX 224755.

[#UPM-538]

  • When upgrading a XenDesktop 5.6 deployment to XenDesktop 7.14, group policy is missing. As a workaround, first upgrade from XenDesktop 5.6 to XenDesktop 7.13. Then upgrade from 7.13 to 7.14.

[#DNA-40976]

  • After upgrading Controllers, the power state of a VDA might indicate "Unknown." As a workaround, restart the Controllers.

[#DNA-37756]

  • When installing a Controller and you select I want to connect to Smart Tools and Call Home on the Smart Tools page of the installation wizard, Call Home might not be enabled. As a workaround, either use the schedule feature in Citrix Scout or enable Call Home using PowerShell.

[#CAM-9907]

  • When installing a Delivery Controller on Windows Server 2012 R2 or Windows Server 2016, if you choose to connect to Smart Tools, and have more than one organization linked with your Citrix Cloud account, the logon process may not complete after you enter your Citrix Cloud credentials. As a workaround, complete one of the following:
    • Ensure the Windows Server and Internet Explore have the latest updates.
    • Clear the Internet Explore browser option: Internet Options > Security > Local Intranet > Sites > Include all sites that bypass the proxy server.

[#CAM-9816]

  • When upgrading the Delivery Controller from a version earlier than 7.13, to version 7.13 and later, an error (exception) may be seen if the "Auto client reconnect timeout" setting is configured in any of the policies. This error happens if the "Auto client reconnect timeout" setting value is outside the permitted range 0 and 300, which was first introduced in version 7.13. To prevent this error, use the Citrix Group Policy PowerShell Provider to unconfigure the setting, or to set it to a value within the specified range. For an example, see CTX22947.

[#DNA-52476]

App-V

  • When you select machines and add them to existing Delivery Groups, Studio allows you to add machines from incompatible Machine Catalogs to the same Delivery Group. (If you first select a Delivery Group and add machines to it, Studio correctly prevents machines from incompatible Machine Catalogs being added.)

    [#DNA-39589]
  • In Studio, when deleting one or more App-V applications from the Applications node, or from a selected Delivery Group, the message "An unknown error occurred" appears. You can safely ignore the message; the applications are deleted.

    [#DNA-29702]

Director

  • The Monitoring Group Policies - Enable monitoring of application failures, Enable monitoring of application failures on Desktop OS VDAs, and List of applications excluded from failure monitoring are not functional in XenApp and XenDesktop version 7.14.
     [#DNA-42998]
  • The Director Dashboard fails to display data and the following error message appears:
    “Cannot retrieve the data”
    The trace shows the following message:
    “Dmc Service error. Citrix.Dmc.Common.ConnectorException: Monitoring Service: One of the DesktopGroup's name is null”
    This issue occurs if the name of a Delivery Group entry in the Monitoring database is undefined or NULL.
    Workaround:
    In the Monitoring database, go to the DesktopGroup table and delete the DeliveryGroup entries that have NULL in the name column. For detailed steps, see the Knowledge Center article CTX208206.
    [#DNA-25795]

General

  • During logon or logoff on a Windows 10 or Windows Server 2016 machine, the operation may pause and appear to be hung. Click in the session window to resume the operation.

    [#DNA-22958]
  • When Local Host Cache is enabled, users with desktop connections might be unable to reconnect to the desktop during an outage. If this occurs, restart the Citrix High Availability Service.

    [#DNA-22957]
  • Published content will not start successfully when initiated from Citrix Receiver. Content launched through the StoreFront web client (or Web Interface) launches as expected.

    [#LC6316]
  • When you're using Windows Media Player with Remote Audio & Video Extensions (RAVE) enabled inside a session, if you right click the video content and select Always show Now Playing on top, a black screen displays.

    [#HDX-4853]
  • If there are stale DNS entries for the NetScaler Gateway virtual server on the client device, adaptive transport and Framehawk might fall back to TCP transport instead of UDP transport.

    As a workaround, flush DNS cache on the client and reconnect to establish the session using UDP transport.

    [#HDX-7441]
  • You create an RDS machine catalog and Delivery Group and you enable the Enhanced Desktop Experience policy setting on the server. When you restart the RDS server and start an RDS hosted desktop with a non-administrator user using BGinfo, the wallpaper might not update as expected. Workaround: Do not use BGinfo.

    [#HDX-8881]
  • After the adaptive transport policy is changed, some Delivery Group sessions might be disconnected. The user can successfully reconnect but might be disconnected again if the adaptive transport policy changes.

    [#HDX-8812]
  • After upgrading XenDesktop, attempts to log off from a XenDesktop session might result in a blank desktop. The following error message appears:

    "Connection Interrupted
    Citrix Receiver will try to reconnect"

    [#LC6761]

Other components

Components available separately on the XenApp and XenDesktop download pages have the following known issues.

Session Recording

  • Attempts to install or upgrade to Session Recording Version 7.14 using the XenApp and XenDesktop full product installer fail on Windows Server 2008 and the following error message appears: "Microsoft Message Queuing failed". 

    As a workaround, use the msi package for fresh installations or upgrades. For more information, see Install, upgrade, and uninstall Session Recording

    [SRT-1782]
  • When you upgrade Session Recording Administration from 7.6 to 7.13 or later and choose Modify in Session Recording Administration to add the Administrator Logging service, the SQL Server instance name does not appear on the Administrator Logging Configuration page. The following error message appears when you click Next: "Database connection test failed. Please enter correct Database instance name".

    As a workaround, add the read permission for localhost users to the following SmartAuditor Server registry folder: (HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\SmartAuditor\Server).

    [SRT-1334]
  • When Machine Creation Services (MCS) or Provisioning Services (PVS) creates multiple VDAs with the configured master image and Microsoft Message Queuing (MSMQ) installed, those VDAs can have the same QMId under certain conditions. This might cause various issues, for example:
    • Sessions might not be recorded even if the recording agreement is accepted.
    • The Session Recording Server might not be able to receive session logoff signals and consequently, sessions might always be in Live status.

    For information about a workaround, see here.

    [#528678]

  • The Machine Creation Services (MCS) image update process may fail with VMware VSAN 6.x because the identity disk cannot be reliably retrieved and attach back to the virtual machine. If this happens, either manually delete and recreate the virtual machine, or create a new catalog for the image update.

    [#CTX219670 ]
  • When you change your XenApp or XenDesktop license type, the change might not take effect immediately for Session Recording.

    As a workaround, restart your VDA machine.

    [#532393]
  • The installation of the Session Recording Server components fails with error codes 2503 and 2502.

    As a workaround, check the access control list (ACL) of the folder C:\windows\Temp to ensure that users under Local Users and Groups > Groups > Users have write permission to the folder. If necessary, add the write permission manually.

    [#611487]

Citrix Licensing 11.14