Please see our latest notes for our VSA 9.5.1 Release.
9.5.1 Patch Release - 12 September 2020
The VSA 9.5.1 release includes the enhancements and fixes described in the topics 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.
Important! This release requires agent version 126.96.36.199. Be sure to update your Windows, Mac, and Linux agents after installing this release.
Please be informed that in the this VSA release Two-Factor Authentication (2FA) will become mandatory on all VSA On-Premises user logins.
This change will bring On-Premises VSA into parity with SaaS VSA as it relates to the use of 2FA for protecting user logins when accessing the VSA UI.
For more information on VSA 2FA, including educational material, please click this link for the KB article.
Deprecated legacy API call (/api/v1.0/sample/environment).
Added support for PingID as a SAML provider for SSO in the AuthAnvil module.
Added additional BMS integration logging to system log.
Added the ability to transfer files directly between the source machine and the remote control target, directly within the remote control application. In this case, users do not have to use the Live Connect application to transfer files while working in an active Remote Control session.
File transfer functionality can be triggered by the following user initiated actions to and from:
As a part of this new feature, we added an option called 'Disable Remote Control File Transfer' under User Role Policy and Machine Policy pages. By setting this option, File Transfer capabilities within Remote Control will be explicitly disabled for specific User Roles, and/or specific machines. Note that by VSA design, Machine Policy takes precedence over User Role Policy. For example, if a VSA agent has RC File Transfer “disabled” in its Machine Policy, RC File Transfer will be disabled for any user of VSA when Remote Controlling said device. If RC File Transfer is not “disabled” in a Machine Policy but is “disabled” in a User Role Policy, RC File Transfer will be disabled for any Remote Control session performed while such User Role is in use.
‘Disable Remote Control File Transfer’ is exclusive to Remote Control and does not affect file transfer capabilities of Live Connect.
For more information regarding this feature, refer to this KB Article.
Providing a feature where user can search registry path in Live Connect's Registry Editor to quickly locate the registry data on an endpoint. The previous search should be cleared any time by clicking on refresh before searching again. Searching text should start with HKEY and NOT Computers\ like regedit. User can also copy the registry path that they mentioned on search text box by clicking provide 'copy' icon and paste it anywhere using Ctrl+V.
Does the mandatory 2FA affect our bms service account used for integration? If so, what is the workaround?
Mandatory MFA does not impact any service accounts utilized for integrations which leverage our API.
Can you elaborate on what exactly was the increased to security to the 1-Click feature? Would like to know details so we can decide if it is secure enough to use now
Does "drag and drop" file transfer only work in one direction (not sure if just me)? Any reason they didnt make it work in both directions?
Eddy - I believe that refers to the ability to include/exclude a machine via [Remote Control\Policy Settings\Machine Policy OR User Policy\1-Click Access]... Meaning you can control what users Roles have 1-click access and further can restrict access per machine even to a Role with Access. Machine Role takes precedence over User Role.
Elliot Tabush - Yes, Drag and Drop is only Unidirectional in this release. Bidirectional feature is still planned, its in the backlog.
Vice President, Global Product Enablement