Known issues 编辑

Known issues that are described in the 1912 initial release, CU1, CU2, CU3, CU4, and CU5 sections of this article continue to be present in CU6 unless they are included in the list of fixed issues.

This warning applies to any workaround that suggests changing a registry entry:

Warning:

Editing the registry incorrectly can cause serious problems that might 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.

Known issues in 1912 CU6

• Microsoft no longer supports the creation of new virtual machines with unmanaged disks on Azure. However, previously created master templates using unmanaged disks are usable. [LCM-10287]

• The command line install parameter, /IGNORE_DB_CHECK_FAILURE, is not supported in 1912 LTSR CUs. [LCM-11958]

Known issues in 1912 CU5

• Attempts to create a hosting connection to Azure in Citrix Studio might fail with an exception. The issue occurs due to the Microsoft changes made on Azure. A private fix is available at CTX457802. [CVADHELP-18741]

• When using this VDA version, Citrix policies applied to a machine by OU can sometimes fail to apply. [CVADHELP-19826]

• After upgrading Delivery Controller to version 1912 CU5, scheduled reboot might not work correctly with VDAs that are not power managed. [CVADHELP-20138]

Known issues in 1912 CU4

• When using this VDA version, Citrix policies applied to a machine by OU can sometimes fail to apply. [CVADHELP-19826]

• Attempts to create a hosting connection to Azure in Citrix Studio might fail with an exception. The issue occurs due to the Microsoft changes made on Azure. A private fix is available at CTX457802. [CVADHELP-18741]

• When you exit from a Citrix virtual session, one or more of the following issues might occur:

  • The VDA still lists the terminated session and the logonui.exe process. The logonui.exe process can be forcefully terminated.
  • The session appears with a blank username in Citrix Studio.
  • You might not be able to launch further sessions.

  A private fix is available at CTX340125.

  [CVADHELP-19182]

Known issues in 1912 CU3

• When attempting to update the Licensing CEIP option using the Set-LicCEIPOption cmdlet, the operation fails with a “Communication Error.” As a workaround, the CEIP option can be enabled through Citrix Licensing Manager. For more information, see Knowledge Center article CTX220679. [LCM-9169]

• Attempts to create a hosting connection to Azure in Citrix Studio might fail with an exception. The issue occurs due to the Microsoft changes made on Azure. A private fix is available at CTX457802. [CVADHELP-18741]

Known issues in 1912 CU2

• Configuring your on-premises site with Citrix Analytics for Performance from Director might fail if the Delivery Controller is running a Microsoft .NET Framework version earlier than 4.8. As a workaround, upgrade the .NET Framework in your Delivery Controller to version 4.8. [LCM-9255]

• Signing in to an unbrokered RDP session with a UPN credential might result in an uncaught exception. In 1912 LTSR CU2, a name translation for usernames provided as UPN was introduced. The truncation of the username due to the limit imposed in RDS data structures produces an incorrect username, resulting in the uncaught exception. [CVADHELP-16510]

• If the .NET Framework version is not at least 4.7.2 after upgrading to 1912 LTSR CU2, the Azure Resource Manager fails. [CVADHELP-16533]

• Attempts to create a hosting connection to Azure in Citrix Studio might fail with an exception. The issue occurs due to the Microsoft changes made on Azure. A private fix is available at CTX457802. [CVADHELP-18741]

• Citrix Director might fail to enumerate policy information. The issue occurs when you use an older version of Director to view session details associated with 1912 LTSR CU2 VDA. As a workaround, follow the steps mentioned in the upgrade sequence. [LCM-8201]

• Some file operations executed in a published app or a published desktop session to a client mapped drive might fail with a “permission denied” error message. Users might also see the “File In Use” error on the local client machine. For more information, see Knowledge Center article CTX285248. [HDX-26969]

Known issues in 1912 CU1

In addition to the known issues in the 1912 LTSR initial release, CU1 contains the following, new known issues:

Citrix Provisioning

• When you attempt to downgrade a Citrix Provisioning Target Device from Version 1912 LTSR or 1912 LTSR CU1, the following message might appear:

  Installation failed.

  As a workaround, uninstall the 1912 LTSR or 1912 LTSR CU1 version and then reinstall the earlier version. [LCM-7341]

• When you upgrade a Provisioning Server from Version 7.15 Cumulative Update 5 to Version 1912, a warning message might appear twice. This message appears because of a dependency on the CDF installer (a separate, Citrix Virtual Apps and Desktops component) during the installation of Citrix Provisioning. The provisioning installer cannot suppress the reboot message created by the CDF installer. As a result, the reboot message appears twice. [LCM-7594]

General

• Attempts to create a hosting connection to Azure in Citrix Studio might fail with an exception. The issue occurs due to the Microsoft changes made on Azure. A private fix is available at CTX457802. [CVADHELP-18741]

Logging display

• After a BrokerHostingPowerAction PowerShell cmdlet runs, the Studio Logging display indicates that the cmdlet failed, although the cmdlet completed successfully. As a workaround, check the result on the host. [BRK-7002]

Content redirection

• With browser content redirection enabled, attempts to open a new tab by right-clicking a hyperlink in Chrome can fail. As a workaround, select Always allow pop-ups and redirects in the Pop-ups blocked message. [LCM-7480]

Install and upgrade

• With app protection enabled, the imported app protection feature table might be removed when you upgrade from Version 1912 to Version 1912 LTSR CU1. Also, the update of the StoreFront feature might be lost. As a workaround, perform the following steps:

  1. On an upgraded CU1 Controller, reimport the xml feature table available with the CU1 download.
  2. On the StoreFront server, reenable the app protection feature.

  [LCM-7872]

Known issues in 1912 initial release

Install and upgrade

• If you already have Universal Print Server (UPS) version 19061022052 installed, upgrading UPS using the 1906.2 metainstaller does not add any new UPS functionality. After the upgrade, only the Universal Print Server version number, in Programs and Features, is changed to 19062022068. [HDX-20674]

• When you run the Citrix Virtual Apps and Desktops metainstaller, on the Diagnostics page if you click Connect without first selecting Collect diagnostic information, after you close the Connect to Citrix Insight Services dialog the Next button is disabled and you cannot move to next page. To re-enable the Next button, select and immediately deselect Collect diagnostic information. [XAXDINST-572]

• If you upgrade Studio from XenApp and XenDesktop 7.15 LTSR (7.15 Studio) to Citrix Virtual Apps and Desktops 7 1912 LTSR (1912 Studio), then uninstall 1912 Studio and reinstall 7.15 Studio, studio fails to launch with error “‘Cannot load windows PowerShell snap-in PvsPsSnapIn error’ occurred in studio.” To solve this issue, before reinstalling 7.15 Studio, manually delete PvsPsSnapIn.dll under C:\Program Files\Citrix\PowerShell SDK. [XAXDINST-610]

• If you request a list of valid options for the XenDesktopServerSetup.exe command, the /no_webstudio option is listed. This option is for internal use only. Do not use it. [STUD-9701]

VDA installation

• After installing a VDA and before restarting the machine, a Citrix Files error message appears: “Incompatible .NET Framework, shutting down. Install one of the KBs listed on this Known Issue page to resolve:..” As a workaround, before VDA installation, install KB4054856 on top of NDP471-KB4033342-x86-x64-AllOS-ENU.exe. [LCM-7563]

General

• When MCS creates non-persistent machines in AWS, the DeleteOnTermination flag is set to True. However, upon power cycling, MCS re-creates new EBS volumes and swaps it with the old one which changes the DeleteOnTermination flag to False. [PMCS-4953]

• In Citrix Hypervisor, after installing a new VDA the Citrix Desktop Service erroneously sets the XenTools registry value to UTC. The service does not verify the system time, leading to a connection failure resulting in machines existing in an unregistered state. This issue is temporary. The VDA corrects the system time when it synchronizes from various sources. The current fix sets the XenTools registry value to UTC only if the operating system time is UTC, resulting in no mismatch. [PMCS-5425]

• If you use the hypervisor to delete a virtual machine provisioned using Citrix Virtual Apps and Desktops, you may not be able to add the machine to the catalog because the base disk is also deleted as part the virtual machine deletion process. [PMCS-8591]

• Using a template to provision a catalog is considered an experimental feature. When using this method, virtual machine preparation may fail. As a result, the catalog cannot be published using the template. [PMCS-602]

• If you try to add a protected app to your Favorites, this message might appear, “Your apps are not available at this time…” When you then click OK, this message appears, “Cannot add app.” After you switch to the Favorites screen, the protected app is listed there, but you can’t remove it from Favorites. [WSP-5497]

• Each time you upload a compressed file using Citrix Workspace app for HTML5 on an end-to-end SSL using either Chrome or Safari browser, session reliability might start, eventually creating an unusable session. To resolve this issue, relaunch the session. To re-enable file transfer, log off from the current session. [HDX-22106]

• After installing the Skype for Business Web App Plug-in, webcams might not be enumerated and meeting pages on Firefox might not refresh automatically. [HDX-13288]

• Upgrading the VDA to version 1906 automatically installs the new MCS I/O driver if it was not previously installed. As a result, target devices fail to boot in read only mode. Citrix recommends that you do not install updated MCS I/O functionality and Citrix Provisioning in the same Windows environment. [PVS-4151]

• When you start an application from StoreFront, the application might not start in the foreground, or the application is in the foreground but might not have focus. As a workaround, click the icon in the task bar to bring the application to the front or in the application screen to bring it to focus. [HDX-10126]

• When you connect to a new session, disconnect, and then reconnect to the same session, your desktop icons might flicker. As a workaround reset the user profile, log off the session, and log on again. [HDX-15926, UPM-1362]

• When using Windows 10 1809 LTSC, VCLibs dependencies fail to install. [HDX-16754]

• The combo box might not display properly when a user selects a combo box that is already in focus on the host. As a workaround, select another UI element and then select the combo box. [HDX-21671]

• When you attempt to reconnect to a session, the desktop might fail to load and a gray window might appear. The issue occurs with VDA Version 1909 running on Microsoft Windows Server 2019. [HDX-21804]

• You have enabled Local App Access. If you start a Windows 2012 R2 VDA session, disconnect and reconnect the session, and then start a local application and maximize it, the VDA taskbar might truncate the application. [HDX-21913]

• When both IPv4 and IPv6 addressing is configured in your network, resources in a delivery group may not be accessible when the delivery group uses a Broker Access Policy rule configured to allow IPv4 address filtering only. To ensure all resource filtering behaves as expected, configure the Broker Access Policy rule to include both client IPv4 and IPv6 addresses. [WADA-7776]

  For example, to set rules allowing IPv4 and IPv6 addresses via ‘direct to StoreFront’ and ‘Citrix Gateway’ access, use PowerShell such as:

   Set-BrokerAccessPolicyRule -Name "Apps_Direct" -IncludedClientIPFilterEnabled $True -IncludedClientIPs @("10.0.0.1","2001::3")
   Set-BrokerAccessPolicyRule -Name "Apps_AG" -IncludedClientIPFilterEnabled $True -IncludedClientIPs @("10.0.0.1","2001::3")