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.

XenApp and XenDesktop

The XenApp and XenDesktop 7.13 release contains the following issues:

Install and upgrade

  • Installation or upgrade of a Controller on Windows Server 2012 R2, or a VDA on Windows 8.1 or Windows Server 2012 R2 will stop if Windows KB2919355 has not been installed. To avoid this, install that update before beginning the Controller or VDA installation. For more information, see Knowledge Center article CTX220340.

    [#DNA-29861]
  • If you install Studio (by itself) on a Windows 7 or Windows Server 2008 R2 machine, the installation fails. To avoid this, install .NET 4.5.2 (or a later supported .NET release) before installing Studio. (.NET 4.5.2 is available in the Support folder on the installation media.)

    [#DNA-34355]
  • On Windows 7 machines, the VDAWorkstationCoreSetup VDA installer creates system restore points for every ICAWS driver. This can add up to 15 minutes to the VDA installation. As a workaround, disable the Windows System Restore feature (Control Panel > System > System protection > Configure > Restore settings, select "Turn off system protection").

    [#HDX-5012]
  • When installing a VDA, the Summary page might contain a message indicating failure to connect to a Controller, even if the connection test was successful. The connection test result on the Delivery Controller page is correct.

    [#DNA-17822]

  • VDA does not register after upgrading from XenApp and XenDesktop 7.1 to XenApp and XenDesktop 7.12. To work around this issue, upgrade to 7.6 LTSR or the latest current release (7.13).

    [#DNA-25044]
  • 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]

AppDisk

  • After updating an image, some applications may fail to work properly due to an ability to verify previously installed licenses. For example, after an image upgrade, launching Microsoft Office may display an error message similar to:

    “Microsoft Office Professional Plus 2010 cannot verify the license for this application. A repair attempt failed or was canceled by the user, the application will now shut down.”

    To resolve this issue, uninstall Microsoft Office and install the new version on the base image.

    [#401558]
  • In some cases, downloading Metro apps from the Windows Store to a published catalog’s virtual machine fails after a long time.

    [#656703]

App-V

  • If you enable the Citrix Personalization for App-V - VDA check box, the "Citrix AppDisk / Personal vDisk" components are automatically selected. This is a known issue in this release. You can prevent this by installing the VDA from the command line containing the /exclude "Personal vDisk" option.

    [#DNA-29658]
  • If an App-V application in an isolation group does not close down properly, future launches that depend on other applications assigned to an isolation group with that application might fail. As a workaround, end the remaining process from the original application launch on the VDA. Then, remove the App-V isolation group and add it again.

    [#DNA-24270]
  • When you have multiple App-V packages with the same package ID but different version IDs, and add an application from one of those packages to a Delivery Group, applications from the other packages also appear to be assigned to that Delivery Group in the Studio App-V Publishing node. The applications from other packages are not actually added to the Delivery Group.

    [#DNA-23490]
  • If you change App-V server addresses in Studio, some properties on the server connections you specify might be reset to default values. These properties are used on the VDAs to connect to App-V publishing servers.

    To recover, reconfigure the nondefault values for any reset properties on the servers.

    To avoid this issue, use PowerShell to specify App-V server addresses if those servers use nondefault property values.

    [#DNA-23487]

Director

  • The table data on the Trends > Sessions page can be incomplete: data related to some sessions might be missing.

    [#DNA-28604]
  • The table data on the Filters > Application Instances page can be incomplete when you apply filters: data related to some application instances might be missing.

    [#DNA-28603]
  • 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

  • When the visual quality is set to Build To Lossless, the desktop display might be blurry even though the lossless indicatior specifies that the display is sharp.

    Workaround: Configure this registry setting:

    HKLM\Software\Citrix\Graphics\
    Name: PreviousFrameMatching
    Type: REG_DWORD
    Value: = 0

    [#HDX-8074]
  • Citrix Kerberos authentication (CtxAuth) does not work for VDAs installed on Windows Server 2016 machines that have Microsoft KB3213986 updates.

    [#HDX-7402]
  • 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]
  • If you are using MCS I/O optimization for a catalog containing 32-bit Windows machines, configuring a RAM Cache greater than the default 256 MB can cause the OS to stop. To prevent this, configure less RAM cache.

    [#DNA-35054]

  • Enabling mandatory logging in Studio (Logging > Preferences > Allow changes to the site configuration when the database is not available) does not enable mandatory logging.

    To work around this issue, use the PowerShell cmdlet Set-LogSite:

    set-logsite -State Mandatory

    To check the current state, enter Get-LogSite.

    [#DNA-36114]

  • 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

  • When you upgrade Session Recording Administration from 7.6 to 7.13 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".

    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 you record a session with a resolution higher than or equal to 4096 x 4096, there might be fragments in the recording appearance.

    [#524973]
  • When Machine Creation Services (MCS) or Provisioning Services (PVS) creates multiple VDAs with the configured master image and installed Microsoft Message Queuing (MSMQ), those VDAs might have the same QMId in 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.

The workaround is to create a unique QMId for each VDA and it differs depending on the deployment methods.

No extra actions are required if Desktop OS VDAs with the Session Recording agent installed are created with PVS 7.7 or later and MCS 7.9 or later in the static desktop mode that is, for example, configured to make all changes persistent with a separate Personal vDisk or the local disk of your VDA.

For Server OS VDAs created with MCS or PVS and Desktop OS VDAs that are configured to discard all changes when a user logs off, use the GenRandomQMID.ps1 script to modify the QMId on system startup. Modify the power management strategy to ensure that enough VDAs are running before user logon attempts.

To use the GenRandomQMID.ps1 script, do the following:

1. Make sure that the execution policy is set to RemoteSigned or Unrestricted in PowerShell.

Set-ExecutionPolicy RemoteSigned

2. Create a scheduled task, set the trigger as on system startup, and run with the SYSTEM account on the PVS or MCS master image machine.

3. Add the command as a startup task.

powershell .exe -file C:\GenRandomQMID.ps1

Summary of the GenRandomQMID.ps1 script:

  1. Remove the current QMId from the registry.
  2. Add SysPrep = 1 to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters.
  3. Stop related services, including CitrixSmAudAgent and MSMQ.
  4. To generate a random QMId, start the services that stopped previously.
GENRANDOMQMID.PS1 for reference Copy

# Remove old QMId from registry and set SysPrep flag for MSMQ

Remove-Itemproperty -Path HKLM:Software\Microsoft\MSMQ\Parameters\MachineCache -Name QMId -Force

Set-ItemProperty -Path HKLM:Software\Microsoft\MSMQ\Parameters -Name "SysPrep" -Type DWord -Value 1

# Get dependent services

$depServices = Get-Service -name MSMQ -dependentservices | Select -Property Name

# Restart MSMQ to get a new QMId

Restart-Service -force MSMQ

# Start dependent services

if ($depServices -ne $null) {

    foreach ($depService in $depServices) {

        $startMode = Get-WmiObject win32_service -filter "NAME = '$($depService.Name)'" | Select -Property StartMode

        if ($startMode.StartMode -eq "Auto") {

            Start-Service $depService.Name

        }
}

}

[#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 does not take effect immediately for Session Recording.

    Workaround: Restart your VDA machine.

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

    Resolution: Check the access control list (ACL) of the folder C:\windows\Temp to ensure that users under Local Users and Groups > Groups > Users have the write permission to this folder. If not, manually add the write permission.

    [#611487]
  • Because Session Recording does not support the Framehawk display mode, sessions in the Framehawk display mode cannot be recorded and played back correctly. Sessions recorded in the Framehawk display mode might not contain the sessions' activities.

    [#622085]

Citrix Licensing 11.14 Build 19005

  • When you try to start the Citrix Licensing Manager and Firefox is the default browser, the Citrix Licensing Manager is inaccessible and Firefox displays a generic error message.

    Workarounds: Do a hard refresh (Ctrl + F5).

    [#LIC-107]
  • The udadmin command might not delete licenses when there is an apostrophe in the device name.

    Workaround: Escape the apostrophe with a backslash. For example, udaadmin.exe –f XDT_PLT_UD –device “jim\’s” –delete

    [#LIC-142]

For the Citrix Licensing 11.14 known issues and fixed issues, see the Citrix Licensing 11.14 known and fixed issues.