Kaseya Community

9.3.0.20 Patch Release - 18 October 2016

  • Hi All,

    We released Patch 9.3.0.20 last night:

    http://help.kaseya.com/webhelp/EN/RN/index.asp#37574.htm

    9.3.0.20 Patch Release - 18 October 2016

    Critical Issues For Customers To Patch Immediately

    Virtual System Administrator™

    • Added Delete Agents, Rename, Change Group, and Set Credentials to the Manage Agents branch of the System > User Roles > Access Rights tree. (PT-216/SDP-1349)
    • Setting a machine ID filter no longer excludes all template accounts categorically inside the Agent Package wizard. Like agent accounts they will display if they match the conditions of the machine ID filter. (PT-178/SDP-1275)
    • Fixed an issue causing the agent to hang on startup in certain environments. (PT-169/VAKF-1008)
    • Fixed an issue with reports not honoring the 'end after x days' scheduling option. (PT-196/APPF-1806)
    • Fixed an issue that could cause Live Connect and Kaseya Remote Control to repeatedly disconnect after the VSA server was migrated. (PT-223/END-1762)
    • User portal now honors the machine role permissions for agent procedures for the default machine role. (PT-167/ATTHREE-467)

    Antivirus

    • With this patch, a machine migrated from Antivirus (Classic) to Antivirus continues to use the same 'uninstall password'. (PT-194/ATTWO-1992)
    • Added support for installing Antivirus on Microsoft Windows Small Business Server 2011. (PT-185/ATTWO-1874)
    • Added a new 'client license deactivated' alert type to the Antivirus module. (PT-210/ATTWO-1784)
    • Fixed an issue that caused the Antivirus client to fail if one of its components became corrupted when invalid scan exclusions were configured. (PT-188/ATTWO-1960)
    • Fixed an issue that caused disabled components to become enabled when a profile was edited and saved. (PT-212/ATTWO-1945)
    • Fixed an Antivirus pending actions error: 'Error On Endpoint: Failed to query param object : Script error util.getEndpointInfo@getValue'. The error was caused by the Kaspersky API not returning the date of last definition update because of a missing registry key. (PT-226/ESR-518)

    Anti-Malware

    • Fixed a Pending Actions error that prevented an Anti-Malware profile from being applied to a machine. The error states "Could not convert string to DateTime: NaN-NaN-NaNTNaN:NaN:NaNZ. Path 'LastFlashScan', line 20, position 48" (PT-184/ATTWO-1917)

    Antivirus and Anti-Malware

    • The following columns were set as default columns in Antivirus and Anti-Malware:
      • for the INSTALLATION column set.
        • Agent Status
        • Machine Id
        • Install Status
        • Installed On
        • Pending Actions
        • Flags
        • Database Date
      • for the STATUS column set
        • Flags

      In addition a new 'Kaspersky Antivirus Version' column was added to the Antivirus grid and a new 'Malwarebytes Anti-Malware Version' column was added to the Anti-Malware grid. (PT-190/ATTWO-1951)

    • If install file downloads are detected as corrupted, Antivirus and Anti-Malware now attempt to re-download good copies of the install files from the VSA and continue with the install. (PT-189/ATTWO-1955)
    • Previously, the only status values reported back during an Antivirus or Anti-Malware install were:
      • Downloading Files
      • Installing

      This fix adds three additional status values:

      • Downloading OEM files to the VSA
      • Downloading Files to the endpoint
      • Installing product on the endpoint (PT-211/ATTWO-1952)
    • For SaaS, all Kaseya-related folders and Kaseya agent-related applications have been added to the Global Exclusions of the Antivirus and Anti-Malware module. On premise environments were already updated in a previous patch release. (PT-222/ATTWO-2022)

    Antivirus (Classic)

    • Fixed an issue with the Executive Summary Network Health Score showing Anti-Virus (Classic) twice. (PT-233/PROTECT-930)

    Antivirus (Classic) and Anti-Malware (Classic)

    • This fix prevents the user from installing Antivirus (Classic) on a machine if the machine has been migrated to the new Antivirus module. It also prevents the user from installing Anti-Malware (Classic) on a machine if the machine has been migrated to the new Anti-Malware module. (PT-225/PROTECT-907)

    Endpoint Security

    • Fixed an issue that caused Endpoint Security profiles to fail to be applied if the profile's Resident Shield tab specified file extensions that were longer than 4 characters or had an asterisk (*) prefix. (PT-195/ATTWO-1872)

    Software Deployment and Update

    • Added seed data to populate certain Software Deployment and Recovery values if the VSA is installed without internet access. (PT-197/SDP-1631)

    Non-Critical Issues For Customers To Patch When Convenient

    Antivirus (Classic)

    • Added a daily job to remove operation queues 2 days older than when they last ran. (PT-156/ATTWO-1919)

  • Been waiting on the AV fixes! Thanks!

  • Does this update include an update to the agents?

    In the future can you include that in the release notes?

    This affects whether we update during a week night or wait until the weekend.

  • Hi  

    Yes, this includes an update to the Agent version (now 9.3.0.11 agent version for 9.3.0.20 patch).

    I will forward your request to our Documentation team who creates the Release Notes.

  • I already have antivirus installed on small business server 2011, it seemed to work just fine.

    Can someone elaborate what the issue was previously, what I need to do now, if anything, to ensure proper operation?

  •  

    The fix ATTWO-1874, corrected an issue preventing the installation on Small Business Server 2011 Operating Systems.

    If it was already deployed, you most likely wouldn't have encountered this issue.

  • Thank you. I'm fairly certain the SBS box in question started out with anti-virus Classic and was upgraded to Anti-Virus(9.3) at some point. It all went OK for us at the time anyhow, so no problemo :)