login vsi company logo login vsi company logo 250x40
header-05.jpg

Launcher only logs into first session

  • patrickdarcy
  • patrickdarcy's Avatar Topic Author
22 Jan 2014 20:53 #1591 by patrickdarcy
The launcher will log into the first session but any subsequent sessions after it sticks at the application selection windows in the Citrix web interface.

The Session monitor stats that all sessions are logged in and active. XenDesktop only ever see 1 session logged in per launcher.

Please Log in to join the conversation.

More
22 Jan 2014 23:56 #1594 by o.bouhaj
Patrick,

What do you exactly mean by "application selection" window? Does it hang where it should be clicking on a resource? Or does it not authenticate the user? Do you see 1 session per/ Launcher? Are you sure that you are initiating more than 1 session per/ Launcher?

Do you test with one (1) test user?
Can you make sure that the Citrix Mgnt/WI allows more session per machine and/or user?

This can either be that:

1- Your test users are only allowed to start one resource
2- When you logoff from the WI it will logoff the user-session

Let me know if you need further help. Thanks,

Please Log in to join the conversation.

  • patrickdarcy
  • patrickdarcy's Avatar Topic Author
23 Jan 2014 09:19 #1597 by patrickdarcy
Hi Omar

What do you exactly mean by "application selection" window? I mean resource selection;
Does it hang where it should be clicking on a resource? The first user works but the second and subsequent stop at clicking on a resource.
Or does it not authenticate the user? It does authenticate.
Do you see 1 session per/ Launcher? We see 1 session per launcher only
Are you sure that you are initiating more than 1 session per/ Launcher?

Do you test with one (1) test user? We use a CSV with 400 logins but we are seeing that each launcher only seem to utilise 1 of the users?
Can you make sure that the Citrix Mgnt/WI allows more session per machine and/or user?

This can either be that:

1- Your test users are only allowed to start one resource - can you point me in the right direction here?
2- When you logoff from the WI it will logoff the user-session

Let me know if you need further help. Thanks,

Please Log in to join the conversation.

More
23 Jan 2014 11:58 #1598 by o.bouhaj
All, the problems are solved.

The issue was that the basephase is initiating session with a timeframe of 6sec. p/ session (default).
If you are using citrix webinterface (ctxconnector) make sure when you use the basephase that the interval of initiating sessions is at least 30sec. This is due to the process that the launcher initiate IE, authenticate the user, click a resource and logoff from the wi.

make sure to check out the docs/vids at: www.loginvsi.com/documentation/Connector...erface_configuration

quick overview what exactly happens for * out there using LoginVSI :):

User 1 logs on to the web interface and starts the whole process of logging in, starting a resource and logging off. This process takes time, let’s say 25 seconds. Let’s assume the interval between sessions per launcher is 10 seconds.
After user 1 is about half way through user 2 starts the process. Since users 1 is still in the process of completing the task it still has a valid session to the web interface. Since Internet Explorer knows this it will use this SAME session for user 2. User 2 will open an instance of Internet Explorer that will use user 1’s session. This results in user 2 not being prompted for a username/password, instead it will be logged on as user 1.

To avoid all of the above you need to make sure that an entire logon process through the web interface fits into a logon interval. In my example above that interval is 10 seconds per launcher. For logging on through the web interface this is simply too quick. There are multiple solutions to solve this problem:
1. Increase the interval (Launcher Logon Rate) between session per launcher (30 seconds or more). This gives each user enough time to complete the web interface process before the next user is launched. In parallel mode this is more complex. Use the session calculator to calculate what the time between sessions is per launcher (Launcher Logon Rate).
2. Add more launchers (parallel mode only). If you want to keep the overall timeframe but want to increase the time between sessions simply increase the number of launchers. As the launchers divide the total amount of sessions among each other, adding more launchers will decrease the number of sessions a single launcher will initiate thus increasing the time between individual sessions on that launchers while keeping the overall timeframe the same.

Changing the T1 and T2 timers is actually detrimental to this issue as the T1 and T2 timers are pauses. T1 = the pause between the user logging on and the resources being visible and the user attempting to click the resource. This time is intended for web interfaces that do not have the resources ready the instant that the user is authenticated and the resources are displayed. In most cases something short like 2 or 3 seconds is plenty of time.
T2 = the pause between the user clicking the resource and CTXConnector attempting to logoff and close Internet Explorer. This pause in intended to give the web interface (and IE) some time to actually generate and download/execute the ICA file before the web interface is closed. Again, depending on the environment, something small like 2 or 3 seconds should be plenty.
As these timers are pauses setting both (or either) of them to 12 seconds means you are delaying the total time it takes to entire web interface process by 12-24 seconds. Keeping the timing issue I describe above in mind this isn’t helpful.

This issue is only relevant for Citrix Xendesktop as it requires the use of the web interface. VMware view has a own client that can be called by a command line and Xenapp can be automated through the Citrix Receiver.
This is due to the way IE (browsers in general) share authenticated session information between instances of the browser.

We recommend using an interval of 30 per launcher host.

The time between sessions per physical host means that you will be launching session at the speed we recommend sessions to be launched. The extra time for the launchers means that they have more time to complete the logon process through the web interface.

Please Log in to join the conversation.

Start Delivering the Best End User Experience Today

Request a Demo

Login VSI, Inc.

3945 Freedom Circle
Suite 670
Santa Clara, CA 95054

Phone: +1 408 899 7418

300 Tradecenter
Suite 3460
Woburn, MA 01801

Phone: +1 408 899 7418

Login VSI B.V.

De Entree 85
1101 BH Amsterdam
The Netherlands

Phone: +31 20 705 1200