Troubleshooting

1. General

The software does not start...

• The Login VSI Launcher and Analyzer require the .Net framework version 3.5, the analyzer also requires the MSChart component.
• Make sure you are running the latest version. Download Login VSI.
• The license file has expired, request a new license.

Can I run multiple tests at once...

• Yes this is no problem, however each test has to be configured to use a seperate VSIShare

Does Login VSI Support all languages ..?

• Yes, By default Login VSI runs on English OS + Office but can be configured to run on any language; The free version of Login VSI (Express) only supports English OS and Office versions.

2. Active Directory Deployment

No users are created by the setup…

• Make sure GPMC is installed
• Check if the installation user has sufficient rights to perform the following actions
  • Create OU
  • Apply GPO
  • Add Users
  • Add Groups
  • Add users to groups

3. Target

The user logs on to the target machine but nothing happens…

• Did you move the target machine to the correct OU? “Login VSI\Computers”, and is the ”VSI System” policy attached to that OU.
• Is running scripts simultaneously disabled?
• Is your security agent blocking the execution of the Login VSI executables / Login script?
• Do the Login VSI users have access to the Login VSI Share ? You can simply test this by accessing \\Server\VSIShare from within a session.
• Did you or Login VSI create the logon scripts that are used in the netlogon folder ? \\DomainName\Netlogon\VSI_Logon.cmd

The script stops at a print dialog window…

• Please set the default printer to “Bulzip PDF Printer” and make sure this value does not get overruled by a session printer (Redirected printer).
• When running Microsoft Office 2010 set the office version to 14 in the Management console

The script stops at a save as window and tries to save an XPS document…

• Please set the default printer to “Bulzip PDF Printer” and make sure this value does not get overruled by a session printer (Redirected printer). You can also delete all printers at the launchers to resolve this issue.

Outlook does not get configured automatically by Login VSI...

• Did you move the target machine to the correct OU? “Login VSI\Computers”, and is the ”VSI System” policy attached to that OU.

The scripts try to start Microsoft Outlook from the wrong location...

• Specify Outlook_Location in the Management Console

The scripts try to start Microsoft Word from the wrong location...

• Specify Word_Location in the Management Console

Office is showing the activation wizard...

• Login VSI does not activate your version of office, but requires an already activated version to be able to run succesfully.

The script stops when displaying [Find/Calculator/Outlook/Excel/Adobe Reader/ Open

• This happens when using a non English operating system or MUI, specify the window title of the application Login VSI is trying to target in the Management Console [ Pro ]
• This happens when running a non English Office version or MUI, Specify the window title of the application Login VSI is trying to target in the Management Console [ Pro ]

The Script tells me there is no active test…

• Make sure the launcher and target machines are configured to use the same fileshare.
• Make sure the users logged on to the launchers have `Write` permissions at the VSIShare
• Make sure the users logged on to the target machines have `Write` permissions at the VSIShare
• Make sure antivirus solutions are not blocking scripts to write at the VSIShare

The script stops at random places during the session…

• Make sure the scripts do not get disturbed by application popups eg: Virus scanners, Security warnings, office plugins.

How can I see what Login VSI tries to execute…

• Check the debug logfile located: %temp%\VSI\Log\%username%_Debug.log, Pro users can configure Login VSI to automatically move these logfiles to the Login VSIShare.

It seems like the CTRL key gets stuck during a test (On a RDS / XenApp machine)

• Setting the following registry key can resolve the issue:

Windows Registry Editor Version 5.00
 
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server]
"IAT"=dword:00000001

Can I add my own application set to the workloads ? [ Pro ]

• Yes you can, this is possible with Login VSI Pro.

Internet Explorer Enhanced Security Configuration (ESC) does not seem to disable

• Remove the Harden key from the registry

Users do not automatically logoff...

• Have you enabled "Auto Logoff" at the Management Console ?
• Are programs preventing the Logoff (e.g. Not responding)
• Do users have sufficient rights to execute "Shutdown /l" ?

4. Launcher

The launcher starts a Citrix session and then loggs it off immediately…

• Make sure that closing the webinterface does not logoff sessions (webinterface configuration)

CTXCONNECT does not enter credentials in the Citrix Webinterface…

• Try enabling protected mode for the intranet zone in Internet explorer

The launcher does not start my ICA connection…

• Check if the Citrix client is installed

The launcher does not start my connection using LaunchRDP.exe...

• Check the supported parameters on the target systems page.
• Make sure not to append the dns suffix to the domain name (e.g. instead of contoso.local use contoso)

The launcher keeps saying my launchers are "Not ready"

• Add the launchers using their hostname, not using the FQDN

The Launched and/or Active sessions counters don't seem to work...

• Make sure the SessionMonitor.exe is running
• Make sure the user running SessionMonitor.exe has sufficient rights on the VSIShare (Write)
• Make sure the SessionMonitor is looking Pat the correct VSIShare

I do not want or cannot use the default user/machine numbering when launching sessions…

• Use the “Custom command line with CSV” option available in the launcher to configure complex launching schemes.

The Agent does not start any sessions when i run a test…

Windows Registry Editor Version 5.00 
 
[HKEY_CURRENT_USER\Software\Login Consultants\VSI Launcher]
"VSIShare"="\\\\Server\\VSIShare"

[HKEY_CURRENT_USER\Software\Login Consultants\VSI Management Console]
"VSIShare"="\\\\Server\\VSIShare"
"VSILicense"="\\\\Server\\VSIShare\\_VSI_Configuration\\LoginVSI.lic"
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Login Consultants\VSI Launcher]
"VSIShare"="\\\\Server\\VSIShare"