The VSA 9.5.12 release (build 188.8.131.5286) 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.
This release requires agent version 184.108.40.206. Be sure to update your Windows, Mac, and Linux agents after installing this release. Agents updated to this version cannot be used to communicate with servers running VSA versions prior to 9.5.8.
Scaled SaaS deployment – Saturday, June 11th
Full SaaS Deployment - Saturday, June 25th
General Availability (on-prem customers) - Thursday, July 7th, 4pm ET
Important Security Updates
This release contains important security updates. We recommend on-premises customers update to this release as soon as possible (No action is required for SaaS customers as updates are automatically applied).
Fixed an issue where an encrypted password for a 3rd party service was exposed in the browser response for authenticated users.
*SNEAK PEEK* LiveView
We are very happy to share a sneak peek of LiveView as we know many of you are excited to get your hands on it. Using LiveView will significantly decrease the time spent administering single devices and make troubleshooting a breeze! When completed, LiveView will be a device-centric “one-stop-shop” focused on surfacing the most important information and workflows on behalf of every major VSA module:
In this sneak peek, we have the introduction of our first LiveView category: Live Tools. Live Tools has been curated to give you the visibility you need with support for powerful management functions. Allowing you to understand the health of a device at-a-glance within Overview, interact using the windows command prompt within Commands, control Services and Processes or check out Events.
Using LiveView is easy, just float your mouse cursor over the same places you would see QuickView today, but while holding ALT.
NOTE: LiveView Sneak Peek is only available for windows-based Devices that have been promoted to Assets.
While we know this is exciting, this is only the introduction of LiveView, you should expect to see LiveView continue to grow over the next year as we plan to add powerful features every release.
User Portal- Agent Procedures
We are pleased to announce that this release re-introduces Agent Procedures to the User Portal, enabling self-service execution of selected automation tasks by end-users.
- To select which procedures to expose in User Portal, use System > Customize > User Portal > Agent Procedures tab.
- To enable end-users to access the Agent Procedures function in User Portal, add the “User Portal Agent Procedures” permission to their Machine Role.
End-users can now access the selected procedures from User Portal by double-clicking on the agent system tray icon and visiting the Agent Procedures function.
In this release, the VSA agent has been updated to natively support macOS devices with Apple Silicon (ARM) based processors. The new installer can be used on Intel or ARM-based devices with supported macOS versions.
In this release, we have added a new User Role permission to provide administrators with more control over bulk scheduling of procedures to help mitigate the risk of accidental bulk execution. It can be found under Agent Procedures > Manage Procedures > Schedule/Create > Procedure Properties > Schedule and is called “Bulk Schedule/Run across Machine Groups”.
- If selected, users belonging to the role can bulk schedule or run agent procedures across all machines in their scope.
- If not selected, they can only bulk schedule or run procedures on agents belonging to a single machine group at one time.
- If a user with this role tries to schedule or run a procedure on machines from multiple groups at one time, a message will be displayed “Your User Role does not have permission to bulk schedule agent procedures across multiple machine groups. Please limit your selection to agents belonging to the same group.”
- The permission applies only to manual scheduling or execution of agent procedures. It does not apply when agent procedures are scheduled via Policy Management.
- The permission applies only to custom procedures created by a VSA user. It does not apply to system-created procedures used for standard VSA functionality (Audit, Patch Scans, etc.)
- This new permission is enabled by default after the patch installs for ALL Users Roles that already had the “Schedule Agent Procedure” permission. Master or System role users wanting to apply the new restriction must explicitly remove the permission.
To further mitigate the risk of accidental scheduling or execution of procedures, we have added a new confirmation dialogue. When a user schedules or runs a procedure from the Agent Procedures > Manage Procedures > Schedule / Create page, a confirmation dialogue is displayed saying “Are you sure you want to schedule <procedure name> on <n> agents? - Yes/No”.
- If Yes is clicked the schedule is submitted. If No is clicked the operation is aborted.
- Updated the hyperlinks for Dell and Lenovo serial numbers on the Audit > View Individual Data > Machine Summary page to route directly to the support page on the manufacturer’s website for the model in question, without needing to enter the serial # manually.
Remote Control Module
- The VSA has been updated to support initiating remote control operations using HTTP, HTTPS and SSH or protocols over custom TCP ports for all Assets within the VSA, which includes both Agents and Network Devices that have been promoted to Assets. A full introduction to this new feature can be found here in our Knowledge Base, and a video review can be found here.
- When the end machine fails to download a 3rd-Party Software patch the status «Not available» is set only for the patch on the machine encountering such error.
- Increased SmClient script execution timeout from 30 minutes to 60 minutes through ScriptsExecutionTimeout parameter to SmClient command line.
In this release, we introduce a custom installers. This makes possible to distribute enterprise (in-house) applications across managed machines.
To add and manage the list of custom installers just click on the «Custom Installer Catalog» on the «3rd-Party Software 2.0» page.
Currently we support only MSI format of installers.
To improve our security posture, we have changed the default User Role permissions for newly installed 3rd party (TAP) modules.
- Only Master and System roles have permission to access the module by default. All other Roles must have permissions explicitly assigned by a Master or System role user from System > User Security > User Roles
- When upgrading or reinstalling an existing TAP module to a new version, reinstalling VSA, or installing a VSA patch, all User Roles maintain the same permissions they had previously.
- Fixed an issue where MacOS or Linux agent upgrades would fail with a “database access error” under certain conditions.
- Fixed an issue where applying a backup profile that was configured to backup to network share would fail with an error stating that credentials for the share are not specified, even though valid credentials were entered in the profile.
Data Warehouse API
- Fixed an issue where certain SaaS servers displayed server error for PowerBi Data Warehouse.
- Fixed an issue where OData installation failed on a server with PowerShell v5.
- Fixed an issue where the tool which creates self-signed certificates was sometimes crashing on certain versions of Windows.
- Fixed an issue in Monitor > Dashboard > Group Alarm Status Dashlet where a popup with an alarm wasn't displayed after clicking on the red circle.
- Fixed an issue where a user in the Service Desk admin UI was unable to download or see the hyperlink of a file that was attached to a ticket note.
- Fixed an issue where files attached to emails processed by Email Reader were not added to the ticket in some circumstances.
- Fixed an issue where the machine selector showed all machines instead of applicable machines on the vulnerability page.
- Fixed an issue where errors appeared when attempting to approve suppressed patches when filtering by patch name.
- Fixed an issue where the identifier column was missing on the patch approval page.
- Fixed an issue where the vulnerabilities page failed to load.
- Fixed an issue in the patch approval page where the number of affected machines per patch was not being filtered. Additional improvements to filtering and pagination were made on the grid.
- Fixed an issue where 3rd Party Software 2.0 Profiles were not visible on SaaS servers.
Fixed an issue where agent status filtering was not working in the Vulnerabilities and Patch Approval pages.
- Fixed an issue where the System > Server Management > Logon Policy page displayed users that are outside of the logged-in user’s scope.
Fixed an issue where access rights were duplicated in User Roles for 3rd party (TAP) modules after upgrading the module to a new version.
- Fixed an issue in the Ticket entry form where a non-defined category was displayed in the drop-down selection list for category fields.
- Fixed an issue where an incorrect title was displayed for Suspend Alarm notifications in the System Notifications area.