Kaseya Community

9.5.0.15

  • Anyone braved the new update that came out yesterday yet?  Just curious to know if anyone has done so and had any "new" issues?



    -
    [edited by: Jenny Escobar at 12:12 PM (GMT -7) on Oct 15, 2018]
  • Not yet, though I see they finally have a fix in for our weird "negative message queue length" bug in the system status page. There's enough stuff in this one to warrant doing the upgrade, especially the Live Connect fixes. (We didn't do .14, wasn't anything in there we needed badly enough to risk getting a new bug.)

  • Yes it has a fix in for me that gets screen recording working again.. I need it but I need to see if we have problems before I load it up.

  • I was thinking about doing it tonight.   Looks like a nice round of bug fixes...

  • So far so good. 24 hours in, and no new issues. At least one of the keyboard state issues in RC sessions isnt fixed, but broadly speaking things seem good, if anything liveconnect seems faster and more reliable to connect, which is always good.
  • FYI - adding in the warranty dates for reports is nice, BUT other than being able to list the warranty dates you can not do a report that allows you to show ONLY the expired and/or missing warranty dates ... Or at least that we've been able to figure out yet ...

  • Hi Everyone,

    Please see the link below for more information on the Patch Release notes - for those that may need it.

    http://help.kaseya.com/WebHelp/EN/RN/#40600.htm

    Agent Update to 9.5.0.7

    • The patches below require updating the agent version to 9.5.0.7 for Windows, Mac and Linux agents

    Software Management

    • Improved the robustness of Software Management to address issue where customers may see a message on machines stating "failed to download file". (VSA-441)

    Endpoint

    • In some environments, if the admin has configured the option for Remote Control Sessions to be recorded, the recording does not get saved to the VSA. All Remote Control Sessions that are recorded are now properly stored on the VSA. (VSA-298)

    Live Connect & Remote Control

    • Added more verbose logging for remote control sessions to provide better information to admins in the event of a failure. (VSA-1569)

    Kaspersky

    • Fixed an issue where if the antivirus agent (KAV) was removed from an endpoint, it would incorrectly show the status as "installed". The status in the VSA now properly reflects that the antivirus agent was uninstalled. (VSA-1214)

    Database & Schema

    • Updates were made to the VSA database to improve overall VSA performance. (VSA-946)

    Patch Management

    • Improves performance of Patch Management to address issues where long running processes may block activity. (VSA-327)
    • On Windows 10 Machines, Microsoft will force updates, so the "automatic update" setting is no longer relevant. VSA will now display "automatic updates not supported" (i.e. auto update cannot be set on or off) for Windows 10 machines on applicable MS Win 10 builds. (VSA-255)
    • Fixed an issue with Patch Management scan failing on a fresh Windows 2016 agent that has never run Windows Update. (VSA-274)

    Live Connect & Remote Control

    • Fixed an issue in Live Connect where, under some circumstances, using File Manager to upload a file would result in an error message (File_Open_Error). (VSA-309)
    • Resolved keyboard issues (CapsLock, CapsLock+shift or ctrl) being improperly sent during Remote Control Sessions. (VSA-313)
    • Enhanced Live Connect for Mac where Mac terminal now includes 310 new Mac Terminal Commands that can be run (e.g. ifconfig, mount, etc...). (VSA-1681)
    • Fixed issue in Live Connect Search where selecting "More Results" showed a blank page. (VSA-433)

    Audit Module

    • Fixed an issue that prevented the REST API call, /assetmgmt/assets/customfields (PUT), from working if no existing custom fields exist. The API can now be called anytime to create a new custom field. This is primarily used by the TAP partners. (VSA-912)

    Audit Module, Policy Management Module

    • Agent Procedures, Audit Schedule, and Patch Procedure Schedule were incorrectly flagged out of compliance when scheduled to "Run Once" in policy management. They will no longer be improperly flagged as out of compliance when scheduling type is set to "Once". (VSA-869)

    Info Center Module

    • Fixed an issue where 'System Purchase Date' and 'System Warranty Expire Date' fields were not available while generating info center report for Machine Summary under Audit. Now these two fields are added and can be used while generating reports for Machine Summary. (VSA-537)

    Agent Module

    Manage Packages:

    • Fixed an issue where the create/edit dialog screens weren’t honoring the user role access right restrictions for the ‘Set As Default Package’ and ‘Show On Download Page’ flags. (VSA-394)

    Classic Monitoring Module

    • Fixed an issue in Classic Monitoring where LUA scheduling issues would great large numbers of log entries and pending script messages. (VSA-379)

    Quickview

    • Fixed an issue in which Wake On LAN scripts were not being properly executed when scheduled through Quick View. (VSA-561)

    Service Desk Module

    • Fixed an issue which causes Service Desk ticket to stays locked after closing edit ticket window using Esc key. (VSA-354)
    • In Service Desk, fixed an issue where the email reader could hang when incoming emails have very large content (large images, etc...). (VSA-426)
    • Fixed an issue which causes two attachment links to be created for each attachment while creating a Service Desk ticket via email. (VSA-425)

    KServer

    • Fixed an issue on the VSA on-prem statistics page "Checkin message queue length" and "Command message queue length" could show incorrect negative values under some circumstances. (VSA-421)

    Discovery Module

    • Fixed an issue in the Discovery Module which prevented editing scheduled scan for networks which had commas in their name. (VSA-395)

    Security Vulnerability, VSA Core

    • Enhanced security of VSA user sessions. (VSA-1385)
    • Added functionality to automatically add the secure flag to session cookies if the VSA is set to require SSL/TLS. (VSA-1016)

    Database & Schema, Installers, KServer, VSA Core

    • Added check to the VSA installer to ensure database connection drivers are using latest versions that support TLS v1.2 encryption (VSA-1165)

    BMS Integration

    • Enhanced VSA-BMS ticket de-duplications - instead of creating additional ticket notes in BMS for each de-duped ticket (which could create many ticket notes), BMS will now show a single note with the text "Duplicate Alarm Detected" and an entry in the note for each timestamp when it occurred. (VSA-923)

    Cloud Backup Module

    • This change won't affect VSA directly and there will be no visual component to trigger automatic updates on VSA. We added a new acronis api call to KCB library that is shared with TUS (Telemetry and Usage Service) an stand alone internal tool that use for storage usage and account provisioning. A scheduled job was added in TUS to automatically flag machines out of date on acronis side and schedule an update (this is all executed by Acronis). TUS has a daily job that goes over every group and reads the number of machines and storage used, we added a call to update the ones the are out of date in case there is any. We followed Acronis recommendation, flagging only 10 machines per api call, so each call will have 10 machines at the most. This job will help to keep acronis agents up to date. (VSA-357)

    Scope Denormalization

    • Scope de-normalization procedures were not running when creating new agents causing Live Connect to experience a 404 error that would last for up to 24 hours, and Live Connect on Demand was not working for non-master and system users. (VSA-666)
  • @Craig Hart;  which one?

  • Is this Kaseya’s way of saying Patch Management doesn’t officially support patching Win 10 devices anymore? Or this applicable to the latest build 1803 only?

    On Windows 10 Machines, Microsoft will force updates, so the "automatic update" setting is no longer relevant. VSA will now display "automatic updates not supported" (i.e. auto-update cannot be set on or off) for Windows 10 machines on applicable MS Win 10 builds. (VSA-255)

    We know it doesn’t work consistently for all Win10 devices but we were hoping they would fix it instead of stop supporting it.

  • I don't know if anyone else had this issue but the machine filters would work a couple of times and then would stop updating the page since about version 9.4. This update seems to have resolved this. I do not need to refresh the whole page.  

    I thought it worth commenting on.

  • Is this Kaseya’s way of saying Patch Management doesn’t officially support patching Win 10 devices anymore? Or this applicable to the latest build 1803 only?

    • On Windows 10 Machines, Microsoft will force updates, so the "automatic update" setting is no longer relevant. VSA will now display "automatic updates not supported" (i.e. auto update cannot be set on or off) for Windows 10 machines on applicable MS Win 10 builds. (VSA-255)

    We know it doesn’t work consistently for all Win10 devices but we were hoping they would fix it instead of stop supporting it.

  • Welp.

    Applied 9.5.0.15 (and, um, .14 as well) and now one of my frequent-running PowerShell-based procedures is broken. I don't know if .14 or .15 did the deed but I'm borked until Support can figure out what went awry. (Given that .14 is the one which specifically mentions "the wrong command" for PowerShell in procedures, that's my guess. But.)

  • We've applied it now as well.  No major *new* issues, but I do have to agree with Craig's findings that it definitely hasn't fixed *all* of the keyboard bugs with liveconnect.   I've had several instances still where while I've got remote control sessions up using live connect my shift key stops working completely *locally*.  Until I close out all live connection sessions.

    It definitely fixed the recording issues we were seeing, and did fix *some* of the keyboard bugs I'd seen.

  • We have been on it Since Friday. No issues here.

  • Patched last night - same findings as  and