Multiple sessions with a single user

From Login VSI Documentation
Jump to: navigation, search


The concept is that you use a single user to log on multiple times to an environment. This is accomplished by configuring the target environment to allow a single user to logon multiple times. In this example Xendesktop is used. When configuring Xendesktop to logon multiple times to the same resource it will give the users access to a copy of the resource. For example, if the resource name is MyDesktop then the user gets access to resources like MyDesktop(1), MyDesktop(2), etc. The goal is to have a single user logon to each resource for every iteration. This will be accomplished by using a CSV file.


You will need:

  • At least one account to log on to your target environment (the environment that you want to put load on).
  • An environment that allows a single user to log on multiple times. You can accomplish this using pretty much every well-known VDI platform. This example is for Citrix Xendesktop using Storefront to connect.
  • Configure your target environment to run the VSI logon script ([file://server/vsishare/_VSI_Binaries/target/logon.cmd \\server\vsishare\_VSI_Binaries\target\logon.cmd]) when the user logs on. The startup folder in the start menu or the run key in the registry can be used to accomplish this if you cannot assign a logon script to a user through Active Directory.

CSV file

A CSV file works by replacing sections of the command line used in the VSI management console with values from the CSV file. For more detailed information about using CSV files in Login VSI please see: Wookload from CSV


  • It is unclear if there is a limit to how many times a single user can logon to a single desktop in a Xendesktop scenario.
  • Using the Citrix Web Interface while a user has access to many resources will significantly slow down the Web Interface. Allowing a user to access a resource more than 10 times is therefore not recommended when using the Web Interface. Using Storefront should not be an issue
  • The CSV file should be referred to using a network/UNC path. This makes sure that every launcher has access to the CSV file. The VSIshare is commonly used to store the CSV file.
  • If you cannot set the logon script for a user you will need to set the Engine Startup setting to chained. You can find the Engine Startup setting in the management console under Workload > Settings.