9.5.6a (9.5.6.2815) Maintenance Release - 18 June 2021

The VSA 9.5.6.2815 release includes bug fix described in the topic below. For minimum system and agent requirements, see these topics in the Kaseya R95 System Requirements Guide: Kaseya Server Minimum Requirements & Configuration and Agent Minimum Requirements. 

This release requires agent version 9.5.0.23. Be sure to update your Windows, Mac, and Linux agents after installing this release. 

Bug Fixes

Authentication

Fixed an issue where the latest versions of Firefox, Chrome, and Edge failed to authenticate third-party integration (TAP) modules, including Spanning O365 Backup and Unitrends. When attempting to access modules, VSA login page would be displayed instead of expected content. 

Pre-requisites 

This fix is dependent on recent updates to .NET Framework being installed on the VSA server. 

Server 2012 R2 - Must have “Security and Quality Rollup for .NET Framework” from December 2019 or later. Please note that this will be displayed in Windows Update as an “optional” update. 

Server 2016 or 2019 - Must have “Cumulative Update for Windows Server” from December 2019 or later. 

Known Issues 

  • VSA server cookies must be cleared from browser before fix will take effect: -
    • Load VSA 
    • Click F12 to access Dev Tools 
    • Click on Application tab > Storage > Cookies – right click on VSA server address and click Clear. 
    • Refresh page using F5, then login to VSA (you will need to re-authenticate with 2FA if device was remembered) 
  • The fix for the third-party integration issue introduces a new issue where Service Desk module cannot be accessed from inside the Live Connect application. User Portal and Live Connect web interface are NOT affected. This will be corrected in a future release.
    • Workaround – use VSA web interface with a machine-based filter, or Live Connect web interface, to access Service Desk tickets for a specific machine. 
  • Introduces a new issue where certain pages in Traverse module return Oops error page. This will be corrected in a future release. 
    • Traverse > Monitoring > Network Map;
    • Traverse > Reporting > Dashboards.

To use Live Connect web interface: 

  1.     Enter https://<server-address>/liveconnect in web browser. 
  2.     Log in to your account. 
  3.     Click on any machine to open Live Connect session - the Ticket function should display the same Service Desk content that would usually be available in Live Connect app. 

 

 

Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section