The VSA 184.108.40.20615 release includes 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.
- SaaS deployment - completed July 17th - 19th
- General Availability (on-prem customers) - Released July 20th, 9.30am EDT
Note: SaaS customers will be informed of their maintenance window via https://status.kaseya.net.
Dates are subject to change at short notice. On-prem customers are advised to check this page again prior to attempting an upgrade.
- Fixed an issue where it was not possible to update the agent to the latest version.
- Fixed an issue where an “Oops” error was displayed while clicking the Apply button in the Unlisted section on the Agent > Protection > Network Access page.
- Fixed an issue where an “Oops” error was displayed while clicking the Enable button for Notify user when app blocked on the Agent > Protection > Network Access page.
- Fixed an issue where Agent Machines did not display on the Templates: Rename, Delete, Change Group, and Set Credential pages.
- Fixed an issue where some system generated procedures were not getting automatically signed and approved, and would fail to execute.
- Fixed an issue where the system failed to create a schedule for the Agent Procedure.
- Fixed an issue where agent procedures with shell commands containing ^ and backtick would fail to execute. This was known to be impacting the Bitdefender TAP integration.
- Fixed an issue where an “Oops” error was displayed after clicking the Select machine ID option on the Configure > Install/Remove tab.
- Fixed an issue where Quick View did not display in Topology Map.
- Fixed an issue where permission reset/assignment failed during the patch installation.
- Fixed an issue where KServer crashed after launching the latest patch release.
- Fixed an issue where an “Oops” error was displayed when trying to load MIB files.
- Fixed an issue where Monitors did not respond on Machines and an error displayed in the Agent Procedure logs.
- Fixed an issue where the System Preferences > Naming Policy page failed to load.
- Fixed an issue where Active Directory domain users would be prompted to change their password on login to VSA, even though they have already changed it in Active Directory.
- Added instructions to the Change Logon page to state that Active Directory domain users must first change their password in Windows, and then log in to VSA with the new password.
- IMPORTANT - please note that when the VSA login policy requires a password change, domain users must change their Active Directory password in Windows before they can use it to log in to VSA, even if the password is not expired in Active Directory.