* Last updated March 29th *

The VSA 9.5.9 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.   

Release Schedule    

• Scaled SaaS deployment – Monday, February 7th, 11pm ET - complete
• Full SaaS Deployment - Saturday, February 12th, 7am-3pm ET - complete
• General Availability (on-prem customers) - Wednesday, February 16th - available now

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. 

Important Security Updates 

New Features

Software Management 2.0 

This is the GA release for our new Operating System and 3rd-Party Software patching. It includes new features, enhancements, and bug fixes which are listed in the following sections. 

General

• The Display 3rd Party Vulnerabilities option was removed. With this change, the behaviour of the module corresponds to the "Hybrid" value of that option, which means 3rd-Party Software Patches will only be included in scans and deployments on agents with Third-Party Support Enabled. Users can enable third-party support on agents in Software Management > Machines Page.  
• On the Application Logging page, the format of event names and messages was redesigned to make it consistent. 
• Patch History page now has a global filter bar with the ability to filter results by Organization, Machine Group, or View. 
• In this release, we added software version number representation to the "Identifier" column on the Machines, Patch Approval, Patch History pages. 
• "Next Scan Date" and the "Next Deploy Date" fields on the Machines page now display both date and time. Previously, it was showing only time information.  
• Database performance optimization. 

macOS

• This release brings support of OS patching for macOS Big Sur and Monterey. Currently, it is limited to Intel-based machines. On macOS Big Sur and Monterey, the end machine will be automatically rebooted once the installation is finished. Beta releases are not supported. 
• We recommend using the "OS Native" patches engine to do macOS patching as it supports both processor architectures and all macOS versions. 
• 3rd-Party Software now supports installation on macOS Big Sur and Monterey. Installed applications run with standard user privileges. 
• "OS Native" patches engine option for macOS now correlates with actual options on macOS end machines. 

Scan and Analysis Profile

• "Only OS Updates" and "Configure Operating System Updates" Patch Strategies have been deprecated. 
• Patch Strategies were renamed: "Kaseya Update" to "Kaseya 1.0", "Kaseya Update 2.0" to "Kaseya 2.0", "Third Party Software Updates + OS Updates" to "OS Native".

• "Patch Strategy" field name was renamed to "OS Patches Engine" as it handles only OS patches mechanism. 

Override Profiles 

• Override profiles now support new search criteria "Days from Release", to be able to create an override based on the number of days since release.  
• Override profiles now support 3rd-Party Software Patches in their rules. The list of supported fields to be searched for: CVE Code, Description, Name, Product, Release Date, Vendor are supported. 

3rd-Party Software Profiles 

• In this release, we renamed menu items to make it easier to distinguish old and new software profiles: "K3PP Software Catalog" to "3rd-Party Software 2.0", "3rd-Party Software" to "3rd-Party Software 1.0". 
• 3rd-Party Software patches that for some reason are not available for download will be marked as "Not available". This may take place for Software Titles that are being frequently updated, like Google Chrome. Usually, in such cases, VSA will have a new patch (new software version) shortly available for download and installation. 
• On the "Add Software" dialog for a given 3rd-Party Software 2.0 profile a column "Auto update" was added to easily turn on the auto-update functionality.

• A new text mark "auto-update" was added for each software application in the 3rd-Party Software 2.0 profile to represent auto-update functionality turned on.    

• Software Catalog now includes custom update channels for Microsoft Office suite. Current, monthly, and semi-annual channels are supported.

Discovery 

• Delivering on our vision for URMM, we’ve expanded the breadth of devices by launching Discovery for Azure devices!
  By providing your Azure credential to VSA (details below), it can automatically discover your Virtual Machines, SQL instances, Cloud Services, App Services and Load Balancers. 

• • Added ability for VSA to install agents on Azure Virtual Machines. Additional details regarding requirements can be found here.
  • Added organizational filters to Discovered Devices and Topology Map.  

• Introduction of Discovery Services Module, Discovery > Discovery Services.
  A new service credential management area that will allow you to administer all your discovery service credentials and their device relationships in one place. 

• • Added Azure Credentials, Discovery > Discovery Services > Credentials.
    First entry within Discovery Services. Once populated, your Azure device information will automatically be collected. Additional details regarding configuration can be found here. 
  • Added Azure Discovery Refresh Interval, Discovery > Administration > Settings.
    Interval is used to control the frequency of data collection for Azure devices (default 10 minutes). 

Info Center 

• In this release, we added the new Data Warehouse API for 3^rd-Party business Intelligence platforms (Microsoft PowerBI, Tableau) to integrate with the VSA and get data from Info Center's datasets.  Data Warehouse API uses OData format that has native support in PowerBI and Tableau to superpower the creation of immersive dashboards and reports in external tools. Datasets structured by categories: Agent, Agent Procedure, Audit, Discovery, Lan Cache, Monitor, Patch, Remote Control, Service Desk, Software Deployment, Software Management, System, AntiMalware, AntiVirus, Cloud Backup, Ticketing.
  
  Video tutorial of using Data Warehouse API in PowerBi
  
  Further reading:
  
  Data Warehouse API Documentation
  Personal Access Tokens Documentation  
  PowerBI Tutorial

Enhancements 

Agent OS Support 

In this release, we added agent support for the following operating systems: - 

• Windows 11 
• Windows Server 2022 
• macOS 12 (Monterey)

This includes all VSA functionality, with the following limitations: - 

• Antivirus and Antimalware (KAV/KAM) - we will announce plans to address this in the next few weeks. 
• Backup (KBU) - this is a legacy module that will not support operating systems later than Windows 10 and Windows Server 2016. 
• Discovery (by Network) - Windows 11 and Windows Server 2019 machines without agents installed can be discovered but the OS version may not be correctly identified. This will be addressed in a future VSA release. 
• Software Management - OS Patching is not supported on ARM-based Mac machines (M1 processor). 
• Patch Management - this is a legacy module that will not support operating systems later than Windows 10 and Windows Server 2019. Customers should migrate to Software Management for Windows OS patching.

Audit 

• The increased character limit for string format Custom Fields from 255 to 2048 characters. 

Cloud Backup 

• Updated the Acronis version for new client installations to 15.0.28323. Existing clients must be updated from the Acronis cloud console.

REST API 

• In this release, we have re-introduced the Swagger UI, allowing customers and 3rd party developers to visualize and interact with VSA API resources.
• GET /assetmgmt/assets API now returns the system serial number (SysSerialNum) field.
• The “/api/v1.0/automation/agentalerts/{alertId}” REST API endpoint for sending new alert events to the VSA has been updated to return a temporary identifier in the “AlertTrackingId” field that can be used to retrieve an Alarm ID generated from the alert request in a follow-up API call to the new “/api/v1.0/automation/getalertTracking/{AlertTrackingId}" endpoint.

User Portal 

• Added a new configuration page, System > Customize > User Portal to allow customization of Portal Header and Custom Links. For further details, please refer to the help topic.

UI / UX Enhancements 

• Added Kaseya App Launcher feature for Users who are authenticated using the "Login with IT Complete" option. The Kaseya App Launcher will provide access to the IT Complete portfolio of products by clicking the App Launcher icon in the VSA Header.
• Made improvements to the VSA Login process.
• Updated VSA Header including new Icons and Help Menu.
• Updated VSA Left Navigation menu with new Icons.

Bug Fixes 

Agent Module 

• Fixed an issue in Agent and Copy Settings where on copying agent settings Oops page and 500 error was getting displayed.
• Fixed an issue in Agent>Agents>Log History where the user was not able to set or update log time values for machines.
• Fixed an issue in Agent>Agents>Log History where on clicking “Select All Archive”/” Unselect All Archive "not all the checkboxes were getting selected or unselected.
• Fixed an issue where the agent was not able to check in to VSA, kaseyaD.ini file and it displayed it was trying to check into an invalid address.
• Fixed an issue where the country field failed to populate on the Manage Agents page and Quickview.

Authentication 

• Fixed an issue where the "Remember Me" check box for VSA login did not persist correctly for new browser sessions.
• Fixed an issue wherein Forgot Password current or any 5 previous user’s password was allowed on the Reset Password page.
• Fixed an issue where for a new login in Safari, Remember Me checkbox was selected automatically after the user logged out.

Backup 

• Fixed an issue in Backup>Backup Status> Offsite Server Status where status pop up was not getting displayed.

Discovery 

• Fixed an issue in Domain Watch Computer Policies where Machine Group Override was not respected in certain circumstances.
• Fixed an issue where some device information, such as IP and MAC address, was not sync'd to BMS for agentless network devices.

Monitoring 

• Fixed an issue in Monitor> Agent Monitoring>Assign Monitoring> Edit Individual Monitor Set where the cancel button was not closing the pop-up and displayed the Oops page after the second click. 

Remote Control 

• Fixed an error that occurred while attempting to start a Live Connect or Remote Control session from certain VSA modules.

Rest API 

• Fixed an API issue where GET /assetmgmt/agents was returning "DNS Computer Name" instead of "Computer Name" in the ComputerName field.
• Fixed an issue where PUT /assetmgmt/documents/{agentId}/file/{path} would fail when specifying a sub-directory.

Service Desk 

• Fixed an issue where importing a Desk Definition to a SaaS tenant would fail.

Software Management

• Fixed an issue where the new deployment process may start while the previous deployment is still in progress.
• Fixed a Windows patch detection issue when using a Scan & Analysis profile with Kaseya Update 2.0 as Patch Strategy.
• Fixed an issue where KAV installation failed in some environments due to an HTTP download error.
• Fixed an issue where the latest version for a software catalog item was not always updated.
• Fixed an issue where the PMClient timed out when attempting to download and install the patch.
• Fixed an issue where the PMClient timed out when attempting to download and install the patch.
• Fixed an issue in Software Management 2.0 when scanning and deploying triggers update or download the Lumension OSPX files.
• Fixed an issue in Software Management 2.0 where the vulnerable machine pop up shows “No records found” on the patch approval page.
• Fixed an issue in Software Management 2.0 where an error message was getting displayed “Exit Code: 9999 Deployment Failure” when third party titles were deployed.
• Fixed an issue in Software Management 2.0 where the History pane was not showing the correct “status date” time.
• Fixed an issue where Reboot was requested twice during software installation and an error occurred.
• Fixed an issue where InstallError was shown in Application History if a reboot was required during the installation process.
• Fixed an issue where some K3PP applications failed to install due to a hash mismatch.
• Fixed an issue where while an agent was offline, the Next Scan Date and the Next Deploy Date was not re-calculated. The next dates were updated after the next scheduled run of Scan or Deployment was triggered.
• Fixed the issue where the «scan» icon appears with a delay (up to 5 minutes) at «Pending actions» when a user starts a scan.
• Fixed the issue CVE Views do not return expected results.
• Fixed the issue where the view «Machines with Reboot Pending for patch installations» is not working properly.
• Fixed the issue where the Force Update function was not working.
• Fixed the issue where the VSA agent doesn't respect Pre and Post update procedures.
• Fixed the issue where the deployment of 3rd-Party Software does not result in the status window being updated with activity or progress.
• Fixed the issue with incorrect sorting of Scan & Analysis, 3rd-Party Software, and Deployment profiles.
• Fixed the issue where the «Patch History» page pagination not working correctly.
• Fixed the issue where the view «Show Member of Scan profile» is not working properly.

System Module 

• Fixed an issue where, in certain circumstances, an Agent Procedure that has been imported to a SaaS tenant may execute a sub-procedure on the wrong tenant. This was known to impact certain 3rd party (TAP) integrations such as Bitdefender.
• Fixed an issue on the System > User Settings > Change Logon page where clicking the “Done“ link after changing an Active Directory password does not re-initiate the VSA login process and allow the user to log back in with the new password. 
• Fixed an issue on System > Customize > Site Customization page where changes to Deploy Header and Site Header was not getting saved and applied. 

User Portal 

• Fixed an issue in User Portal where a prohibited file type could be attached to a ticket, but the ticket could not be opened from the portal interface and the file could not be accessed from Service Desk. The User Portal interface will now display an error if the user tries to attach a file type that is not whitelisted.