Hotfix package name: GPMx170WX86011.zip
For: Computers running the 32-bit version of Windows 7, Vista, XP, Server 2003, or Server 2008, with the Group Policy Management Console installed
Replaces: All previous versions
Date: February, 2016
Languages supported: English (US), German (DE), Spanish (ES), French (FR), Japanese (JA), Simplified Chinese (SC)
Readme version: 1.00
Readme Revision History
Version | Date | Change Description |
1.00 | February, 2016 | Initial release |
Caution! All instances of the Group Policy Management Console must be at the same hotfix level; mixed hotfix levels are not supported. – If you choose to upgrade to the console to this hotfix, you must update all Group Policy Management Consoles in your deployment. As a cautionary measure, Citrix recommends that you back up all policies before installing this hotfix.
Caution! Downgrading from this hotfix is not supported: If you configure new policies or update existing policies after installing this hotfix, then uninstall this hotfix and install an earlier hotfix, the policies configured or updated while this hotfix was in place are not visible in earlier versions of the console.
Caution! This release may require you to edit the registry. Using Registry Editor 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.
This document describes the issue(s) resolved by this release and includes installation instructions. For additional product information, including system requirements, see XenApp 6.5 on the Citrix Product Documentation site.
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.
[From GPMx170WX86011][#LC2121]
When running the Group Policy Modeling wizard on the policies node of AppCenter as a domain user, applied user and computer policies might not be visible.
[From GPMx170WX86011][#LC3284]
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.
[From GPMx170WX86001][#LA1374]
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.
[From GPMx170WX86001][#LA1757]
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.
[From GPMx170WX86001][#LA1844]
The Multimedia conferencing policy is not visible in Desktop 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.
[From GPMx170WX86001][#LA1881]
Attempts to change the upper/lowercase state of one or more letters of a policy name cause the display of all other policies to disappear from the console.
[From GPMx170WX86001][#LA2038]
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]
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.
[From GPMx170WX86003][#LA1835]
Some XenDesktop policies are visible in the Group Policy Management Console while filtered for XenApp policies.
[From GPMx170WX86003][#LA2895]
Attempts to apply a policy to a worker group whose name contains a colon (:) character might fail.
[From GPMx170WX86003][#LA3525]
This enhancement adds the following new policy settings under a new category, Connector For Configuration Manager 2012, of the Group Policy management Console:
For more information about Connector for Configuration Manager Policy Settings, see http://support.citrix.com/proddocs/topic/xenapp65-admin/ps-ref-policies-connector-config-manager.html.
[From GPMx170WX86005][#LA4600]
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.
[From GPMx170WX86006][#LA4802]
This fix addresses certain Japanese translation issues for the "Desktop Launches" group policy.
[From GPMx170WX86006][#LA4832]
Policies can be lost. This happens when the policy file is corrupted and truncated as a result of high memory consumption by AppCenter and Desktop Studio, which can occur when you modify policies in scenarios with a large number of configured policies.
[From GPMx170WX86007][#LA5385]
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.
[From GPMx170WX86007][#LC0083]
Importing a saved policy template to AppCenter fails to show the policy settings if the settings are not edited after the import.
[From GPMx170WX86008][#LC0684]
The configured Citrix policy settings might not be visible when attempting to combine Microsoft and Citrix Policy settings in the same Group Policy Object (GPO). The settings do appear when editing the GPO. You can also see the policies when configuring the settings in the AppCenter console.
[From GPMx170WX86009][#LC0513]
Application processes might prevent sessions from gracefully logging off. With this release, you can configure a group policy and create a list of processes that can be ignored to allow a graceful logoff of XenApp sessions.
To enable this fix, install both XenApp 6.5 Hotfix XA650R05W2K8R2X64023 (or its replacement) and a Group Policy Management Console Hotfix GPMx170WX86010 or GPMx170WX64010, (or their replacements) that contains Fix #LC1980.
Note: You must configure this policy by using group policy to allow this enhancement to work correctly.
To configure the group policy on the host
In XenApp, click Citrix AppCenter > Policies > Citrix Computer Policies > Server Settings > Graceful session logoff: ignore process.
Enter the list of application names with a comma and without spaces between the names. For example: app1.exe,app2.exe,app3.exe.
Important: If you do not configure these values by using this format, the policy might not work.
At a command line, run "gpupdate /force" on all servers on which to enforce the policy settings.
The policy settings are stored in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Citrix\IMA\Ignore Process\LogoffCheckGPModules.
[From GPMx170WX86010][#LC1980]
Notes:
To install this hotfix:
To uninstall this hotfix: