Fixed issues 编辑

The following issues have been fixed since Version 7.14.1:

Fixed issues compared to 7.14.1

Fixed issues compared to 7.6 LTSR CU4

Fixed issues compared to 7.14.1

Citrix Director

• When navigating to the Trends > Failures > Connection tab in Citrix Director, the following error message might appear:

  “Unexpected error. Check your network connection or view Director server event logs for further information.” [LC7755]

• Attempts to view policy information for certain sessions in Citrix Director can fail and the following error message appears:

  “Cannot retrieve the data” [LC8207]

Citrix Policy

• Group Policy Objects that contain both Citrix and Microsoft settings might not be enforced. This issue occurs when the extension unit in the list contains more than two GUIDs. [LC7533]

Citrix Studio

• Attempts to add computer accounts to new or existing machine catalogs might fail when using GUI mode instead of using PowerShell commands. The issue occurs when the directory searcher tool does not bind the correct object while finding the NetBIOS name.

  For example, if the domain name is xyz.ad.airxyz.aa and the NetBIOS name is xyz-Ad, the NetBIOS name is accepted as xyz instead of xyz-Ad when using GUI mode. As a result, the machine account cannot be added for both existing and new computer accounts. [LC6679]

• After upgrading Citrix Delivery Controller to Version 7.12, attempts to add machines from Citrix Provisioning Services (PVS) to a catalog might fail in a multi-domain environment. The issue occurs when PVS does not return the domain name along with the device name. When Citrix Studio searches for the account name in the local domain, the account cannot be found. [LC6818]

• Attempts to publish App-V applications might fail. [LC7421]

• When an administrator attempts to add an App-V application from an isolation group to the Delivery Group or attempts to create an isolation group, the following error message might appear in Citrix Studio:

  “An unknown error occurred.” [LC7594]

• Attempts to add machines to a Delivery Group by using the “NETBIOS” name for user association might fail. Instead, the domain name might appear. The issue occurs when the NETBIOS name uses the wrong URL. [LC7830]

Controller

• After upgrading Citrix Delivery Controller to Version 7.12, attempts to add machines from Citrix Provisioning Services (PVS) to a catalog might fail in a multi-domain environment. The issue occurs when PVS does not return the domain name along with the device name. When Citrix Studio searches for the account name in the local domain, the account cannot be found. [LC6818]

• Attempts to add machines to an existing Machine Creation Services catalog might not follow the round robin method for multiple storages that can be selected to accept the new machines. [LC7456]

• Attempts by custom administrators to create an isolation group might fail and the following error message appears:

  “You do not have the permissions required to complete this request. For more information, contact your XenDesktop Site administrator.” [LC7563]

• When an administrator attempts to add an App-V application from an isolation group to the Delivery Group or attempts to create an isolation group, the following error message might appear in Citrix Studio:

  “An unknown error occurred.” [LC7594]

• Attempts to disable TLSv1.0 on Citrix Delivery Controller can cause loss of communication to the VMware vCenter hypervisor. [LC7686]

• Attempts to add machines to a Delivery Group by using the “NETBIOS” name for user association might fail. Instead, the domain name might appear. The issue occurs when the NETBIOS name uses the wrong URL. [LC7830]

Profile Management

• When you attempt to open files in a profile with Profile Streaming enabled, the file might appear empty after you log on. [LC6996]

• Servers might experience a fatal exception, displaying a blue screen, on upmjit.sys with bugcheck code 0x135. [LC7841]

• UserProfileManager.exe might exit unexpectedly when you log on to a VDA. [LC7952]

StoreFront

• Attempts to reconnect to disconnected sessions might fail within a multi-Site aggregation deployment. As a result, you might receive a second instance of the same resource. [LC7453]

• When a part of the source of an aggregated application is disabled, the application might be unexpectedly hidden from the end user. [LC7675]

• Attempts to disable the “Account Self-Service” option in StoreFront might not take effect, even though the option appears as disabled. [LC7744]

• Attempts to remove shared authentication from Stores in StoreFront might result in the following error message while saving the changes:

  “An error occurred while saving your changes.” [LC7781]

Universal Print Server

Client

• The print spooler service might become unresponsive and, as a result, Universal Printing does not work. The issue occurs when a timeout is reached while waiting for a transaction response from the spooler service. [LC5209]

• When using Profile Management, changes made to Citrix Universal Print Server printers (adding, removing, and renaming) in a session on one server might not be correctly reflected in subsequent sessions on another server. [LC7645]

Server

• Attempts to print a document might fail and the following error message appears:

  “Windows cannot print due to a problem with the current printer setup.” [LC6825]

• When using certain printers, Microsoft Notepad might display the message “The handle is invalid” and fail to print. The issue occurs if “Use only printer model specific drivers” is configured in the Citrix policy “Universal print driver usage” and if “Enabled with no fallback to Windows’ native remote printing” is configured in the Citrix policy “Universal Print Server enable.” [LC7623]

VDA for Desktop OS

Installing, Uninstalling, Upgrading

• After upgrading the VDA from Version 5.6.400 to Version 7.9, restarting the VDA can cause the mirror drivers installed by the previous version to be left behind. [LC6295]

• Certain WMI classes might be renamed after installing Version 7.12 or 7.13 of the VDA on a non-English version of the Microsoft Windows operating system. [LC7555]

• Certain WMI classes might be renamed after installing Version 7.12 or 7.13 of the VDA on a non-English version of the Microsoft Windows operating system. [LC7587]

Printing

• The Citrix Print Manager service (cpsvc.exe) might become unresponsive and exit unexpectedly when new users log on. [LC6933]

• After upgrading the VDA from Version 7.9 to Version 7.12 or later, attempts to print from Microsoft Internet Explorer by using the Citrix Universal Print Driver might print only to tray 1 instead of printing to the tray that is selected. [LC7463]

Session/Connection

• When multiple webcams of the same model are installed on the VDA for Desktop OS, only the latest webcam might be recognized by the session and mapped. [LC5008]

• A removable client drive might not be returned by the WFAPI SDK on the VDA for Desktop OS. [LC6877]

• The window positions might not be retained when you reconnect to a published desktop session and are using multiple monitors. [LC7644]

• When you switch sessions between multiple monitors in full-screen mode with legacy graphics mode enabled and without Desktop Viewer configured, only one monitor might appear to be running the session. [LC7907]

Smart Cards

• Occasionally, removing a smart card reader might not trigger the user session to get locked, even though smart card removal is configured to lock the user session. [LC7411]

System Exceptions

• VDAs might experience a fatal exception, displaying a blue screen, on vd3dk.sys with bugcheck code 0X00000050. [LC6833]

• VDAs might experience a fatal exception, displaying a blue screen, on picadm.sys with bugcheck code 0x7F while shutting down a session. [LC7545]

• The Service Host (svchost.exe) process might experience an access violation and exit unexpectedly. The issue occurs because of the faulting module, scardhook64.dll. [LC7580]

• Servers might experience a fatal exception, displaying a blue screen, on vdtw30.dll with stop code 0xc0000006. [LC7608]

• VDAs might experience a fatal exception, displaying a blue screen, on tdica.sys with a bugcheck code. [LC7632]

• This fix addresses a memory issue with the wdica.sys file that can cause servers to exit unexpectedly. [LC7666]

User Experience

• This fix provides improved support for sounds that play for a short period of time when using high quality audio.

  Note:

  • This fix does not take effect in sessions running on Windows Server 2008 R2.
  • For this fix to work, you must use Citrix Receiver 4.4 for Windows Long Term Service Release (LTSR) CU5 or later versions and the VDA version of XenApp and XenDesktop 7.6 LTSR CU4 or later. [LC5842]

• When performing an insert operation between two Microsoft Excel 2010 worksheets running on a Version 7.9 VDA, the Excel window might become unresponsive. [LC7481]

• In a multi-monitor environment, define the external monitor as the “Main Display” of Windows and position it to the right of the secondary laptop or tablet monitor in the display settings of the Control Panel. When you start a published application that appears on the external monitor and move this application to the tablet monitor or a laptop that is attached to the external monitor, opening or closing the lid of the tablet or a laptop can cause the published application to become black.

  To enable the fix, you must set the following registry key value on the VDA:

  HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Ica\Thinwire; Name: EnableDrvTw2NotifyMonitorOrigin; Type: REG_DWORD; Value: 1 (to enable) and 0 (to disable; 0 is the default value). By default, the registry value is missing. [LC7760]

User Interface

• URL shortcut icons might be displayed as blank when using a touch-optimized desktop. [LC6663]

• If you open a spreadsheet with more than one workbook in Excel 2010, the taskbar displays only the most current workbook. [LC7557]

VDA for Server OS

Installing, Uninstalling, Upgrading

• Certain WMI classes might be renamed after installing Version 7.12 or 7.13 of the VDA on a non-English version of the Microsoft Windows operating system. [LC7555]

• Certain WMI classes might be renamed after installing Version 7.12 or 7.13 of the VDA on a non-English version of the Microsoft Windows operating system. [LC7587]

Printing

• The Citrix Print Manager service (cpsvc.exe) might become unresponsive and exit unexpectedly when new users log on. [LC6933]

• After upgrading the VDA from Version 7.9 to Version 7.12 or later, attempts to print from Microsoft Internet Explorer by using the Citrix Universal Print Driver might print only to tray 1 instead of printing to the tray that is selected. [LC7463]

Server/Site Administration

• The following error message might appear for child domain users while launching an application through Web Interface or StoreFront:

  “You have not been granted access to this published application.” [LC7566]

Session/Connection

• When multiple webcams of the same model are installed on the VDA for Desktop OS, only the latest webcam might be recognized by the session and mapped. [LC5008]

• Attempts to reconnect to a session can fail intermittently and cause the VDAs for Server OS to go into “Initializing” status. The issue occurs when the VDA is registered again with a Delivery Controller. [LC6647]

• Active sessions might be disconnected on the XenApp servers when the Delivery Controller loses connectivity. The issue occurs when VDAs fails to track the status of sessions that move from “pre-launch” to “active” status correctly. As a result, when the Delivery Controller is restarted, it attempts to clear the resources from the VDAs, and sessions in the pre-launch status are disconnected or logged off while the applications are being actively used. [LC6819]

• When you launch a published application on Microsoft Windows Server 2016, a black screen might appear for several seconds before the application becomes visible. [LC7947]

System Exceptions

• VDAs might experience a fatal exception, displaying a blue screen, on picadm.sys with bugcheck code 0x7F while shutting down a session. [LC7545]

• The Service Host (svchost.exe) process might experience an access violation and exit unexpectedly. The issue occurs because of the faulting module, scardhook64.dll. [LC7580]

• Servers might experience a fatal exception, displaying a blue screen, on vdtw30.dll with stop code 0xc0000006. [LC7608]

• VDAs might experience a fatal exception, displaying a blue screen, on tdica.sys with a bugcheck code. [LC7632]

• This fix addresses a memory issue with the wdica.sys file that can cause servers to exit unexpectedly. [LC7666]

User Experience

• This fix provides improved support for sounds that play for a short period of time when using high quality audio.

  Note:

  • This fix does not take effect in sessions running on Windows Server 2008 R2.
  • For this fix to work, you must use Citrix Receiver 4.4 for Windows Long Term Service Release (LTSR) CU5 or later versions and the VDA version of XenApp and XenDesktop 7.6 LTSR CU4 or later. [LC5842]

• When performing an insert operation between two Microsoft Excel 2010 worksheets running on a Version 7.9 VDA, the Excel window might become unresponsive. [LC7481]

• In a multi-monitor environment, define the external monitor as the “Main Display” of Windows and position it to the right of the secondary laptop or tablet monitor in the display settings of the Control Panel. When you start a published application that appears on the external monitor and move this application to the tablet monitor or a laptop that is attached to the external monitor, opening or closing the lid of the tablet or a laptop can cause the published application to become black.

  To enable the fix, you must set the following registry key value on the VDA:

  HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Ica\Thinwire; Name: EnableDrvTw2NotifyMonitorOrigin; Type: REG_DWORD; Value: 1 (to enable) and 0 (to disable; 0 is the default value). By default, the registry value is missing. [LC7760]

User Interface

• URL shortcut icons might be displayed as blank when using a touch-optimized desktop. [LC6663]

• If you open a spreadsheet with more than one workbook in Excel 2010, the taskbar displays only the most current workbook. [LC7557]

Virtual Desktop Components - Other

• Attempts to publish App-V applications might fail. [LC7421]

• Attempts to launch App-V applications in Single Admin mode might fail. The issue occurs when the application name contains special characters. [LC7897]

Fixed issues compared to 7.6 LTSR CU4

Citrix Director

• Citrix Director with Windows Integrated Authentication (WIA) might not work with a Kerberos Constrained Delegation setup. [LC5196]

• A “System unavailable” error occurs after attempting to log onto Citrix Director. [LC5385]

• Citrix Director might not display session details. The issue occurs when using Published content as the application type. [LC6577]

Citrix Policy

• The Citrix Policy processing might stop responding, which causes user sessions to become unresponsive. When this occurs, connection requests to Receiver and Remote Desktop (RDP) fail. [LA4969]

• On systems with Fix LC1987 (GPCSExt170W2K8R2X64006 or its replacement) installed, Active Directory (AD) policies that contain both Citrix and Microsoft settings might not be enforced.

  Note: This fix addresses the issue for AD policies you create after installing this update. It also addresses it for existing policies where Citrix settings were configured before Microsoft settings. It does not address it for existing AD policies where Microsoft settings were configured before Citrix settings. For those AD policies, you must open the affected policies and save the Citrix settings. [LC2121]

• With this feature enhancement, the Citrix Group Policy Engine generates additional event log messages while processing Citrix policies. [LC3664]

• When upgrading from 7.6 to either versions 7.8 or 7.9, certain color schemes in Citrix Studio might appear too dark for text to display properly. [LC5690]

• After installing the Citrix Federated Authentication Service, attempts to configure the Security Access Control Lists on the StoreFront server under User Rules can cause the Configuration window to become unresponsive. [LC5788]

• The CPU and memory consumption of Microsoft Excel might spike while opening a file with the XLSM file extension with macros. As a result, attempts to open the file fail. [LC6142]

• Group Policy Objects that contain both Citrix and Microsoft settings might not be enforced. This issue occurs when the extension unit in the list contains more than two GUIDs. [LC7533]

Citrix Studio

• When multiple users create policies in a multiple studio session, the latest policy created overwrites the earlier policy when Citrix Studio is refreshed. [LA5533]

• Citrix Studio might not recognize the XenDesktop App Edition License and the following error message appears:

  “Can’t find a valid license No suitable licenses are available. Check the license server address and that the product edition and model are correct.” [LC0822]

• When attempting to add cross-domain users to a Delivery Group, Citrix Studio resolves their actual domain to the local domain account. [LC1886

• Attempts to publish an application in Citrix Studio 7.7 by using command line arguments that contain quotations (“) might result in an error message. [LC4525]

• Citrix Studio might offer the Catalog Rollback option even when no catalog update has been done. Opting to roll back causes an exception. [LC4791]

• Attempts to add machines to a Machine Catalog from Citrix Studio can fail and an error message appears. The issue does not occur when you add machines using the XenDesktop Setup wizard. [LC5030]

• When two applications have the same ApplicationID, refreshing App-V applications can cause Citrix Studio to set the App-V package name incorrectly. [LC5261]

• When a Delivery Controller goes offline or becomes otherwise unavailable, Citrix Studio might operate slowly. [LC5335]

• After upgrading XenApp or XenDesktop to 7.7 from 7.6, a prompt to upgrade might occasionally appear in Citrix Studio. [LC5478]

• When you close and then attempt to reopen an instance of Version 7.9 of Citrix Studio that is configured with App-V servers containing many packages, Studio remains in an expanding state and fails to open. [LC5643]

• Using Citrix Studio, you can add only one App-V server to a Site. To add additional App-V servers to the Site, you must use PowerShell. [LC5767]

• After upgrading Citrix Studio from 7.8 to 7.9, applications you add after the upgrade appear with no package name or version. [LC5958]

• Adding an application through the Applications node in Citrix Studio might cause an error where the application is not added. As a workaround, use the Delivery Group node to add applications. [LC5975]

• When trying to create a new XenDesktop Site through Citrix Studio and pointing to the SQL AlwaysOn Listener, the following error might appear:

  “The replica server <servername> could not be contacted. Check the database status on the SQL server. Ensure database server allows remote connections and the firewall is not blocking connections.” [LC6010]

• If you remove an existing published App-V package from Citrix Studio and attempt to add a different version of the same App-V package with the same name and publishing location to the Delivery Group, the package might enumerate with a red exclamation point and the following error message appears:

  “Failed to load application data for the application “APPLICATION NAME”” [LC6254]

• Attempts to add a Delivery Controller in a mirrored database setup by using the option to add an additional controller from Citrix Studio and the PowerShell command “Add-XDController” might fail. [LC6563]

• Attempts to add computer accounts to new or existing machine catalogs might fail when using GUI mode instead of using PowerShell commands. The issue occurs when the directory searcher tool does not bind the correct object while finding the NetBIOS name.

  For example, if the domain name is xyz.ad.airxyz.aa and the NetBIOS name is xyz-Ad, the NetBIOS name is accepted as xyz instead of xyz-Ad when using GUI mode. As a result, the machine account cannot be added for both existing and new computer accounts. [LC6679]

• After upgrading Citrix Delivery Controller to Version 7.12, attempts to add machines from Citrix Provisioning Services (PVS) to a catalog might fail in a multi-domain environment. The issue occurs when PVS does not return the domain name along with the device name. When Citrix Studio searches for the account name in the local domain, the account cannot be found. [LC6818]

• When upgrading a XenApp Site, the license model might change from XenApp to XenDesktop unexpectedly. [LC6981]

• The “Start-Transcript” command might fail for “Get-XDSite” and other XenDesktop high level administrative PoSH commands when run in PowerShell 5. [LC7006]

• When an administrator attempts to add an App-V application from an isolation group to the Delivery Group or attempts to create an isolation group, the following error message might appear in Citrix Studio:

  “An unknown error occurred.” [LC7594]

• Attempts to add machines to a Delivery Group by using the “NETBIOS” name for user association might fail. Instead, the domain name might appear. The issue occurs when the NETBIOS name uses the wrong URL. [LC7830]

Controller

• Deploying virtual machines using Machine Creation Services in Citrix Studio fails, displaying the following error message:

  “Error Id: XDDS:0F7CB924.” [LC4930]

• When users attempt to deleted the pooled catalog created on XenServer and then run the catalog update, the base disks are not removed from storage and the number of base disks might increase. [LC0577]

• Session reliability cannot be disabled by using either Active Directory Group Policy Object (GPO) or through Citrix Studio on VDA 7.x sessions that start by using XenDesktop 5.6 Desktop Delivery Controller (DDCs). [LC0878]

• When creating a new pooled machine by using the Machine Creation Services from a master image with custom VMX and nvram settings, the settings are not copied to the new virtual machines. [LC0967]

• The PrepareSession task that is executed by the Broker Service might time out when used in XenDesktop 5.6 environments, causing StoreFront to fail. [LC1055]

• This fix addresses a timing issue that can occur when the hypervisor is congested while formatting a PvD disk volume during initial machine creation. [LC3275]

• Creating virtual machines with Machine Creation Services using VMware vSphere 6.0 and vSAN 6 storage might fail. [LC4563]

• The WaitForTask response causes the exception VimApi.MissingProperty which does not allow the update of Machine Catalogs. [LC4573]

• Attempts to add machines to a Machine Catalog from Citrix Studio can fail and an error message appears. The issue does not occur when you add machines using the XenDesktop Setup wizard. [LC5030]

• After upgrading the VDA to Version 7.8, attempts to perform the update inventory operation might fail and the following error message appears:

  “Update inventory failed with :An internal error occurred Error code 0x2.” [LC5051]

• Extraneous characters might appear at the end of “Service Display Name” and “Service description” of certain Citrix services installed on a Japanese operating system. [LC5208]

• When two applications have the same ApplicationID, refreshing App-V applications can cause Citrix Studio to set the App-V package name incorrectly. [LC5261]

• After upgrading XenApp or XenDesktop to 7.7 from 7.6, a prompt to upgrade might occasionally appear in Citrix Studio. [LC5478]

• An ampersand (&) in the title of an application causes the StoreFront XML to become corrupt and display no applications or icons. [LC5505]

• When you close and then attempt to reopen an instance of Version 7.9 of Citrix Studio that is configured with App-V servers containing many packages, Studio remains in an expanding state and fails to open. [LC5643]

• After upgrading to XenDesktop 7.9, logging on might occasionally fail due to the NetScaler broker’s not sending credentials correctly. [LC5753]

• Using Citrix Studio, you can add only one App-V server to a Site. To add additional App-V servers to the Site, you must use PowerShell. [LC5767]

• After installing the Citrix Federated Authentication Service, attempts to configure the Security Access Control Lists on the StoreFront server under User Rules can cause the Configuration window to become unresponsive. [LC5788]

• Changing the SDK port of Flexcast Management Architecture services such as Analytics, Broker, Log, etc. causes Citrix Studio to not connect properly. [LC6005]

• When trying to create a new XenDesktop Site through Citrix Studio and pointing to the SQL AlwaysOn Listener, the following error might appear:

  “The replica server <servername> could not be contacted. Check the database status on the SQL server. Ensure database server allows remote connections and the firewall is not blocking connections.” [LC6010]

• Citrix Director might show a number of unregistered machines on the dashboard that does not match with the report on the Trends page. [LC6184]

• The Monitoring Service fails to insert new session data into the Monitoring database when the Load Evaluator Index policy is enabled. This can lead to Citrix Director not displaying up-to-date information for sessions such as Logon Duration, Current Number of Active Sessions, and others. While the problem shows in Citrix Director, it is caused by an issue in the Delivery Controller. The current version of the Controller addresses the issue. [LC6241]

• Attempts to remove a hosting unit can cause the replication of AppDisks on any other hosting unit to fail. As a result, the machines in the Delivery Group with AppDisks fail to start. [LC6433]

• After restarting the Citrix Monitoring Service or the Citrix Delivery Controller, event id 1013 might appear:

  “Initial database housekeeping failed with: System.NullReferenceException: Object reference not set to an instance of an object.”

  The issue occurs when the Citrix Monitor Service is stopping. [LC6438]

• Attempts to use certain third-party applications such as RayStation on a Citrix Delivery Controller might fail and the following error message appears:

  “The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.” [LC6552]

• Attempts to add a Delivery Controller in a mirrored database setup by using the option to add an additional controller from Citrix Studio and the PowerShell command “Add-XDController” might fail. [LC6563]

• Attempts to delete MCS catalogs on VMware VSANs might fail. [LC6691]

• Memory consumption of the Monitoring Service can spike, causing servers to be unresponsive. [LC6705]

• After upgrading Citrix Studio from previous versions or when you do a fresh install of Citrix Studio Version 7.12, the Delivery Controller might cause Citrix Studio to be stuck in a mandatory upgrade loop. [LC6737]

• When using version 7.12 of Machine Creation Services to create VMs, XenTools fails to be installed, preventing graceful shutdown of the VMs. [LC6769]

• After upgrading Citrix Delivery Controller to Version 7.12, attempts to add machines from Citrix Provisioning Services (PVS) to a catalog might fail in a multi-domain environment. The issue occurs when PVS does not return the domain name along with the device name. When Citrix Studio searches for the account name in the local domain, the account cannot be found. [#LC6818]

• Permissions to publish App-V packages might be denied for administrators who do not have full permission with the following exception:

  “Citrix.Console.Models.Exceptions.PermissionDeniedException: You do not have the required permissions to perform this operation.” [LC6897]

• The HighAvailabilityService.exe process might consume high memory. [LC6918]

• When upgrading a XenApp Site, the license model might change from XenApp to XenDesktop unexpectedly. [LC6981]

• The “Start-Transcript” command might fail for “Get-XDSite” and other XenDesktop high level administrative PoSH commands when run in PowerShell 5. [LC7006]

• This fix addresses a memory issue in Citrix Host Service. [LC7516]

• Attempts by custom administrators to create an isolation group might fail and the following error message appears:

  “You do not have the permissions required to complete this request. For more information, contact your XenDesktop Site administrator.” [LC7563]

• When an administrator attempts to add an App-V application from an isolation group to the Delivery Group or attempts to create an isolation group, the following error message might appear in Citrix Studio:

  “An unknown error occurred.” [LC7594]

• Attempts to install the VDA on Microsoft Windows Server might fail when the Microsoft Remote Desktop Session Host role service is already installed. [LC7680]

• Attempts to disable TLSv1.0 on Citrix Delivery Controller can cause loss of communication to the VMware vCenter hypervisor. [LC7686]

• Attempts to add machines to a Delivery Group by using the “NETBIOS” name for user association might fail. Instead, the domain name might appear. The issue occurs when the NETBIOS name uses the wrong URL. [LC7830]

Licensing

• The license server might fail the Payment Card Industry (PCI) compliance scan for clickjacking because the “X-Frame-Options” header type is not set. [LC1983]

• Attempts to add a domain group whose name contains more than 32 characters might fail. [LC1986]

• If the NetBios domain name contains an ampersand (&), attempts to open the Licensing tab in Studio might fail with the following error message:

  “Citrix license server unavailable” [LC2728]

Profile Management

• Attempts by certain third party applications to rename or move files during logon or logoff might fail. For example, if there are files file0, file1, and file2 in the local profile, attempts to rename file2 to file3, file1 to file2, and file0 to file1 might fail during the logoff process if file2 already exists on the pending area or user store. [LC0465]

• When users log off, the Profile Management (UserProfileManager.exe) service occasionally fails. [LC0625]

• The “LOGON DURATION” panel in the Performance Monitor (Perfmon) counter might record the data for user logons that are not managed by the Profile Management. [LC0779]

• The Profile Management might not synchronize the files with the user store after a certain period of time. [LC1338]

• After enabling the following logging options, no debugging information is recorded in the log file:
  • Policy: Active Directory actions
  • Policy: Policy values at logon and logoff
  • Policy: Registry difference at logoff [LC2003]

• If a user enables Profile Versioning as described in https://support.microsoft.com/en-us/kb/2890783, the Profile Management might not migrate for the following reasons:

  • The Microsoft roaming profile is created with the extension “V4”
  • The UPM profile was not migrated and created from the “Default user” template. [LC2427]

• After resetting the user profile in Desktop Director, folder redirection does not work when users log on for the first time. Folder redirection does work when users subsequently log on. [LC2602]

• The Profile Management (UserProfileManager.exe) service might close unexpectedly. [LC2979]

• After applying Fix LC0625, the Profile Management (UserProfileManager.exe) service might close unexpectedly. [LC3058]

• On Windows 8.1, attempts to download files using Internet Explorer 11 fail if Enhanced Protected Mode is enabled. [LC3464]

• File locks can occur in Profile Management during the logoff process with the following error message:

  “The process cannot access the file because it is being locked by another process.”

  Attempts to delete files locked by Profile Management might fail until the locks are released. [LC3532]

• Profile Management can exit unexpectedly while the user device is in the process of shutting down. [LC3626]

• XenApp servers might become unresponsive in the farm until the server is restarted. [LC4318]

• When attempting to log on to a XenApp 7.7 server using RDP, the server might become unresponsive on the welcome screen. [LC5169]

• After upgrading a VDA from Version 7.6.1000 or earlier to Version 7.7 or later, attempts to delete, repair, or reinstall Profile Management or the VDA might fail. [LC5207]

• When logging off, Profile Management occasionally locks files/folders on the server, causing applications to fail to launch. Locally cached profiles also do not get deleted. [LC5266]

• Profile Management occasionally locks files in user profiles. When this happens, users receive a temporary profile while trying to reconnect until the lock on their profile is released. [LC5278]

• Locally cached profiles might not delete when users log off. [LC5470]

• When the license server is offline, files using the user redirection folder on the server are lost. [LC5595]

• Users’ files are lost when the license trial period ends without renewal. [LC5775]

• Profile Management might incorrectly raise a “NetworkDetection” flag indicating that the network might be lost. This fix introduces an extra check to ensure that the network is not available instead of temporarily being unavailable. [LC5943]

• Occasionally, the user logon screen becomes unresponsive on Windows Server 2012 R2. [LC6149]

• Attempts to migrate roaming profiles into Profile Management might fail. The issue occurs when an incorrect version number is added to the profile. [LC6150]

• The application icons might appear as grayed out when you attempt to copy the icons from the Profile Management user profile store through a WAN connection. [LC6152]

• File type associations might fail to roam in Profile Management enabled sessions running on Microsoft Windows 10 and Windows Server 2016. [LC6736]

• With the “Delete local cache at logoff” policy enabled on Microsoft Windows 10 or Windows Server 2016, the NTUSER.DAT file might fail to be deleted at logoff, causing another local profile to be created at the next logon. [LC6765]

• When using Profile Management on Microsoft Windows Server 2016 and usrclass.dat is included, the Start menu might not work. [LC6914]

• When you attempt to open files in a profile with Profile Streaming enabled, the file might appear empty after you log on. [LC6996]

• Profile Management can cause a black screen to appear when you attempt to launch a Microsoft Windows 10 session. With this fix, you must configure the policy “Directories to synchronize” and add the folder “*AppData\Local\Microsoft\Windows\Caches*.” [LC7596]

Provisioning Services

Console Issues

• With this fix, the “Schedule the next vDisk update to occur on” option and “Apply vDisk updates as soon as they are directed by the server” option are no longer available for Provisioning Services. [LA4166]

• Attempts to create virtual machines through the XenDesktop setup wizard might fail in a non-English Microsoft System Center Virtual Machine Manager (SCVMM) environment. [LC5451]

• Attempts to create an ISO with the New-BootDeviceManager PowerShell script can fail and the following error message appears: “ISOFileName must be called with the name of the new ISO file to create.” [LC5559]

• When using clustered volume storage, the Streamed VM Setup wizard does not honor the volume selection and can create target devices on random volumes. [LC5890]

• Attempts to close the Provisioning Services Console after running the XenDesktop Setup wizard or the Streamed VM Setup wizard can result in an exception. [LC6048]

• After upgrading to PVS 7.11 from version 7.6, users in other domains might not be able to log on to the console. [LC6216]

• Server communication time out. In some cases, login times can become excessively long (for example, greater than 2 minutes). This can cause server timeout issues between the PVS Console and the SoapServer. By default, the timeout for such connections is 2 minutes. However, you can increase this value by modifying the registry value HOTKEY_LOCAL_MACHINE\Software\Citrix\ProvisioningServices ConnectionTimeout=<timeout in seconds>. If the login time is greater than approximately 4 minutes, users will also experience timeouts from the Microsoft MMC containing the PVS Console (these timeouts can be dismissed).

  One cause for this issue is unreachable domains in Active Directory, where there is a 30 second timeout applied each time an attempt to connect to an unreachable domain is made. This can quickly add up to several minutes if there are multiple unreachable domains. In general, unreachable domains are created by adding a test or experimental domain to Active Directory, then removing it at a later time. Although the domain is gone, it is still reported by Active Directory when enumerating domains or authorization groups.

  Unreachable domains can also be caused by a domain controller being temporarily shut down and disconnected from the network, so not all unreachable domains should be blacklisted.

  The best way to determine whether there are unreachable domains is by looking at the CDF trace for the PVS_DLL_ADSUPPORT module and checking for “Unreachable Domain” and “Server Referral” errors. If any of these are found, check the domains to ensure that they are not in use any more, and if not, add the domain names to the blacklist.

  The blacklist is a JSON format file called “%ProgramData\Citrix\Provisioning Services\blacklist.json”. For example:

   {
  
   "Domains":
  
   [
  
   "sub.xs.local",
  
   "sb.xs.local"
  
   ]
  
   }
   <!--NeedCopy-->