This Quick Fix Engineering (QFE) release fixes issues 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 18.104.22.168. Be sure to update your Windows, Mac, and Linux agents after installing this release.
This QFE is for SaaS only. Where relevant, the fixes will be made available to On-Premise customers in the next maintenance release (9.5.7e).
- Full SaaS deployment - Thursday August 19th, 3 am EST
Note: SaaS customers will be informed of their maintenance window via https://status.kaseya.net.
User Portal: Home Page and Ticketing
This QFE contains fixes required to support the re-introduced User Portal functionality on the SaaS platform. End users on machines with the VSA agent can access the portal in the same way they could prior to 9.5.7a, using the Agent Contact Administrator menu (double-click on system tray icon).
In this release, the User Portal provides the following functionality: -
- Home page displaying Machine ID and basic system information (the ability to create Custom Links will be restored in a later release)
- Ticket interface with the following ticket platforms: -
- VSA Service Desk (including automation tasks providing integration with 3rd party PSA’s via MSP Assist plugin)
- NextGen Ticketing / BMS - This integration does not use or depend on VSA Service Desk. It works by VSA interacting directly with BMS.
- The updated Ticketing interface provides the following functionality: -
- Create ticket
- Edit / Change ticket:
- Add Note
- Add Attachment
- Close ticket
- View Active or Closed tickets.
- The following issues will be addressed in future releases: -
- On a masOS agent using Safari as default browser, the Description field for creating a new ticket is not accessible and information cannot be entered.
- If Ticketing platform is NextGen Ticketing / BMS, the end user cannot download file attachments from the ticket through the portal interface.
- If browser session is left inactive for a while, errors may be displayed when trying to interact with the Ticket interface again. Closing the browser tab and reinitiating the session via Agent menu will resolve this.
- Fixed an issue where the Ticket Change Procedure was not executed if the Ticket status was changed via the REST API or using the User Portal Ticket interface.
- Fixed an issue where ticket changes made through User Portal were not evaluated correctly when executing Ticket Change Procedures, for example when using IF testIncidentProperty() statement.
- Fixed an issue where the User Portal was not loaded on a SaaS agent machine because it was not directing to the correct web server address.