Citrix just put the CTX127030 online containing:
Tag Archive for XenApp
Citrix XenApp on VMware Best Practices
Recently I found a blogpost from Alex Fontana at the VMware community blogs with Citrix XenApp on VMware Best Practices:
RES Workspace Manager: Windows 7 Embedded, Citrix and log off local client
Today I was at a customer with thin clients with Windows 7 embedded installed, these thin clients had to be configured to connect to a Citrix XenApp 5 farm. The problem was that we wanted to have SSO (single sign out ;-)). So of course we asked RES if we could use the Subscriber/VDX but they came with the following statement:
Citrix XenApp seamless desktop and task manager.
Recently I participated in a project in which a new Citrix XA5 for 2008 farm was build and PowerFuse 2010 was used for ‘user workspace management’. They had thin clients which connected to their old Citrix farm by using a distributed ICA file. In the new farm we created a setup with two Citrix Web Interfaces servers with a Citrix Services Site configured. Only one server was active, the other one was configured as backup URL.
The desktop was started as seamless desktop because of the configuration in the ICA file, this resulted in a situation where the user could start the task manager of the local thin client (Windows 7 Embedded) so they could stop running processes in their ICA session but they couldn’t use the windows shortcut keys because all of the commands were passed trough to the thin client. The customer wanted a full desktop so they could use their windows shortcut keys but they also wanted a method to stop running processes in their ICA session.
In my opinion they had two options:
- Full desktop with taskmgr.exe as application within this full desktop
- Full desktop with memory optimization from RES PowerFuse.
Full desktop with taskmgr.exe as application within this full desktop
By offering a full desktop the windows shortcut keys can be used within the ICA session but the user doesn’t get the functionality to stop running processes. As an addition taskmgr.exe should be offered to the users via PowerFuse. The downside would be that the taskmgr.exe gives more information that needed for the users and would probably create more confusion for the users.
Full desktop with memory optimization from RES PowerFuse
By offering a full desktop the windows shortcut keys can be used within the ICA session but the user doesn’t get the functionality to stop running processes. As an addition PowerFuse should be configured to give the users the option to stop running processes.
By turning on memory optimization there’s an option in RES PowerFuse to show the memory usage in the system tray:
When this option is enabled users will get an extra icon in their system tray:
When the user clicks this icon a program will appear that displays the running processes, the memory usage and let’s the user close an application:
But… when memory optimization is enabled keep in mind that there’s more to configure. A limit will be forced so you have to calculate the limit properly and a couple of applications can’t really deal with these kinds of memory optimization. When you’ve got such an application you can exclude this specific application from the memory optimization in PowerFuse 2010:
So my advice would be to run a full desktop with memory optimization but keep in mind that it brings on additional administrative burden.
Recommended Citrix and Microsoft Hotfixes for XenApp 6 and Windows Server 2008 R2
Based on Citrix Technical Support experience and customer feedback, the following Citrix and Microsoft hotfixes have been found to resolve the most common issues with XenApp 6 and Windows Server 2008 R2. These hotfixes focus on basic functionality and stability. For a complete list of Citrix hotfixes for XenApp 6, please click here.
Citrix SSOShell.exe Memory leak
While installing Citrix SSO 4.8 in a test environment in combination with Windows Server 2003 and Citrix XenApp 5 for Windows Server 2003 we noticed that the Citrix servers were affected by this installation. The user sessions were taking more memory than before the installation of Citrix SSO. While investigating this issue we noticed that the memory usage was growing as the session was longer active. So Citrix SSO 4.8 had a memory leak, Citrix already had a fix for this in the SSOP480WX86001 (Version 4.8.6501.0) – For Citrix Single Sign-on Plug-in 4.8 x86 hotfix which fixes the following: