Symptom

There are Login VSI error message boxes about executables (.exes) not existing during a test, when a Login VSI workload function expects the executables to be on the Login VSI targets.

Cause

One potential reason this could occur is client antivirus software is either preventing executables from being downloaded from the share to the local targets, the files are being deleted once downloaded to the target by the antivirus software, or the antivirus software is preventing the executables from running.

Resolution

The executables that should be whitelisted in client antivirus are (these will affect the target runtime):

• Source: \\{LoginVSI_Server}\{LoginVSI_Share}\_vsi_binaries\target\lib\7za.exe
  • Target destination: %temp%\vsi\runtime\lib\7za.exe
• Source: \\{LoginVSI_Server}\{LoginVSI_Share}\_vsi_binaries\target\lib\freemind\Freemind.exe
  • Target destination: %temp%\vsi\runtime\lib\freemind\freemind.exe
• Source: \\{LoginVSI_Server}\{LoginVSI_Share}\_vsi_binaries\target\lib\freemind\unins000.exe
  • Target destination: %temp%\vsi\runtime\lib\freemind\unins000.exe
• Source: \\{LoginVSI_Server}\{LoginVSI_Share}\_vsi_binaries\target\VSI.exe
  • Target destination: %temp%\vsi\runtime\vsi.exe
    
• Source: \\{LoginVSI_Server}\{LoginVSI_Share}\_vsi_binaries\target\VSIDate.exe
  • Target destination: %temp%\vsi\runtime\vsidate.exe
    
• Source: \\{LoginVSI_Server}\{LoginVSI_Share}\_vsi_binaries\target\lib\VSIFakeInstaller.exe
  • Target destination: %temp%\vsi\runtime\lib\vsifakeinstaller.exe
• Source: \\{LoginVSI_Server}\{LoginVSI_Share}\_vsi_binaries\target\lib\VSIMemoryEater.exe
  • Target destination: %temp%\vsi\runtime\lib\vsimemoryeater.exe
• Source: \\{LoginVSI_Server}\{LoginVSI_Share}\_vsi_binaries\target\lib\VSINotepad.exe
  • Target destination: %temp%\vsi\runtime\lib\vsinotepad.exe
    
• Source: \\{LoginVSI_Server}\{LoginVSI_Share}\_vsi_binaries\target\lib\VSIPictureViewer.exe
  • Target destination: %temp%\vsi\runtime\lib\vsipictureviewer.exe
    
• Source: \\{LoginVSI_Server}\{LoginVSI_Share}\_vsi_binaries\target\lib\WinAudit.exe
  • Target destination: %temp%\vsi\runtime\lib\winaudit.exe
    
• Source: \\{LoginVSI_Server}\{LoginVSI_Share}\_vsi_binaries\target\lib\LoginVSIStartApp.exe (only in Login VSI 4.1.7 and newer)
  • Target destination: %temp%\vsi\runtime\lib\loginvsistartapp.exe
    

In case of AV on the VSI server, the VSI server binaries that should be whitelisted are:

• \\{vsi server}\{vsi share}\_VSI_ManagementConsole\Login VSI Management Console.exe
• \\{vsi server}\{vsi share}\_VSI_ManagementConsole\LoginVSICMD.exe
• \\{vsi server}\{vsi share}\_VSI_Binaries\RAMDisk\imdiskinst.exe
• \\{vsi server}\{vsi share}\_VSI_Binaries\Launcher\VSIDebug.exe
• \\{vsi server}\{vsi share}\_VSI_Binaries\Launcher\SessionMonitor.exe
• \\{vsi server}\{vsi share}\_VSI_Binaries\Launcher\Helper.exe
• \\{vsi server}\{vsi share}\_VSI_Binaries\Launcher\Agent.exe
• \\{vsi server}\{vsi share}\_VSI_Binaries\Connectors\ICAConnect\ICAConnect.exe
• \\{vsi server}\{vsi share}\_VSI_Binaries\Connectors\CTXConnector\CTXConnector.exe
• \\{vsi server}\{vsi share}\_VSI_Binaries\Connectors\ConsoleConnector\DDC.exe
• \\{vsi server}\{vsi share}\_VSI_Binaries\Connectors\SFConnect.exe
• \\{vsi server}\{vsi share}\_VSI_Binaries\Connectors\RDPConnect.exe
• \\{vsi server}\{vsi share}\_VSI_Binaries\Connectors\LoginVSI.Connectors.Connect.exe
• \\{vsi server}\{vsi share}\_VSI_Binaries\Analyzer\Login VSI Analyzer.exe
• \\{vsi server}\{vsi share}\_VSI_Binaries\Analyzer\Login VSI Analyzer Console.exe

The originating paths of these files are from 

Properties

Applies to

Login VSI 4.x

See Also

How the logon phase works