Articles in this section

See more

Login VSI - Connectors reference, and connection setup

Avatar
Joshua Kennedy
  • Updated
Follow

Login VSI Connectors reference

Introduction

This document describes the Login VSI connectors for benchmarking 1.0 used by Login VSI 4.0. These connectors have been designed keeping in mind best practices to do performance tests. All Login VSI licensees are allowed to use these connectors.

  • Direct Desktop Connector (DDC) only Login VSI Pro licensees can use Direct Desktop Connector

Concept

The connectors shipped with Login VSI are designed to initiate (remote) connections to the Login VSI target environment with ease. Launchers are responsible for initiating sessions. To do this, a session can be initiated via a command line. Some platforms can do this out of the box; others need a third party tool, the connectors.

Requirements

  • Connectors require a Login VSI Launcher
    • Login VSI Launcher
      • A Launcher requires a machine with at least 2(v)CPU and 4GB RAM of memory
      • A Launcher requires the remoting client to establish a connection (e.g. RDP client, Citrix Receiver or VMware Horizon View client)
      • Launcher Agent
      • Access (read/write) to the VSIshare
      • Connectors require Microsoft .NET Framework 4.5.2

The Launcher will establish a connection through the pre-configured connector command line and depending on the configured connector type/remote protocol. Depending on the remote protocol used by the Launcher best practices for each connector are:

  • Citrix remote protocol: HDX (3D Pro) / ICA
    • 25 sessions per Launcher
  • Direct Desktop Connector (DDC)
    • 1000 sessions per Launcher
  • Microsoft remote protocol: RDP
    • 50 sessions per Launcher
  • VMware Horizon View remote protocol: PCoIP
    • 25 sessions per Launcher

Note

  • Connectors are compatible with all multi-language operating systems more recent than XP
    • For both 32-bit and 64-bit versions
  • A connector is required to run stress and performance tests
  • The Login VSI Management Console is required to setup a connector command line to stress and performance test

Connector types

The following connectors are shipped with Login VSI.

Connection types:

  • Citrix Storefront
    • HDX (3D Pro) / ICA
    • Citrix Storefront (SFConnect) is designed for Citrix (usually Citrix XenDesktop 7.x and Citrix Excalibur) environments
  • Citrix Web Interface
    • HDX (3D Pro) / ICA
    • Citrix Web Interface (CTXConnector) is designed for Citrix Web Interface (usually Citrix XenApp 3.x/4.x/5.x/6.x and XenDesktop 3.x/4.x/5.x) environments
    • Please note: CTXConnector does not support the Storefront website
  • Citrix XenApp
    • HDX (3D Pro) / ICA
    • Citrix XenApp (ICAConnect) is designed for Citrix XenApp (usually Citrix XenApp 3.x/4.x/5.x/6.x) environments
  • Direct Desktop Connector
    • Remote protocol: none (DDC bypasses the entire remoting protocol, including brokers and connection servers). DDC directly connects to the VDI VMs on the Hypervisor, including: ESX(i), XenServer, Hyper-V and/or any other Hypervisor with Windows based VDI VMs/operating systems
    • Direct Desktop Connector (DDC) is designed for VDI (usually Citrix XenDesktop 3.x/4.x/5.x/7.x, Microsoft VDI and VMWare Horizon View 4.x/5.x) environments
  • Microsoft Windows
    • Remote Desktop Protocol
    • Microsoft Remote Desktop Protocol (RDP) is designed for Microsoft Remote Desktop Services (formerly known as Terminal Services) and Microsoft VDI (usually Microsoft RDS and Microsoft VDI) environments
  • VMware Horizon View
    • PCoIP
    • VMware Horizon View is designed for VMware Horizon View environments

Connector variables

The Login VSI Management Console, VSI Connectors, VSI Launchers and VSI Launcher Agent have predefined variables that can be used in the command line. The following variables are available to use with the Login VSI Connectors.

  • {VSISHARE}
    • The location of the VSIShare (UNC), optional
  • {server}
    • Will parse the ‘Server’ input from the ‘connection details’, optional
  • {username}
    • Will parse the ‘Username’ input from the ‘connection details’, optional
  • {password}
    • Will parse the ‘Password’ input from the ‘connection details’, optional
  • {domain}
    • Will parse the ‘Domain’ input from the ‘connection details’, optional
  • {count}
    • Will be replaced by an incrementing number. This variable can be used to make the username section of the command line variable between sessions.
    • Use {count/1} for leading zeros. The number indicates the minimum number of digits. For example: LoginVSI{count/1} = LoginVSI1
  /1 = 1, 2, 3 … 10, 11 … 100
  /2 = 01, 02, 03 … 10 … 100
  /3 = 001, 002, 003 … 010 … 100

  Login VSI Connector.exe {count/[0-9]}

Optional arguments:

Parameter

Description

[0-9]

Digits between 0-9 are allowed. For example, LoginVSI{count/999}

Connector error log files - starting with ver4.1.21

We have improved the information contained within the log files for the various connectors featured within Login VSI. These Text documents now provide more detailed information regarding any errors found during testing for all supported connectors. This helps locate problems more easily during the results analysis for all stress and performance tests. After a test has been run, these raw log files can be found in the following location: \\VSIshare\_VSI_Logfiles\Test_name\Monitor.

Connection wizard

The connection wizard, found in the Login VSI Management Console in the ‘test setup > connection’ tab is intended for creating command lines (wizard driven) for each testing environment. Click on 'start connection wizard' in the right upper corner to start the connection wizard

  • Select the connection type required for the target environment and fill in the values for the required connector type

Citrix StoreFront configuration

How to setup a Citrix StoreFront configuration with Login VSI 4.x

  • Citrix Storefront
    • HDX (3D Pro) / ICA
    • Citrix Storefront (SFConnect) is designed for Citrix (usually Citrix XenDesktop 7.x and Citrix Excalibur) environments
  • StoreFront URL (Citrix StoreFront broker/connection server)
    • The exact URL to the Citrix StoreFront Store is required. For example, http://LoginVSI/Citrix/Storename
    • Please note that the exact URL is case sensitive
    • Make sure that the URL does not point to the StoreFront Web (StoreWeb URL), for example, http://LoginVSI/Citrix/StorenameWeb
  • Authentication protocol (on the Launcher)
    • Authentication protocol to use when authorizing to the StoreFront store. To get a list of available protocols, use the /getprotocols argument
  • Connection timeout (on the Launcher)
    • Number of seconds to wait before initiating a new request to the StoreFront site
  • Username
    • Username to use when connecting to the StoreFront store. For example LoginVSI{Count}
  • Password
    • Password to use when connecting to the StoreFront store. For example Password!
  • Resource name (Desktop or Delivery Groups name)
    • Name of the resource to start. To get a list of available resources, use the /getresources argument
  • Color
    • Define the color depth used during the session (valid values: 16, 256, 16bit)
  • Display size type (on the Launcher)
    • The display type that should be used during the session (valid values: seamless, percent, absolute, fullscreen)
  • Display absolute (on the Launcher)
    • The exact width and height of the screen, split by x; example: 800x600 (only if '/display absolute' is used)
  • Display percentage (on the Launcher)
    • The percentage of the screen that should be used for the session (only if '/display percent' is used)
  • Session audio (redirected audio on the Launcher)
    • Define the audio quality for a session (valid values: high, medium, low, off)
  • Windows key combinations (key combinations in the Target)
    • The behaviour of the windows keys, etc. (valid values: local, remote, fullscreenonly)
  • Redirect special folders (to the Target)
    • Are special folders redirected? (valid values: true, false)
  • Remote clear type fonts (in the Target)
    • Are clear type fonts remoted? (valid values: true, false)
  • Enable virtual COM port (to the Target)
    • Specifies whether or not virtual COM ports are enabled or not (valid values: true, false)
  • Allow COM port mapping (to the Target)
    • Specifies whether or not COM port mapping is permitted (valid values: true, false)
  • Allow client print mapping (to the Target)
    • Specifies whether or not client printer queue mapping has been enabled (valid values: true, false)


When the connection wizard is finished a command line is generated. This command line can be used for the Citrix StoreFront testing environment

 

Citrix StoreFront connector options

Before execution remember that the connectors are individual parts and can be found in the VSI share at “\\server\VSIshare\_VSI_Binaries\Connectors”. It is recommended to keep the connectors at the default path. It is allowed to manually call them (CMD) with the help syntax ‘/?’, for example “\\VSISERVER\VSISHARE\_VSI_Binaries\Connectors\SFConnect.exe” /?

It is allowed to modify the command line box manually without the wizard.

  SFConnect.exe [/url URL] [/user USERNAME] [/password PASSWORD] [/proxy PROXY]

Optional arguments:

Parameter

Description

/user

Username to use when connecting to the StoreFront store

/password

Password to use when connecting to the StoreFront store

/domain

Domain to use when Trusted Domains are configured for StoreFront

/proxy

Proxy server to use when connecting to the StoreFront server

/proxyport

Port number to use when a proxy server is defined, if left empty, port 80 will be used

/noproxy

Do not use a proxy when connecting to the StoreFront server (by default SFConnect will use the configured web client proxy)

/resource

Name of the resource to start. To get a list of available resources, use the /getresources argument

/protocol

Protocol name to use when authorizing to the StoreFront store. To get a list of available protocols, use the /getprotocols argument

/timeout

Number of seconds to wait for before the request to the StoreFront site is timed out

/getprotocols

Get the valid authentication protocols from the StoreFront site

/getresources

Get the resources that the defined user has access to from the StoreFront site

/silent

Do not display messages during connection

/audio

Define the audio quality for this session (valid values: high, medium, low, off)

/color

Define that color depth used during the session (valid values: 16, 256, 16bit)

/display

The display type that should be used during the session (valid values: seamless, percent, absolute, fullscreen)

/displaypercent

The percentage of the screen that should be used for the session (only if '/display percent' is used)

/displayabsolute

The exact width and height of the screen, split by x; example: 800x600 (only if '/display absolute' is used)

/keypassthrough

The behaviour of the windows keys, etc. (valid values: local, remote, fullscreenonly)

/folderredirection

Are special folders redirected? (valid values: true, false)

/cleartyperemoting

Are clear type fonts remoted? (valid values: true, false)

/virtualcomport

Specifies whether or not virtual COM ports are enabled or not (valid values: true, false)

/comport

Specifies whether or not COM port mapping is permitted (valid values: true, false)

/clientprinters

Specifies whether or not client printer queue mapping has been enabled (valid values: true, false)


More information:

-Common Citrix StoreFront errors and how to avoid them in a Login VSI test

-Citrix StoreFront Connection Issue – Trusted Domains Only

Citrix Web Interface configuration

How to setup a Citrix XenApp Web Interface configuration with Login VSI 4.x

How to setup a Citrix XenDesktop Web Interface configuration with Login VSI 4.x

The Citrix Web Interface method used in Login VSI will simulate the process like a ‘normal’ end-user would execute. Which means, starting Internet Explorer, browsing to the Citrix Web Interface URL, provide credentials, login and startup a Citrix Resource.

  • Citrix Web Interface
    • HDX (3D Pro) / ICA
    • Citrix Web Interface (CTXConnector) is designed for Citrix (usually Citrix XenApp 3.x/4.x/5.x/6.x and XenDesktop 3.x/4.x/5.x/7.x) environments
  • Web Interface URL
    • The exact URL to the Citrix Web Interface. For example, http://LoginVSI/Citrix/VSI
  • Username
    • Username to use when connecting to the Citrix Web Interface. For example LoginVSI{Count}
  • Password
    • Password to use when connecting to the Citrix Web Interface. For example Password!
  • Domain (optional)
    • Domain to use when connecting to the Citrix Web Interface. For example LAB
    • Optional, if the Citrix Web Interface is configured for predefined domains no domain input is required
  • Published resource (Published desktop, published application or delivery group)
    • Name of the resource to start
    • If the Citrix Web Interface is configured to auto-launch resources it is not required to specify the published resource
  • Tab name (on the Citrix Web Interface, optional)
    • Specify the tab name to click on after the user is authenticated to start the resource (usually “Desktops”). For example, Desktops
    • If the Citrix Web Interface is configured for both Applications and Desktops (resources) the Web Interface page layout/framework will have two tabs instead of one. Usually Applications is the first tab and therefor clicking on the right tab is required
  • Do not click resource (on the Citrix Web Interface, optional)
    • If the Citrix Web Interface is configured to auto-launch resources it is not required to specify the published resource
  • Start resource after (sec.) (on the Citrix Web Interface, optional)
    • The pause (time) between the user logging on and the resources being visible and the user (CTXConnector) attempting to click the resource
    • Depending on how slow or fast the environment is the time is configurable, default is five seconds
  • Wait before IE close (sec.) (on the Citrix Web Interface, optional)
    • The pause (time) between the user clicking the resource and the user (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
    • Depending on how slow or fast the environment is the time is configurable, default is five seconds


When the connection wizard is finished a command line is generated. This command line can be used for the Citrix Web Interface testing environment

 

Citrix Web Interface connector options

Before execution remember that the connectors are individual parts and can be found in the VSI share at “\\server\VSIshare\_VSI_Binaries\Connectors”. It is recommended to keep the connectors at the default path. It is allowed to manually call them (CMD) with the help syntax ‘/?’, for example “\\VSISERVER\VSISHARE\_VSI_Binaries\Connectors\CTXConnector\CTXConnector.exe” /?

It is allowed to modify the command line box manually without the wizard.

  CTXConnector [-s http://webinterfaceserver] [-u user] [-p password] [–d domain] [-r resource]

Optional arguments:

Parameter

Description

-debug

Enables debugging mode, debugging will exactly show what each parameters output is

-s

the site URL that is required to establish a connection to, for example http://LoginVSI/Citrix/VSI

-u

Username to use when connecting to the Web Interface

-d

Domain to use when connecting to the Citrix Web Interface, for example LAB

-p

Password to use when connecting to the Web Interface

-r

Name of the resource to start

-t1

The seconds pause (time) between the user logging on and the resources being visible and the user (CTXConnector) attempting to click the resource

-t2

The seconds pause (time) between the user clicking the resource and user (CTXConnector) attempting to logoff and close Internet Explorer

-n

Changes the name of the logon button that CTXConnector is searching for. If the name of the logon button is different than default

-i

Changes the ID of the logon button that CTXConnector is searching for. If the ID of the logon button is different than default

-w

Changes the ‘User name:’ ID/field that CTXConnector is waits for before continuing with the logon sequence. If the ID/field of the ‘User name:’ is different than default. For example, Web Interface in foreign languages

-nu

Changes the ‘User name:’ input field that CTXConnector is searching for. If the ID/field of the ‘User name:’ text field is different than default. For example, Web Interface in foreign languages

-np

Changes the Password input field that CTXConnector is searching for. If the ID/field of the ‘Password:’ text field is different than default. For example, Web Interface in foreign languages

-nd

Changes the Domain input field that CTXConnector is searching for. If the ID/field of the ‘Domain:’ text field is different than default. For example, Web Interface in foreign languages

-tab

Specify the tab name to click on after the user is authenticated to start the resource (usually “Desktops”). For example, Desktop

-dontclose

Will not close IE after finishing

-dontlogoff

Will not logoff user after finishing

-noclick

Will not click on the resource. If the Citrix Web Interface is configured to auto-launch resources it is not allowed/needed to specify the published resource

Citrix XenApp configuration

How to setup a Citrix XenApp and Citrix XenApp Web Interface configuration with Login VSI 4.x

  • Citrix XenApp
    • HDX (3D Pro) / ICA
    • Citrix XenApp (ICAConnect) is designed for Citrix XenApp (usually Citrix XenApp 3.x/4.x/5.x/6.x) environments
  • Published application (published desktop/target)
    • Published application name (not display name) to connect to. If this option is not set, the connection will be made to the server's desktop. For example, LoginVSI
  • Citrix server
    • XenApp server to connect to; if the /uselb switch is set, this server is used to do load-balancing. For example, XenApp1
  • Use Citrix load balancing (on a Citrix Farm, optional)
    • Use load balancing instead of making a connection directly to the server defined in the /server option
  • XML port (for Citrix server)
    • Specify the XML port to use (only valid with the /uselb switch)
  • Encryption level (for the connection to the Target)
    • Encryption level of the ICA sessions (valid values: Basic, RC5-Logon, RC5-40, RC5-56, RC5-128)
  • Username
    • Username to use when connecting to the Citrix XenApp server. For example LoginVSI{Count}
  • Password
    • Password to use when connecting to the Citrix XenApp server. For example Password!
  • Domain (optional)
    • Domain to use when connecting to the Citrix XenApp server. For example LAB
    • Optional, if the Citrix Web Interface is configured for predefined domains no domain input is required
  • Color (on the Launcher)
    • Color depth to use in ICA session (valid values: 16, 256, 16bit, 24bit, 32bit)
  • Resolution (on the Launcher)
    • Resolution to use in ICA session; the width and height values are split by the "x" character (eg. 800x600)


When the connection wizard is finished a command line is generated. This command line can be used for the Citrix XenApp testing environment

 

Citrix XenApp connector options

Before execution remember that the connectors are individual parts and can be found in the VSI share at “\\server\VSIshare\_VSI_Binaries\Connectors”. It is recommended to keep the connectors at the default path. It is allowed to manually call them (CMD) with the help syntax ‘/?’, for example “\\VSISERVER\VSISHARE\_VSI_Binaries\Connectors\ICAConnect\ICAConnect.exe” /?

It is allowed to modify the command line box manually without the wizard.

  ICAConnect.exe [/server SERVER] [/user USERNAME] [/password PASSWORD]

Optional arguments:

Parameter

Description

/server

XenApp server to connect to; if the /uselb switch is set, this server is used to do load-balancing

/user

Username to use when connecting to the XenApp server

/password

Password to use when connecting to the XenApp server

/domain

Domain to use when connecting to the XenApp server

/application

Published application name (not display name) to connect to. If this option is not set, the connection will be made to the server's desktop

/xmlport

Specify the XML port to use (only valid with the /uselb switch)

/color

Color depth to use in ICA session (valid values: 16, 256, 16bit, 24bit, 32bit)

/resolution

Resolution to use in ICA session; the width and height values are split by the "x" character (eg. 800x600)

/seamless

Start the published application in seamless mode

/uselb

Use load balancing instead of making a connection directly to the server defined in the /server option

/lbtype

Browser type to use when connecting; this option isonly used when the /uselb option is used (valid values: TCP, HTTP)

/encryption

Encryption level of the ICA sessions (valid values: Basic, RC5-Logon, RC5-40, RC5-56, RC5-128)

/silent

Do not output any messages to the console

Direct Desktop Connector (DDC) configuration

How to setup a Direct Desktop Connector (DDC) configuration with Login VSI 4.x

  • DDC
    • DDC bypasses the entire remoting protocol, including brokers and connection servers. DDC directly connects to the VDI VMs on the Hypervisor, including: ESX(i), XenServer, Hyper-V and/or any other Hypervisor with Windows based VDI VMs/operating systems
    • DDC is designed for VDI (usually Citrix XenDesktop 3.x/4.x/5.x/7.x, Microsoft VDI and VMWare View 4.x/5.x) environments
    • DDC is not supported for Windows XP
  • Target machine (VDI VM)
    • The target to make the (console) connection to. For example LoginVSI_VDI{Count}
  • Username
    • Username to use when connecting to the target. For example LoginVSI{Count}
  • Password
    • Password to use when connecting to the target. For example Password!
  • Domain
    • Domain to use when connecting to the target. For example LAB


When the connection wizard is finished a command line is generated. This command line can be used for the VDI testing environment

 

Direct Desktop connector options

Before execution remember that the connectors are individual parts and can be found in the VSI share at “\\server\VSIshare\_VSI_Binaries\Connectors”. It is recommended to keep the connectors at the default path. It is allowed to manually call them (CMD) with the help syntax ‘/?’, for example “\\VSISERVER\VSISHARE\_VSI_Binaries\Connectors\ConsoleConnector\DDC.exe” /?

It is allowed to modify the command line box manually without the wizard.

  DDC.exe [/server SERVER] [/user USER] [/password PASSWORD] [/domain DOMAIN]

Optional arguments:

Parameter

Description

/server

The target to make the (console) connection to. For example LoginVSI_VDI{Count}

/user

Username to use when connecting to the target. For example LoginVSI{Count}

/password

Password to use when connecting to the target. For example Password!

/domain

Domain to use when connecting to the target. For example LAB

Microsoft (RDP) configuration

How to setup a Microsoft (RDP) configuration with Login VSI 4.x

  • Microsoft Remote Desktop Protocol
    • RDP
    • Microsoft RDP is designed for Microsoft Remote Desktop Services (Formerly known as Terminal Services) and Microsoft VDI (usually Microsoft RDS and Microsoft VDI) environments
  • RD Session Host (the Remote Desktop Services (RDS), formerly known as Terminal Services (TS) and VDI targets)
    • The target to make the connection to. For example LoginVSI_VDI{Count} or 2012RDS{Count}
  • Username
    • Username to use when connecting to the target (can be DOMAIN\USER). For example LoginVSI{Count}
  • Password
    • Password to use when connecting to the target. For example Password!
  • Domain (optional)
    • Domain to use when connecting to the target. For example LAB
    • Optional, if the RD Session Host is configured for predefined domains no domain input is required
  • Suppress warnings (on the Launcher, optional)
    • Suppress warnings if the publisher can't be verified
  • Fullscreen (on the Launcher, optional)
    • Use full screen mode as resolution (the /display value will be ignored)
  • Resolution (on the Launcher, optional)
    • The screen size to use for this RDP connection, split by x; for example: 800x600 (leave empty for fullscreen)
  • Color (on the Launcher, optional)
    • The color depth to use for this connection (valid values: 15bit, 16bit, 24bit, 32bit)
  • Scale session (on the Launcher, optional)
    • Scale the session in the RDP window (Windows 2008 R2 and up)
  • Map clipboard (from the Launcher, optional)
    • Redirect local clipboard to the RDP session (valid values: true, false)
  • Map COM ports (from the Launcher, optional)
    • Redirect local COM ports to the RDP session (valid values: true, false)
  • Map drives (from the Launcher, optional)
    • Redirect defined local drives to the RDP session, specify each drive separated by "," (e.g. C: , G:) or use "ALL" to connect all drives
  • Map printers (from the Launcher, optional)
    • Redirect local printers to the RDP session (valid values: true, false)
  • Map smartcards (from the Launcher, optional)
    • Redirect smartcards to the RDP session (valid values: true, false)
  • Map PnP devices (from the Launcher, optional)
    • Redirect drives that are plugged in later (if the /mapdrives option is set to "ALL", this option is set to true by default) (valid values: true, false)
  • Connection optimization (for the Launcher, optional)
    • The connection speed to optimize performance (valid values: modem, low, satellite, high, wan, lan)
  • Desktop background (on the Target, optional)
    • Allow desktop background (valid values: true, false)
  • Font smoothing (on the Target, optional)
    • Allow font smoothing (valid values: true, false)
  • Desktop composition (on the Launcher, optional)
    • Allow desktop composition (valid values: true, false)
  • Show dragging content (on the Target, optional)
    • Allow showing the window content while dragging (valid values: true, false)
  • Allow animations (on the Target, optional)
    • Allow menu and window animations (valid values: true, false)
  • Visual styles (on the Target, optional)
    • Allow visual styles (themes) (valid values: true, false)
  • Remote Desktop (RD) Gateway mode (connect to the Target via RDG, optional)
    • What kind of RD Gateway mode to use; No RD Gateway, Automatically detect or Manual entry (use the /rdgateway argument) (valid values: none, auto, manual)
  • RD Gateway address (connect to the Target via RDG, optional)
    • Server name to use as RD Gateway
  • Logon method (to connect to Target, optional)
    • RD Gateway logon method; Allow me to select later, Ask for password (NTLM) or Smart card (valid values: select, ask, smartcard)
  • Bypass for local addresses (on the Target, optional)
    • Bypass RD Gateway server for local addresses (valid values: true, false)
  • Use RDG credentials (on the Target, optional)
    • Use RD Gateway credentials for the remote computer (valid values: true, false)


When the connection wizard is finished a command line is generated. This command line can be used for the Microsoft Remote Desktop testing environment

 

Microsoft RDP connector options

Before execution remember that the connectors are individual parts and can be found in the VSI share at “\\server\VSIshare\_VSI_Binaries\Connectors”. It is recommended to keep the connectors at the default path. It is allowed to manually call them (CMD) with the help syntax ‘/?’, for example “\\VSISERVER\VSISHARE\_VSI_Binaries\Connectors\RDPConnect.exe” /?

It is allowed to modify the command line box manually without the wizard.

  RDPConnect.exe [/server SERVER] [/user USER] [/password PASSWORD] [/nowarning]

Optional arguments:

Parameter

Description

/server

The server/target to make the RDP connection to. For example /server 2012RDS{Count}

/user

Username to use when connecting to the target (can be DOMAIN\USER). For example LoginVSI{Count}

/password

Password to use when connecting to the target. For example Password!

/nowarning

Suppress warnings if the publisher can't be verified

/admin

Connect to the administrative session (Windows 2008 R2 and up)

/fullscreen

Use full screen mode as resolution (the /display value will be ignored)

/scale

Scale the session in the RDP window (Windows 2008 R2 and up)

/display

The screen size to use for this RDP connection, split by x; for example: 800x600 (leave empty for fullscreen)

/usealldisplays

Stretch the RDP connection over all available monitors

/span

Used in combination with /usealldisplays; if the client OS is lower than Windows 7 and the server OS is lower than Windows 2008R2, use this setting to enable multi monitor support.

/color

The color depth to use for this connection (valid values: 15bit, 16bit, 24bit, 32bit)

/hideconnectionbar

Do not display the connection bar in fullscreen mode

/cbbtnhideminimize

Hide the minimize button in the connection bar (Windows CE 5.0)

/cbbtnhidepin

Hide the pin button in the connection bar (Windows CE 5.0)

/cbbtnhiderestore

Hide the restore button in the connection bar (Windows CE 5.0)

/cbpinned

Pin the connection bar to the window (Windows CE 5.0) (valid values: true, false)

/remoteaudio

Remote audio playback mode; Play on this computer, Do not play or Play on remote computer (valid values: local, none, remote)

/remoterecording

Remote audio recording mode; Record from this computer or Do not record (valid values: local, none)

/windowskeys

Apply Windows key combinations; On this computer, on the remote computer or Only when using the full screen (valid values: local, remote, fullscreenonly)

/mapclipboard

Redirect local clipboard to the RDP session (valid values: true, false)

/mapcomports

Redirect local COM ports to the RDP session (valid values: true, false)

/mapdrives

Redirect defined local drives to the RDP session, specify each drive separated by "," (eg. C:,G:) or use "ALL" to connect all drives.

/mapplugdrives

Redirect drives that are plugged in later (if the /mapdrives option is set to "ALL", this option is set to true by default) (valid values: true, false)

/mapprinters

Redirect local printers to the RDP session (valid values: true, false)

/mapsmartcards

Redirect smartcards to the RDP session (valid values: true, false)

/mappnpdevices

Redirect other supported PnP devices

/startprogram

Start this program (path and filename) on connection

/startworkingfolder

The working folder when starting the program (only applicable when the /startprogram is used)

/connection

The connection speed to optimize performance (valid values: modem, low, satellite, high, wan, lan)

/desktopbackground

Allow desktop background (valid values: true, false)

/fontsmoothing

Allow font smoothing (valid values: true, false)

/desktopcomposition

Allow desktop composition (valid values: true, false)

/showdraggingcontent

Allow showing the window content while dragging (valid values: true, false)

/animations

Allow menu and window animations (valid values: true, false)

/visualstyles

Allow visual styles (themes) (valid values: true, false)

/bitmapcaching

Allow persistent bitmap caching (valid values: true, false)

/negotiatesecurity

Negotiate the security layer (valid values: true, false)

/reconnect

Reconnect if the connection is dropped (valid values: true, false)

/authenticationfail

What to do when server authentication fails (valid values: disconnect, warn, connect, none)

/rdgatewaymode

What kind of RD Gateway mode to use; No RD Gateway, Automatically detect or Manual entry (use the /rdgateway argument) (valid values: none, auto, manual)

/rdgateway

Server name to use as RD Gateway

/rdlogon

RD Gateway logon method; Allow me to select later, Ask for password (NTLM) or Smart card (valid values: select, ask, smartcard)

/rdbypasslocal

Bypass RD Gateway server for local addresses (valid values: true, false)

/rdusecredentials

Use RD Gateway credentials for the remote computer (valid values: true, false)

/cacherdpfile

Do not remove the generated RDP file after it has been launched

/timeout

Number of seconds to wait before the RDP file is removed after launch

/template

Use the specified RDP file as template (only overwrite defined command line arguments)

VMware Horizon View configuration

How to setup a VMware Horizon View configuration with Login VSI 4.x

  • VMware Horizon View
    • PCoIP
    • VMware Horizon View PCoIP is designed for VMware Horizon View environments
  • VMware Horizon View Agent path (on the Launcher)
    • View Agent (client) path, predefined default path
  • Username
    • Username to use when connecting to the VMware Horizon View connection server/broker. For example LoginVSI{Count}
  • Password
    • Password to use when connecting to the target. For example Password!
  • Domain
    • Domain to use when connecting to the target. For example LAB
  • VMware Horizon View Connection Server (connection server/broker)
    • VMware Horizon View Connection Server to use when connecting to the VMware Horizon View environment (pool/desktop). For example vcs.loginvsi.com
    • It is allowed to connect to the Connection Server via URL, IP address, DNS or FQDN of the Connection Server
  • Desktop name (pool name on the View Connection Server)
    • The desktop/pool name to make the connection to. For example LoginVSI_VDI or LoginVSI_VMware_Horizon
    • Specifies the name of the desktop as it would appear in the Select Desktop dialog box. This is the name as you see it in the select desktop dialog
  • Connect USB on startup (from the Launcher, optional)
    • Redirects USB devices that are plugged in
    • When set to true, redirects all USB devices to the desktop that are currently connected to the host. The default is false


When the connection wizard is finished a command line is generated. This command line can be used for the VMware Horizon View testing environment


 

VMware View connector options

Before execution remember that the view client connector is an individual shipped installation setup from VMware Horizon View and can be found in the predefined default path. It is allowed to manually call them (CMD) with the help syntax ‘/?’, for example “C:\Program Files\VMware\VMware View\Client\bin\wswc.exe” (default VMware View path) /? or for VMware client 3.0 and up it is "C:\Program Files (x86)\VMware\VMware Horizon View Client\vmware-view.exe"

It is allowed to modify the command line box manually without the wizard.

  wswc.exe [-serverURL SERVER] [-username USERNAME] [-password PASSWORD] [–domainName DOMAIN] [–desktopName DESKTOPNAME]

Optional arguments: the latest available arguments can be found on: http://www.vmware.com/support/pubs/view_pubs.html

 

Related articles

Comments

0 comments

Article is closed for comments.