Issues Fixed in This Release

Citrix XenDesktop 7.x

Product: Citrix XenDesktop
Current Product Version: XenDesktop 7.x

The following issues were fixed in XenDesktop 7.x:

VDA (Desktop OS) | VDA (Server OS)

XenDesktop 7.6

XenDesktop 7.5

XenDesktop 7.1

XenDesktop 7

XenDesktop 7.6

Compared to: XenDesktop 7.5

XenDesktop 7.6 contains all fixes that were included in XenDesktop 7, 7.1, and 7.5, plus the following, new fixes:

Citrix Studio

1. Citrix Studio might incorrectly show the state of the VDA as "Unregistered" even if the VDA is registered.

   [#LA4681]

2. Attempts to launch a session using a custom virtual driver can fail.

   To enable the fix, you must create the following registry key:

   • On 32 bit Windows
     HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client
     Name: VdLoadUnLoadTimeOut
     Type: REG_DWORD
     Data: Any value in seconds
   • On 64 bit Windows
     HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\Citrix\ICA Client
     Name: VdLoadUnLoadTimeOut
     Type: REG_DWORD
     Data: Any value in seconds

   [#LA4711]

3. Attempts to include the Applications > License ID column in Citrix Studio Search might fail with the following error message:

   "The given key was not present in the dictionary."

   [#LA5677]

4. The Citrix "Server idle timer interval" policy in Citrix Studio does not work for Windows Server 2012 VDAs.

   [#LC0058]

5. This fix addresses a memory issue in an underlying component.

   [#LC0047]

Desktop Director 7.6.100

1. Non-ASCII characters do not display correctly in the PDF when exported from the Trends page.

   [#485313]

2. Strings are not localized in the PDF when exported from the Trends page.

   [#496621]

3. The License Alerts panel might display "Required product license is not found" for XenApp Platinum and Concurrent Model when there are valid licenses available.

   [#507413]

4. The application-based usage grid details are not exported to the CSV file.

   [#498006]

Desktop Director 7.6

1. Desktop Director connections can time out with the following exception in the trace log:

   "XAConnector.CloseClient: exception caught: The session was closed before message transfer was complete."

   [#LA4550]

2. In VMware deployments, Version 2.x of Director reports the number of physical CPUs of VMs rather than the number of virtual CPUs.

   [#LA5851]

3. Management Framework 3.0 introduces a new local group, WinRMRemoteWMIUSers__, that you can use to prevent non-administrator roles from accessing WMI remotely.

   [#LC0010]

4. If "Log.LogToFile" is set to 0, logging continues to the file specified in Log-FileName.

   [#LC0014]

5. Logon performance data for VDAs running on German Language versions of Windows is not shown in Director.

   [#LA5505]

Group Policy Client-Side Extension

1. When reconnecting to an existing session using a different connection method than for the initial session (for example, with and without using the Access/NetScaler Gateway), Citrix policies are not reevaluated for the reconnected session.

   Note: This fix requires you to delete all entries in the following locations on the Windows Desktop OS or Windows Server OS device. Do not apply this fix unless you are affected by the issue as described:

   • Registry : HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Citrix
   • Folder: C:\ProgramData\Citrix\GroupPolicy\*.*

   [#LA5051]

Group Policy Management Experience

1. When reopening the "Printer driver mapping and compatibility" policy and pressing Settings, the "Edit Printer settings" window that appears loses focus. Additionally, when pressing Settings again, the Group Policy Editor might exit unexpectedly with an exception.

   [#LA4802]

2. The priority order of GPOs is reversed in the following scenarios:

   • After upgrading from Version 1.7 to Version 2.1 of the Citrix Group Policy Management Console.
   • After exporting GPOs from Version 1.7 or earlier of the Citrix Group Policy Management Console and importing them into Version 2.1 or later of the Citrix Group Policy Management Console. 
     Note: This fix does not address the issue for GPOs that were modified using Version 2.1 of the Citrix Group Policy Management Console; it will prevent the issue only with GPOs you modify going forward. To fix the reversed priority order of existing GPOs you modified in Version 2.1 of the Citrix Group Policy Management Console, you must manually adjust the priority order of the affected GPOs once you install this fix.

   [#LA5362]

3. Policies can be lost. This happens when the policy file is corrupted and truncated as a result of high memory consumption by AppCenter and Citrix Studio, which can occur when you modify policies in scenarios with a large number of configured policies.

   [#LA5385]

4. Attempts to rename the "Unfiltered" built-in policy set result in all changes to the policy to be lost. By design, you should not be able to rename this policy. This fix modified the user interface so that attempts to rename are no longer accommodated.

   [#LA5437]

5. When making changes to Citrix policies in Citrix Studio the following error message appears:

   "Changes made to policies outside of this console, such as in PowerShell or management tools from previous versions, resulted in a discrepancy between policies.

   The priorities for policy [PolicyA's name] and policy [PolicyB's name] interfere with each other in the "user" and "computer" components. The priorities must be assigned in the same order for both policies."

   Note:

   • This fix prevents any issues occurring with merged policies. If the error message appears before applying the fix, then you must manually adjust the priority order after installing this fix.

     For example, if two merged policies, PolicyA and PolicyB, are swapped and a user setting is added to PolicyB, the issue occurs. To prevent the issue from occurring, run the following commands on Citrix Delivery Controller:

     PS>Add-PSSnapin Citrix.Common.GroupPolicy
     PS>New-PSDrive Site â??PSProvider CitrixGroupPolicy â??Root \ -Controller localhost
     PS>cd Site:\Computer
     [Note the PolicyA's computer setting priority]
     PS> cd ..
     PS>cd Site: \User
     PS>Set-ItemProperty PolicyA -Name Priority -Value [PolicyA's computer setting priority]

   • You can configure user and computer settings in the same policy and both settings can have the same priority order. Occasionally, the priorities for the settings might be different. For example, PolicyA and PolicyB have the same user and computer settings, but the computer setting priority of PolicyA is higher than PolicyB. In this instance, configure the user setting of PolicyA to be higher than PolicyB.

   [#LC0063]

6. After editing the built-in "Unfiltered" policy, the following error message appears:

   "Changes made to policies outside of this console, such as in PowerShell or management tools from previous versions, resulted in a discrepancy between policies.

   The Enabled Flag for the "user" and "computer" components of the policy Unfiltered must have the same value."

   Note: This fix prevents any issue occurring with unfiltered policies. If the error message appears before applying the fix, you must manually enable the flag of the "Unfiltered" policy by using PowerShell commands (cmdlet) after installing this fix.

   For example, if "Unfiltered" has only computer settings configured and the Enabled flag is clear, run the following commands in Citrix Delivery Controller:

   PS>Add-PSSnapin Citrix.Common.GroupPolicy
   PS>New-PSDrive Site -PSProvider CitrixGroupPolicy -Root \ -Controller localhost
   PS>cd Site:\User
   PS>cd Site:\User\Unfiltered
   PS>Set-ItemProperty . -Name Enabled -Value True

   [#LC0068]

7. Policies can be lost. This happens when the policy file is corrupted and truncated as a result of high memory consumption by the Group Policy Management Console and the Group Policy Editor, which can occur when you modify policies in scenarios with a large number of configured policies.

   [#LC0083]

Server/Site Administration

1. Attempts to reset or restart a Hyper-V based VM from Desktop Director or Citrix Studio might fail with the following error message:

   "The Specified Method Is Not Supported."

   [#LA4105]

2. Catalog updates fail with VMware host connections with multiple storage objects. Instead an error occurs during the CopyDisk call, indicating that a file with the same name already exists.

   [#LA4669]

3. SCVMM Hyper-V local storage enumerates but machine provisioning fails unless the local storage is a shared drive.

   [#LA5693]

Session/Connection

1. In deployments that use a combination of NetScaler Gateway and StoreFront, launching two VM hosted apps on a single VDA at the same time can cause one of the apps to disconnect and then reconnect while the other VM hosted app fails to launch.

   [#LA4925]

Universal Print Server

1. Attempts to print using the Universal XPS Printer Driver can cause the UPServer.exe process to exit unexpectedly.

   [#LA4052]

2. When using the Universal Print Server and printing from Microsoft Office applications, the UPServer.exe process might exit unexpectedly, causing the print operation to fail.

   [#LA4106]

3. The XpsNativePrintHelper.exe process on the Universal Print Server might become unresponsive when XPS print jobs fail.

   [#LA4398]

4. This enhancement improves the scalability and reliability of the Universal Print Server. To enable this enhancement in its entirety, you must install both a Universal Print Server and a Universal Print Server Client hotfix that contains Fix #LA5186.

   [#LA5186]

5. The Citrix XTE Server might exit unexpectedly or fail to process Universal Print Server Client requests. The issue occurs as a result of incorrectly set thread values.

   With this fix, the Citrix XTE Server enforces the following values:

   • Default value of 5000 for the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\XTEConfig\MaxThreads registry value.
   • Minimum value of 150 for the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\XTEConfig\MaxThreads registry value.
   • Default value of 8000 for the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\XTEConfig\ThreadLimit registry value.
   • Minimum value of 150 for the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\XTEConfig\ThreadLimit registry value.

   [#LC0007]

6. A high number of concurrent print requests from multiple sessions can render the print server unresponsive.

   [#LC0025]

Universal Print Server Client

1. Attempts to print in duplex mode might fail from Microsoft Excel 2010 in conjunction with the Citrix Universal Print Driver (UPD) and the Citrix Universal Print Server (UPS).

   [#LA2890]

2. The Spooler process (spoolsv.exe) might exit unexpectedly.

   [#LA4317]

3. When using the Citrix Universal Printer Driver (UPD), and printing from Microsoft Office applications, those print jobs might remain in the spooling status for a long time and can eventually cause the print spooler service to become unresponsive.

   [#LA4329]

4. This enhancement improves the scalability and reliability of the Universal Print Server. To enable this enhancement in its entirety, you must install both a Universal Print Server and a Universal Print Server Client hotfix that contains Fix #LA5186.

   [#LA5186]

5. When using roaming profiles and the Universal Print Server client, changes to session printers (adding, removing, renaming) made in a session on one server might not be correctly reflected in subsequent sessions on another server.

   [#LA5308]

6. Redirecting a Zebra printer on a XenApp 6.5 server can delete other, shared printers installed on the same server. Network printers installed on other computers are not affected.

   [#LA5668]

7. This fix addresses various issues related to installing and repairing the Universal Print Server client.

   [#LC0021]

8. After running Repair on the Universal Print Server client on 32-bit systems or systems with XenApp 6.5 with Hotfix Rollup Pack 3, the Universal Printer driver is not available.

   [#LC0046]

9. The Universal Print Server client does not retain printing preferences when using a native printer driver.

   [#LC0113]

Miscellaneous

1. This fix addresses an intermittent high memory utilization issue of the Broker Service on the Controller.

   [#LA5629]

2. When using XenDesktop 7.1 Machine Creation Service, Microsoft Office 2013 it is not automatically activated against the Key Management Service (KMS) server.

   [#LA5940]

3. The memory consumption of the Monitoring Service can grow steadily until the service stops responding to requests from Director, eventually rendering Director unresponsive as well.

   [#LA5615]

XenDesktop 7.5

Compared to: XenDesktop 7.1

XenDesktop 7.5 contains all fixes that were included in XenDesktop 7 and 7.1, plus the following, new fixes:

Desktop Director

1. This fix provides various stability enhancements for Desktop Director.

   [#LA5804, #LA5805]

Citrix Studio

1. When creating a catalogue name containing an underscore ("_"), the underscore might not be retained in the name when listed in the Delivery Group created. For example, the catalogue name test_test appears as testtest instead in the Delivery Group.

   [#LA3822]

Security Issues

1. This update is intended to be applied only by customers who require Federal Information Processing Standards compliant encryption. This update supports end-to-end TLS encryption of HDX communications in a XenDesktop 5.6 environment.

   [#LA3873]

Server/Site Administration

1. Attempts to create new machine to an existing dedicated catalog might fail with the following error message:

   "The object has already been deleted or has not been completely created."

   This fix adds additional tracing to the CreateTargetVM function to help facilitate debugging this issue.

   [#LA4361]

2. Off-peak turn-off delays specified for permanently allocated machines are not properly honored.

   [#LA4950]

3. When a catalog is updated, the original base image file is deleted but its parent folder is not. Furthermore, XenDesktop is unaware that the file was deleted and attempts to delete it repeatedly. This can result in several instances of the DisusedImageCleanUp background task running concurrently.

   [#LA5233]

4. Organizing virtual environments into folders in VCenter prevents the broker from being able to access the datastore.

   [#LA5575]

Session/Connection

1. A deadlock can cause the Desktop Delivery Controller to become unresponsive.

   [#LA4863]

2. Machine creation and provisioning might fail in XenDesktop 7.1 deployments running standalone Microsoft System Center Virtual Machine Manager with Hyper-V and using local shared storage or Server Message Block (SMB) type storage repositories.

   [#LA5271]

3. With Auto Client Reconnect enabled, the following error message can appear when trying to reconnect to an active session from a different device:

   "An error occurred on the server while attempting to complete the request."

   [#LA5366]

System Exceptions

1. The Citrix Pvs for VMs Agent (PvsVmAgent) service might fail to start. The issue is observed while the VDA restarts and occurs after the VDA experiences a fatal exception, displaying a blue screen, during a write operation to the VDAState.ini file.

   [#LA4884]

Miscellaneous

1. This fix address an occasional memory leak in citrix.machinecreation.exe.

   [#LA4824]

XenDesktop 7.1

Compared to: XenDesktop 7

XenDesktop 7.1 contains all fixes that were included in XenDesktop 7, plus the following, new fixes:

Citrix Studio

1. Attempts to add a duplicate entry for an existing user under Citrix Studio > Assignments > Edit Desktop Group > Machine Allocation > Select Users appear to succeed initially but the user with the duplicate entry is, in fact, not assigned to the expected machine at all.

   [#LA3822]

2. Attempts to apply a hotfix to an existing base installation of Citrix Studio fail if the base installation was performed in a custom location; instead, the hotfix is installed in the default location at ...\Software\Citrix\DesktopStudio. Because Citrix Studio hotfixes install the full program, attempts to apply a hotfix to a base installation in a custom location result in the installation of an additional instance of Citrix Studio.

   [#LA4599]

Session/Connection

1. When a Virtual Desktop Agent takes a long time to start (for example, as a result of applying Windows updates at startup), an attempt to connect to the VDA from the Web Interface can time out. If you make an additional connection attempt from the Web Interface to the same VDA before it has completed the startup process, the following message appears on the Web Interface:

   "You are not permitted to start any more sessions for this resource."

   [#LA3243]

2. When using the Quick Deploy or the Desktop Deployment features, the Set-ConfigDBConnection PowerShell command times out, causing the deployment process to fail with the following error messages:

   Error message displayed for Desktop Deployment feature:
   "Exception has been thrown by the target of an invocation"

   Error message displayed for Quick Deployment feature:
   "An unhandled error was thrown by the service"

   [#LA4354]

XenDesktop 7

Compared to: XenDesktop 7

XenDesktop 7 contains the following fixes compared to XenDesktop 5.6:

Citrix Studio

1. Attempting to add target devices to a streamed machine catalog in Citrix Studio with a non-standard Provisioning Services (PVS) Soap Server port might fail.

   Note: This fix addresses the issue only for new catalogs you create in Citrix Studio; any existing catalogs need to be deleted and recreated for the fix to take effect.

   [#LA1365]

2. Virtual Desktop Agents that are powered off on the hypervisor randomly show as powered on in Citrix Studio.

   [#LA1545]

3. This feature enhancement eliminates a limitation that prevents Citrix Studio from displaying more than 250 catalogs and desktop groups.

   [#LA1610]

4. Attempts to edit the existing tag for a pooled desktop group can result in the edited tag being appended to the existing tag(s).

   [#LA3317]

5. Attempts to delete a dedicated catalog from Citrix Studio with the option "Remove from XenDesktop and delete from Active Directory" fail on VMware vSphere 5 Update 2.

   [#LA3798]

6. The power state of Virtual Desktop Agents imported from a .csv file can display as "Unknown." The issue occurs when the a host name in the catalog is a substring of another (for example, XS and XS_2).

   [#LA3802]

Desktop Director

1. When using Desktop Director, the IIS worker process (w3wp.exe) can utilize up to 100% of the CPU.

   [#LA2211]

2. Desktop Director might fail to show the network latency for Windows XP Virtual Desktop Agents.

   [#LA2641]

3. Searches for users in Desktop Director do not return users in pre-W2K3 domains if only the nested groups to which the user belongs (but not the parent group) have permissions to access a Desktop Group.

   [#LA2810]

4. Searching a user name in Desktop Director might be slow if the search string contains blank spaces.

   [#LA3498]

5. When a user logs on, the Citrix Group Policy Engine (CitrixCseEngine.exe) can cause the CPU to spike to 100% for an excessive amount of time while performing Group Policy checks.

   With this fix, the CPU time of the Group Policy engine (CitrixCseEngine.exe) process is reduced significantly.

   [#LA3903]

Installing, Uninstalling, Upgrading

1. Installing Hotfix XD560MISvcWX64003 on Desktop Delivery Controllers in a site with failed provisioning workflows can prevent the Machine Identity Service from starting.

   [#LA3556]

Licensing

1. When using Concurrent User (CCU) licensing, the licenses might fail to check-in, eventually resulting in a shortage of licenses. The administrator is required to restart the Desktop Delivery Controller or the license server to return it to the original state. The issue occurs when there is a mismatch in the search result while using the case-sensitive string comparator. As a result, the record of the licenses might not be found while releasing the license.

   [#LA0971]

2. Provisioned XenApp servers refuse to accept connections if they are restarted while the license server is unavailable. The issue occurs because the license server cache file, MPS-WSXICA_MPS-WSXICA.ini, is saved in the%ProgramFiles(x86)%\Citrix\system32\cache folder, which might be unavailable when the server image shuts down.

   This fix allows you to save the license server cache file in a shared network location - a location separate from the XenApp server image - so that the file is available even when the server image shuts down. If you save the file in a location away from the server image, you must set the following registry key to point to the cache file location:

   HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Install
   Name: CacheLocation
   Type: REG_SZ
   Data: <network location of license server cache file>

   Note: You must restart the server after this registry edit in order for the license file to be cached.

   For more information, see Knowledge Center article CTX131202.

   [#242177]

Printing

1. Changes to session printer properties might be saved and restored even if the printer properties retention policy "Do not retain printer properties" is enabled.

   [#LA2152]

2. The Citrix Print Manager Service process might exit unexpectedly.

   [#LA2611]

3. The print spooler service might exit unexpectedly. The issue occurs when UpProv.dll dereferences a null pointer.

   [#LA2652]

4. This fix addresses a memory leak in the Universal Print Server.

   [#LA2934]

5. Users experience significant delays when opening the Devices and Printers window, opening the Printer Properties dialog, and navigating to the Ports tab in the Printer Properties dialog. The issue occurs because the print spooler on the Universal Print Server Client makes excessive RPC connections to the Universal Print Server. To enable this fix in its entirety, you must install both a Print Server hotfix (UpsServer100WX86100; UpsServer100WX64100 or their replacements) and a Universal Print Server Client hotfix (UpsClient100WX86100; UpsClient100WX64100 or their replacements) that contains Fix #LA3177.

   [#LA3177]

6. On XenApp servers with Fix #LA3177 installed that act as clients to the Universal Print Server, the Windows print spooler can exit unexpectedly. The issue results from a third-party printer driver incompatibility.

   [#LA3672]

7. This fix provides speed improvements when using the Universal Print Server.

   To enable this fix, you must install both Universal Print Server (UpsServer100WX86100; UpsServer100WX64100) and Universal Print Server Client (UpsClient100WX86100; UpsClient100WX64100) hotfixes or their respective replacements that contain Fix #LA3708.

   [#LA3708]

Server/Site Administration

1. Removing Authenticated Users from the Security Filtering of Group Policy Objects (GPOs) in the Group Policy Management Console and applying different Security Filtering for the GPOs can cause the GPOs to fail.

   [#LA0641]

2. Desktop groups cannot be created or deleted if their names exceed 63 characters in length or contain underscores ("_").

   [#LA0978]

3. Note: This is a feature enhancement that requires you to install both a Broker Service and a Broker Service PowerShell Snap-in hotfix that contains Fix #LA1371.

   By design, existing catalogs provide only partial power management for assigned desktops. As a result, assigned desktops do not power back on during configured peak hours if they were shut down by the Broker at logoff/disconnect. This feature enhancement introduces a new desktop group setting, "AutomaticPowerOnForAssignedDuringPeak" that lets you force assigned desktops to power back on when logged off or disconnected during peak hours. With the "AutomaticPowerOnForAssignedDuringPeak" setting set to "false" (default), XenDesktop behaves entirely as in earlier releases. To force assigned desktops to power back on during peak hours, use the following PowerShell command:

   "Set-BrokerDesktopGroup <DesktopGroup> -AutomaticPowerOnForAssignedDuringPeak $True"

   [#LA1371]

4. When clicking Browse while assigning a worker group to the load evaluator, browsing can be slow and might experience delays in loading the next control depending on the farm size.

   [#LA1374]

5. This feature enhancement to the Citrix Group Policy feature provides Connector for ConfigMgr policy settings for configuring the XenApp Agent service component of the XenApp Connector for Configuration Manager 2012.

   [#LA1433]

6. Enabling maintenance mode on an assigned desktop powers on all other desktops in the same desktop group.

   [#LA1462]

7. Attempts to publish streamed applications can fail with just-in-time errors. The issue occurs with applications such as Corel PaintShop Pro that use fully transparent icons.

   [#LA1468]

8. Administrators with "Machine administrator" privileges cannot view or create personal vDisk resources ("Pooled with personal vDisk" and "Streamed with personal vDisk") in Citrix Studio.

   [#LA1722]

9. The text of the description of the policy, "Notify user when display mode is degraded," incorrectly states that the policy applies to both XenApp and XenDesktop. The policy applies only to XenApp. This fix corrects the text of the policy description.

   [#LA1757]

10. Certain Windows Group Policy (GPO) settings might prevent the Group Policy Management Console from displaying Citrix policies. The issue occurs in the Group Policy Results reports.

    In order to obtain the Group Policy Results report, you can use the CtxCseUtil.exe tool with the Resultant Set of Policies (RSoP) switch instead of using the Group Policy Management Console:

    Usage: CtxCseUtil.exe /rsop [/o(u|c)] [/u user] [/c ComputerName] [/f filename] [/q] [/dbg]

    • /rsop Generate the RSOP Report for Citrix policies.
    • /o(u|c) Generate only the computer report or only the user report. By default, both are generated.
    • /u Specify the target user. The default is the active user.
    • /c Specify the target computer [IP Address/MachineName]. The default is the local computer.
    • /f Specify a file name for the report. The default is CitrixRsopResult.html.
    • /q Specify if you want to run in Quiet Mode. By default, Quiet Mode is off.
    • /dbg Enable debugging output for the execution of the command.

    return : ERRORLEVEL 0 if successful ; greater than 0 if an error occurred.

    Samples:
    CtxCseUtil.exe /rsop
    CtxCseUtil.exe /rsop /ou
    CtxCseUtil.exe /rsop /u user1 /c remotecomputer1
    CtxCseUtil.exe /rsop /u user1 /f Test1_user1_121024.html /q
    CtxCseUtil.exe /rsop /ou /u user1
    CtxCseUtil.exe /rsop /oc /c remotecomputer1
    CtxCseUtil.exe /rsop /u user1 /c remotecomputer1 /dbg
    CtxCseUtil.exe /rsop /dbg

    Note: You must run the tool with domain administrators' credentials.

    [#LA1835]

11. This fix addresses an issue that prevents the new preferred controller from getting data from the host connection when the preferred controller is changed.

    [#LA1837]

12. XenApp 6.5 policy migration fails for policies filtered by OU. The issue does not occur when using other types of policy filters such as username, or Client IP.

    [#LA1844]

13. The Multimedia conferencing policy is not visible in Citrix Studio and in the Group Policy Management console while filtered for XenDesktop. However, the policy is visible when setting the filter to XenApp or to All.

    [#LA1881]

14. Attempts to retrieve policies on a VDA from Desktop Director fail. To resolve this issue in its entirety, you must install this fix and then grant "Read" permissions on the agent's C:\Users\<Username>\Citrix\ folder, including subfolders and files, to the Desktop Director user.

    [#LA2270]

15. Some XenDesktop policies are visible in the Group Policy Management Console while filtered for XenApp policies.

    [#LA2895]

16. The CtxCseUtil.exe tool might fail to retrieve the Resultant Set of Policies (RSoP) on XenApp 6 servers because the GetRsopReport function is missing from the Windows Management Instrumentation (WMI) interface.

    With this fix, the WMI interface is updated to obtain the RSoP report from XenApp 6.0 using CtxCseUtil.exe.

    [#LA2968]

17. After restoring the database from a backup, current machine and user policy settings are not applied on the VDA. The issue occurs because of a versioning discrepancy in the policy settings version.

    [#LA3210]

18. The Output Session Bandwidth Performance Monitoring (Perfmon) counters might not work as expected. As a result, the values displayed for sessions are too low and do not reflect the session bandwidth correctly.

    [#LA3251]

19. Deleting a provisioned Virtual Desktop Agent on Version 5.1 of VMware ESX from Version 5.6 of the Delivery Controller might fail.

    [#LA3335]

20. Attempts to delete a Dedicated Machine Catalog on Version 5.1 of VMware ESX from Citrix Studio might fail.

    [#LA3624]

Session/Connection

1. Description: Failure of a hypervisor or a loss of connectivity between the hypervisor and the Broker renders an active session inaccessible, and attempts to reconnect to the session fail. For shared desktops, and in the common case where a user is entitled only to a single desktop from a group, the user effectively loses all access to that desktop group, even if other machines in the same group (but on a different hypervisor) are available for use. For large hypervisors in a data center, such loss of a hypervisor can cause a large scale reduction of availability of XenDesktop that requires significant operator intervention to remedy.

   With this feature enhancement:

   • a new session can be brokered from the existing infrastructure
   • sessions orphaned as a result of hypervisor failure or of a loss of connectivity can be enumerated and terminated from the console

   Background: This feature enhancement adds a new "hidden" attribute to every session. With the "hidden" attribute set to "false" (default), XenDesktop behaves entirely as in earlier releases. To avoid a loss of desktop availability in the event of hypervisor failure, the Broker automatically marks a session as hidden ("hidden" = "true") the moment a user attempts to reconnect to that session. With the session marked hidden this way, the Broker continues with the session launch as if no session was found to which to reconnect. Provided sufficient desktops are available, a new session is created on a different desktop - even if the user's entitlement to that resource would ordinarily be exhausted.

   • To enumerate orphaned sessions, use the PowerShell command "Get-BrokerSession -Hidden $true"
   • To revert all hidden sessions to their visible state, use the PowerShell command "Get-BrokerSession -Hidden $true | Set-BrokerSession -Hidden $false"

   [#LA0754]

System Exceptions

1. Citrix Desktop Service can fail to start on a system that has a group policy rollback file (rollback.gpf) of size zero bytes.

   [#LA0706]

2. Existing difference disks might not be deleted, which can eventually result in storage overflow.

   [#LA0793]

Miscellaneous

1. Users' attempts to restart a dedicated Virtual Desktop Agent from the Web Interface fail if a session record for the agent exists in the Broker database but is missing user information.

   [#LA2849]