I've been doing some EdgeSight Load Testing with XenApp 6.5; which I haven't done in a few months. We have updated our Citrix servers since then with the newer HotFix RollUp (HFRU) pack and now I'm testing a new application. Our typical setup is to use a single generic account and connect it via multiple sessions to the same Citrix server and capture some metrics (CPU, Network, Memory, etc). In the past, this seemed to work pretty flawlessly but in the last week I was having issues. By the time the 3rd session was connecting to the Citrix server, instead of creating a new session it would 'steal' the 1st session. This prevented me from having more than 2 sessions connected to a server.
Well, it turns out Citrix modified their behaviour a bit but allowed a registry key to be set to change it back. The new value was introduced in HFRU 2 and is as follows:
http://support.citrix.com/article/CTX136248
On Windows Server 2003, you can specify whether a user can reconnect to a session from any client device or only from the originating client. The From originating client only option is not present anymore in the Remote Desktop Services settings of the Windows Server 2008 R2 edition.
This feature enhancement allows you to implement the same functionality on Windows Server 2008 R2 through XenApp. To enable the feature, you must set the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\Citrix
Name: ReconnectSame
Type: REG_DWORD
Data: 1
Note that if Workspace Control is enabled on the Web Interface, enabling the "Automatically reconnect to sessions when users log on" feature can result in side effects and users might have to launch the session twice to open a session from the non-originating client device.
Enabling that registry key and I can immediately restart my load testing without any stolen sessions.
No comments:
Post a Comment