Kaseya Community

9.5.0.10 & 9.5.0.11 Patch Releases - 24 May 2018

  • Hey guys,


    Here is the latest information on our most recent R9.5 VSA patch:

    http://help.kaseya.com/WebHelp/EN/RN/index.asp#40437.htm

    Discovery

    • Fixed an issue where Windows and Mac agent packages created and deployed via Discovery would eventually consume all available disk space in the Kaseya Installation directory causing service outages. (NINEFIVEPT-630/SAAS-10385)

    Antivirus

    • Updated default global exclusions to match the latest parameters required by Kaspersky. Refer to notes below for compliance information. (NINEFIVEPT-581/EXT-3777)
      • An out-of-compliance notification for existing agents may appear after running this patch. A daily background job will re-apply the policies automatically clearing the notification.
      • For more immediate resolution, manually re-applying policies or KAV profiles will resolve this.
      • For new agent deployments, audits must be completed before they are checked for compliance.
    • There were reports of instability and incompatibility when the Windows 10 April 2018 Update was installed on agents running Kaspersky Endpoint Security 10 SP2 MR1. To address this issue, the KAV package is now updated to Kaspersky Endpoint Security 10 SP2 MR2. Refer to notes below for deployment information. (NINEFIVEPT-629/EXT-3847/EXT-3863)
      • Due to changes in Kaspersky’s versioning, it will require either the built-in daily job to run or manually running Protection > Get Status before an update.
      • Important: Kaspersky strongly recommends rebooting immediately after updating to the latest version. We recommend scheduling updates outside business hours. If skipping reboot is desired, ensure that reboot options are configured in Antivirus > Configuration > Profiles.



    Making sticky note. - O.R.
    [edited by: Oscar Romero at 9:30 AM (GMT -7) on May 29, 2018]
  • Looks like .11 has KAV working well for us. We did find the endpoints really do need a reboot after KAV updates, for the system to fully recognize the update.

  • KAV is working for us, but only after we ran a SQL script to download the latest version(Refer to case #246695).

    Before that there we were still having the "Downloding OEM files to VSA" problem.

  • Glad your issue was resolved.  The downloading of Kaspersky OEM installers has been updated to reflect the required executables as well.