Login VSI - How to upgrade to Login VSI 4.1.25 (legacy)

This article will assist you with upgrading from 4.x to 4.1.25. All common encountered known issues will be listed.

Upgrade Preparation

• Read the release notes between the currently installed version and the version being upgraded to: https://www.loginvsi.com/documentation/index.php?title=Login_VSI_Release_Notes
• Note that the launcher workflow feature has changed. Please navigate to the fourth page of the Start Test Wizard, named Launcher workflow, to see if this feature is currently in use.​
• If the launcher workflow is in use:
  
  • Ensure the Login VSI Server is compatible with RDP version 8.1 or higher
    
    • Open the Remote Desktop Connection and navigate to About
      
    • The compliant version will be listed here
      
    • For more information read: https://loginvsi.zendesk.com/hc/en-us/articles/115002632589 
  • Ensure the launcher user is a local administrator on the launcher systems
• To be safe, backup the Login VSIshare before starting the upgrade process (the installation directory)

Upgrade Process

• Download the 4.1.25 upgrade patch from: https://www.loginvsi.com/downloads/login-vsi
• If a Login VSI test is in progress, allow it to complete or abort the test
• Close out of any Launcher Agents running on the launcher systems—the process name is agent.exe
• Execute and perform the upgrade patch
• Restart the Login VSI Server once the upgrade is complete

Post upgrade to ver4.1.25

After the upgrade, there are a couple of known issues that can be potentially encountered:

• The target testing engine (vsi.exe) may generate false-positive stuck sessions. The message box pop-up that's generated will include the text: "The window with title <title> exists but not responding." 
  
  • For the explanation and resolution, read: https://loginvsi.zendesk.com/hc/en-us/articles/115002775425
• The launcher workflow might show launchers getting stuck on the status of RdpSuccessful. This will prevent the launcher workflow feature from completing, meaning the test can't be started.
  
  • For the explanation and resolution, read: https://loginvsi.zendesk.com/hc/en-us/articles/115002911405