Target Systems

1. Custom Command Line

The Login VSI launcher is platform and protocol independent with the introduction of the “Custom” and “Custom with CSV file” connection options. As long as the client allows the use of a command-line to automatically launch sessions, Login VSI will support that platform.

The “Custom” function is really simple. The following variables are supported %input_servername%, %input_username%, %input_domain%, %input_password%, %count%. The image below shows to which field these variables are mapped. %count% corresponds the number of the session that is about to be launched.

This example (dummy code) will connect multiple users to a broker:

ExampleClient.exe /user:%input_domain%\%$input_username%%Count% /Broker:%input_servername% /Password:%input_password%

This example (dummy code) will connect multiple user to multiple machines:

ExampleClient.exe /user:%input_domain%\%input_username%%Count% /computer:%input_servername%%count% Password:%input_password%

For added flexibility you can create CSV for input of your custom command line. There is no limitation on the amount of columns (variables) and the naming of the parameters. Use a comma “,” as a delimiter. The setup of the CSV is straightforward, the launcher will process the second row and use the name specified in the first row as variable name. Save the custom CSV file in the Login VSI share.

Example csv file

2. Environments:

2.1. Remote Desktop Services

Also known as Terminal Services, RDP and Microsoft Remote Desktop. To setup a RDP connection from Login VSI you can set the connection type to RDP in the Management Console. If you require more flexiblility you can setup a RDP connection from the Custom CommandLine. Because the default MSTSC.exe does not allow password passtrough Login VSI uses LaunchRDP.exe created by Remco Weijnen.

"C:\Program Files\Login Consultants\VSI\Launcher\Agent\LaunchRDP.exe" %CSV_Workstation% 3389 Login_VSI%count% Domain Password! 0 0 0

LaunchRDP.exe requires the following parameters:

2.2. VMware View (all versions)

To connect to VMware View commandline we can use VMware's view client directly because it supports sufficient parameters to setup a connection.

Configure the following Custom Commandline together with a CSV file:

"c:\program files\VMware\VMWare View\Client\bin\wswc.exe" -serverURL %CSV_ServerURL% -username fu_VSI -password %CSV_Password% -domainname MyDomain -desktopname %CSV_DesktopName% -Standalone -logInAsCurrentUser False-connectUSBOnStartup False

2.3. Citrix XenApp

• Download Citrix XML ICA Connector (ICAConnector.zip)
• Make sure the Citrix Client is installed on all launchers
• Extract ICAConnect to your VSIShare, for example \\server\VSIShare\ICAConnect (If the folder does not exist create it)
• Start the Login VSI Management Console and go to the “Test Configuration” tab.
• Set the “Connection Type” to “Custom Command Line” (CCL) or when required “Custom Command Line with CSV”
• Configure the following “Custom Command Line”:

\\Server\VSIShare\ICAConnect\ICAConnect.exe /server MyServer /user MyUser1 /password SuperSecretPass /domain LAB /encryption RC5-128

2.4. Citrix XenDesktop 4

Citrix Consulting Solution Center published an external white paper titled Performance Assessment and Bandwidth Analysis for Delivering XenDesktop to Branch Offices which leveraged Login Consultants VSI Pro as the benchmarking tool for Citrix XenDesktop 4. After the release of the aforementioned document and other Consulting engagements involving Login VSI, guidance was requested regarding the implementation and configuration of the Login VSI benchmarking tool in conjunction with Citrix XenDesktop. Download the Login VSI & Xendesktop 4 configuration guide.

2.5. Citrix XenDesktop via webinterface 5.4

To let Login VSI connect to Citrix XenDesktop 5 or a XenApp farm use the following steps:

• Download Citrix Webinterface Connector (CTXConnector.zip) (Requires .net 3.0)
• Make sure the Citrix Client is installed on all launchers
• Extract CTXConnect to your VSIShare, for example \\server\VSIShare\CTXConnect (If the folder does not exist create it)
• Start the Login VSI Management Console and go to the “Test Configuration” tab.
• Set the “Connection Type” to “Custom Command Line” (CCL) or when required “Custom Command Line with CSV”
• Configure the following “Custom Command Line”:

“\\server\VSIShare\Scripts\CTXConnect\CTXConnector.exe” -s “http://MyXDwebsite” -u “Login_VSI%Count%” -p “Password!” -d “DomainName” -r “DesktopName” -t1 5 -t2 7

• Save the test settings

This video contains captions (subtitles)

To troubleshoot XDConnect you can create a CMD file with the contents below. You can run this CMD file directly on any launcher that has the Citrix Client installed and access to the XDConnect.exe file. Make sure that on a per launcher basis only one instance of CTXConnect is running at the same time, if they overlap please change the logon interval or change the t1/t2 parameters.

“\\server\VSIShare\Scripts\XDConnect\XDConnect.exe” -s “http://MyXDwebsite” -u “Login_VSI1” -p “Password!” -d “DomainName” -r “DesktopName” -debug

This should open a new instance of internet explorer browse to the webinterface site authenticate a user and connect the desktop. When the connection fails debug information will be stored in the %temp%\VSI\Log folder.

2.6. XenDesktop Alternative by Citrix

Citrix released a whitepaper on connecting Login VSI with XenDesktop

2.7. Quest vWorkspace

To connect Login VSI with a Quest vWorkspace environment use the following steps:

• Publish a PIT file with an application name, not a servername. (see below).

• Save this as .PIT file
• You can use PNTSC.exe [PITFILE from step 2] -username [username] -password [password] to execute a PIT file. This will execute against the broker
• Use the following Custom Command line in the Login VSI management console:

C:\PathTo\PNTSC.exe [PITFILE from step 2] -Username Login_VSI%Count% -Password Password!