Based on Citrix Technical Support experience and customer feedback, the following Citrix and Microsoft hotfixes are found to resolve the most common issues with XenApp 6, and Xenapp 6.5 running on a Windows Server 2008 R2 platform. These hotfixes focus on basic functionality and stability. For a complete list of Citrix hotfixes for each product, click Xenapp 6.0 or Xenapp 6.5.
XenApp 6.5 Hotfixes
XA650W2K8R2X64001 NEW
- Pass-through authentication fails in a pass-through client.
- After shadowing a session, the win32k.sys and vdtw30.dll files can leave the session unresponsive on the server; the session cannot be reset.
XA600W2K8R2X64R01
- This hotfix rollup pack replaces most individual hotfixes released for this version of XenApp so far, and introduces a number of new fixes and enhancements that have not been released previously. To download this hotfix rollup pack, click here.
Other XenApp 6.0 Citrix Hotfixes
DSCXACmd600W2K8R2X64003 (Not Included in Rollup Pack 1)
- The Add-XAAutoReplicatedPrinterDriver cmdlet takes a parameter named sourceservername. However, get-help add-xaautoreplicatedprinterdriver รข€“ examples incorrectly states that the cmdlet takes a parameter named servername.
- This fix addresses various issues with published icons.
- This enhancement is a part of the XenApp Printing Optimization Pack. The Printing Optimization Pack improves the user experience and printing speed by reducing the printer bandwidth required. For more information, including system requirements and required components, see XenApp Printing Optimization Pack in eDocs, the Citrix Product Documentation Library.
Windows Server 2008 R2 SP1 contains most of the following hotfixes (exceptions noted inline). For a list of all Microsoft Hotfixes included in Windows Server 2008 R2 SP1, refer to: Documentation for Windows 7 and Windows Server 2008 R2 Service Pack 1 (KB976932) and click the download link for “WS08R2 SP1.xls”. Microsoft has published the following KB article specific to Remote Desktop Services: Available Updates for Remote Desktop Services (Terminal Services) in Windows Server 2008 R2
KB2661001 NEW (Not included in SP1)
- On Servers running Windows 2008 R2, the following error messages are displayed during the logon process: "Please wait for Local Session Manager", "The task you are trying to do can't be completed because remote desktop services is currently busy”, and
- A Windows Server 2008 R2-based Remote Desktop server denies some connection requests randomly under heavy logon or logoff conditions.
- There is a delay when you shut down, restart, or log off on a Windows Server 2008 R2.
- If a heavy load situation exists or if connectivity issues exist, there is a stop error message in Windows 7 and in Windows Server 2008 R2 as follows:
"STOP: 0x000000B8"
- A computer that is running Windows Server 2008 R2 stops responding randomly.
- An application or service that uses Winsock API or Winsock Kernel API might randomly stop responding in Windows Server 2008 R2
- Installing a 32-bit help System 2008R2 might be required if hosting 32-bit applications
- Remote desktop sessions do not exit completely and you cannot establish new remote desktop sessions to a computer that is running Windows Server 2008 R2.
- Startup takes a long time on a Windows 7 or Windows Server 2008 R2-based computer that has an Intel Nehalem-EX CPU installed.
- A computer that is running Windows 7 or Windows Server 2008 R2 intermittently cannot use a shared network printer to print.
- You cannot access shared files or shared printers in Windows 7 or in Windows Server 2008 R2
- A mapped drive that has the non-persistent flag set is displayed as a disconnected drive in Windows 7 or in Windows Server 2008 R2
- The logon process stops responding in Windows Server 2008 R2 or in Windows 7
- Invalid redirected printers may be available in a Remote Desktop Services session that connects to a RD Session Host server that is running Windows Server 2008 R2
- Unexpectedly slow startup or logon process in Windows Server 2008 R2 or in Windows 7
XA600W2K8R2X64044 (Xenapp Fundamentals Edition only)
- When a server running Access Fundamentals/XenApp 6 Fundamentals Edition is in a workgroup, the Citrix license cannot be retrieved and application launch fails, resulting in the following error message: "License Acquisition failed..."
- This fix addresses security vulnerability. For more information, see Knowledge Center article CTX123359.
- This fix addresses session reliability issues that can occur when using multiple, disparate, client devices to reconnect to the same session.
- This fix addresses security vulnerability. For more information, see Knowledge Center article CTX128169
- Servers might experience a fatal exception, displaying a blue screen, with bugcheck code 0xf4 on IMAAdvanceSrv.exe.
- Servers running XenApp 6 can become unresponsive when shutting down. The issue occurs when the picadm.sys driver encounters certain error conditions that prevent it from shutting down in an orderly fashion. Also, servers might experience a fatal exception, displaying a blue screen on picadm.sys with bugcheck code 0x22 (FILE_SYSTEM).
- If a session is disconnected while it is still reading or writing a Client Drive Mapping (CDM) file, the resulting deadlock condition can prevent servers from accepting new session requests.
- Servers might experience a fatal exception, displaying a blue screen, on picadm.sys. The issue occurs when the user removes a thumb drive from a client device while connected to a session. Dumps indicate that picadm.sys is referencing invalid, possibly disconnected volumes.
- When the ReadOnlyMappedDrive registry key (HKEY_LOCAL_MACHINE\SYSTEM\Current Control Set\services\picadm\Parameters) is set to 1, published applications can no longer access and browse mapped client drives.
- With folder redirection enabled, servers can experience a fatal exception, displaying a blue screen, on picadm.sys. The issue can be observed when attempting to save a file that was introduced into the session on a USB device attached to and then removed from a thin client device.
- Servers with Hotfix XA600W2K8R2X64018 installed can become unresponsive intermittently. The issue occurs when a scheduled reboot is triggered by a Citrix policy while there are active sessions on the server.
- With Session Reliability enabled, ICA connection attempts fail if the ICA Listener is bound to a single NIC in a multi-homed environment.
- The Citrix SSL Relay Configuration tool can fail to correctly create the outbound connection policies defined in its Connection tab. After applying this fix on affected deployments, the policies are modified to disallow all outgoing connections. As a result, SSL connections can stop working. In order to recreate the correct policies and allow SSL connections to work again, you must rerun the Citrix SSL Relay Configuration tool, verify the policies in its Connection tab and click Apply. The next time the server restarts, the correct policies are in place.
- This fix addresses two installation issues:
- Hotfixes fail to install on a XA6 server that has not yet had the XenApp Server Role configured.
- Installing hotfixes or performing a repair on the base product for Citrix XenApp 6 for Windows Server 2008 R2 can inadvertently remove the Citrix Licensing component, if present, from the system. This fix prevents the Citrix Licensing component from being removed when installing subsequent hotfixes.
- Servers might experience a fatal exception, displaying a blue screen while shadowing is started.
- This fix addresses security vulnerability. For more information, see Knowledge Center article CTX129430.
- Certain applications fail to launch when Administrator Approval Mode is enabled in User Account Control.
- This fix addresses the following issues for sessions launched as streamed to server or by a script: 1) The application name can be missing from the session information of the Delivery Services Console Session and not appear under the Applications folder of the Delivery Services Console. 2) Application limits might be ignored. 3) Attempts to reconnect to disconnected sessions might fail.
- Certain applications can perform slowly when run in seamless mode
- The CPU consumption of the winlogon.exe process can be higher than usual and it might cause new connection attempts to fail once a server hosts 70 connections or more. Eventually, servers can experience a fatal exception and need to be restarted.
- Attempts to log on to a XenApp 6 server using Version 7 or earlier versions of the clients can cause svchost.exe to exit unexpectedly. As a result, further connection attempts to the server fail until it is restarted.
- The CPU consumption of the CitrixCseEngine.exe process can spike unexpectedly and cause logon delays.
- Attempts to launch a published application that resides on a mapped network drive rather than on a XenApp server failure
- When connecting to a server running Windows Server 2008 R2 with Service Pack 1, Terminal Services can exit unexpectedly. This causes users to experience a black screen when logging on and the logon process fails to complete.
- A rare race condition that occurs when a shadowee disconnects at roughly the same time a shadower connects can cause servers to experience a fatal exception, displaying a blue screen on RPM.dll.
- The fix addresses an issue where the IMA Service exits unexpectedly when a network adapter is not bound to an IP address.
- Servers might become unresponsive or experience a fatal exception on rpm.dll when an administrator initiates a shadowing session.
- authentication fails after applying Hotfix XA600W2K8R2X64048.more...
- This enhancement is a part of the XenApp Printing Optimization Pack. The Printing Optimization Pack improves the user experience and printing speed by reducing the printer bandwidth required. For more information, including system requirements, required components, and known issues, see XenApp Printing Optimization Pack in eDocs, the Citrix Product Documentation Library.
- This enhancement allows printing within a session using ICA Proxy through Branch Repeater.
- During times of heavy logon/logoff activity, sessions can become unresponsive while connecting. The "Starting <application name>" message appears but the connection attempt fails to complete.
No comments:
Post a Comment