The VSA 9.5.22 feature release (build 9.5.22.7018) includes enhancements and fixes described in the following sections. For minimum system and agent requirements, refer to Kaseya Server Minimum Requirements & Configuration and Agent Minimum Requirements.
Release schedule
- SaaS deployment started: Saturday, March 1st, 2025
- SaaS deployment completed: Saturday, March 15th, 2025
- General Availability (on-premises customers): Tuesday, April 1st, 2025 - Available Now!
Note: SaaS customers will be informed of their maintenance window via status.kaseya.com.
Dates are subject to change at short notice. On-premises customers are advised to check this page again before attempting an upgrade.
Last Update: March 25th, 2025 - General Availability date changed from March 25th to April 1st.
Important security update
This release includes important security updates. We recommend that on-premises customers upgrade as soon as possible after the General Availability (GA) release date. (No action is required for SaaS customers, as updates are automatically applied).
Dependencies
| Agent |
This release requires agent version 9.5.0.47. After upgrading from an earlier VSA version, you must update your Windows, macOS, and Linux agents using the automatic or manual update process from the agent module. Note: this version cannot be installed to some End-of-Life macOS versions. Please reference the "Updates to macOS and Linux agent supported versions" section below for further details. |
| Live Connect Application | When starting a Live Connect or Remote Control session for the first time after installing this release, you will be prompted with a link to download the latest Live Connect build. You must complete the installation before proceeding with the session. |
| Software Management |
This release includes updates to the Software Management client code. Each managed machine will download 120 MB of file updates during the first patch scan or deployment cycle after installing the VSA update. The files will be sourced from the VSA server or a peer endpoint machine on the local network that already has the files. Recommendations to mitigate the impact on network bandwidth:
|
Support policy for prior releases
Kaseya recommends that customers update their environments to the latest patch release as soon as possible after the GA release date.
Our policy is to provide support for the current GA release, one prior Feature Release, and any interim Maintenance Releases. After the 9.5.22 GA date stated in the release schedule, the minimum supported version will be the 9.5.21 Feature Release.
Important note for On-premise customers
When installing this patch release on your Kaseya server, make sure that under Install Options, you select the first option, Install latest Patch Release or addons. We are investigating an issue with outbound email when selecting the second option. Refer to Installing Patch Releases.
Product lifecycle updates
Update to Agent Minimum Requirements
Windows Server 2025 has been added to the list of supported operating systems for agent deployment.
Update to VSA server installation pre-requisites
Java is no longer required on the VSA server. The installer system checks have been updated to display a warning if its already installed. It should be uninstalled using Windows Control Panel if not required by another application.
Removal of deprecated Antivirus (KAV) and Anti-Malware (KAM) modules
KAV and KAM modules have been end-of-life since 2022 but some management capability was retained to facilitate migration of endpoints to alternative endpoint security solutions. All remaining functionality has now been removed from the product, including Info Center data sets and machine view filters.
vPro
Support for the vPro module will end on May 31st, 2025.
Live Connect
Support for the 32-bit Windows version of the Live Connect technician application will end on May 31st, 2025.
REST API
The following v1.0 endpoints will be fully or partially removed from the next VSA release. Customers and 3rd-party integrators should migrate to the equivalent v2.0 endpoints as soon as possible to ensure compatibility with v9.5.23 and later VSA releases.
| v1.0 Endpoint (deprecated) | v2.0 Endpoint | Notes |
| POST api/v1.0/authsso | POST api/v2.0/auth/authsso | The v1.0 endpoint will be removed in v9.5.23. |
| GET api/v1.0/auth (with 2FA passcode) | POST api/v2.0/auth/auth-2fa | GET api/v1.0/auth should still be used when authenticating with a personal access token (PAT). |
3rd-Party Software 2.0: March updates
New titles
- .NET Desktop Runtime 9.0 (32-bit)
- .NET Desktop Runtime 9.0 (64-bit)
- ASP.NET Core Runtime 9.0
- Microsoft .NET SDK 9.0 (32-bit)
- Microsoft .NET SDK 9.0 (64-bit)
Refer to VSA 9 Software Management application catalog.
Release features
Unified Endpoint Security with Datto EDR and VSA 9
We are pleased to announce some new features and improvements to the Datto EDR integration:
-
Policy-based EDR client deployment
- Added an Endpoint Protection policy object with option to Install EDR Agent:
- Pre-requisites: EDR integration must be enabled in Endpoint Protection module and Ransomware Detection should not be installed on target machines.
- If pre-requisites are met, EDR Client will be installed (if not already installed) when applying the policy to machines.
- Policy will be out of compliance if pre-requisites are not met, or EDR Agent is uninstalled.
-
Enhanced agent service status
- Data column enhancements on Endpoint Protection > Operations > Machines page:
- Datto Antivirus (AV) and Rollback (RB) service status is now displayed.
- Note: Alert Configuration in VSA applies only to the Datto EDR service, not AV or Rollback.
- License status is now shown for Datto EDR, AV and RB services, represented in the same data column as Agent Service Status:
- Icons represent Agent Service Status.
- Text shading represents licensed state (grayed out when license is not active).
- Hover over the service name to view details in a tooltip.
- The data source for the EDR Agent Status column has been updated to better align with the status reported in the Datto EDR management platform.
- Datto Antivirus (AV) and Rollback (RB) service status is now displayed.
- An EDR tile has been added to Live View with EDR installation status, licenses, and other relevant data.
- Data column enhancements on Endpoint Protection > Operations > Machines page:
-
Inventory Sync
- If a VSA agent with EDR is moved to another organization or group, it's organization and site assignment in EDR will update within 24 hours.
- Note: this is a one-way sync, changes made in the Datto EDR management platform are not automatically applied in VSA.
- If a VSA agent with EDR is moved to another organization or group, it's organization and site assignment in EDR will update within 24 hours.
-
Reporting and dashboards
- New Info Center data sets added for EDR. Ransomware Detection folder renamed to Endpoint Protection to reflect the unified module name.
- Enhanced dashboard showing aggregated data on agent protection status, EDR alert counts and alert history.
- A Remove Connection button has been added to the EDR Integration page, allowing easy removal of the Datto EDR integration. On removal, the following changes will be applied:
- Installed EDR agents will remain active on endpoints, but VSA will no longer report their status or generate alerts.
- No new EDR agents will be deployed by Policy Management. Any policy with Install EDR Agent selected will be reported out of compliance.
- EDR functionality in Endpoint Protection module will be deactivated.
- Info Center data sets will no longer return any data.
Bug fixes and other improvements
Agent Procedures
- Fixed an issue where, if multiple agent procedures with the same name existed in different folders, it was not possible to select the correct one when defining an executeProcedure() step from another procedure.
Authentication
- Account modified email notifications triggered when users reset their password through the Forgot Password link will now include details on the username and the action taken.
Bitdefender Integration
- Fixed an issue where user role access rights to the Bitdefender integration were reset during module redeployment or update.
Monitoring
- Fixed an issue with Event Log alerts where the re-arm period defined for an Event Set was incorrectly applied to all events with a matching Log Type.
Patch Management
- Aligned scheduling logic for monthly scheduling of Patch Scans and Automatic Updates, to ensure they would start in the same month when applied by policy.
Policy Management
- Fixed an issue where Remote Control policy could not be reapplied to machines after a manual override.
Reporting
- Fixed an issue where the total count of devices was not including Windows 11 and Windows Server 2022 devices.
Software Management
- Fixed an issue where next scan date would not be reported correctly under certain conditions.
- Fixed an issue where an error would sometimes be displayed when running an ad-hoc Scan on a large selection of machines.
User Interface
- Fixed an issue where a message stating "Error getting online admins" would intermittently be displayed in the top right notification area.