Kaseya Community Patch Release - 24 October 2017

  • Hello All,

    We have released patch to production:

    http://help.kaseya.com/webhelp/EN/RN/index.asp#38510.htm Patch Releases - 24 October 2017

    Virtual System Administrator™

    • The agent version is updated to (NINEFOURPT-668)
    • Corrected an issue where the Agent and Agent Endpoint services will crash when a dependent registry key is missing. (NINEFOURPT-631/EES-1347)
    • Audit will now correctly identify which country an IP address is associated with. IP records will need to be imported again to correct any stored IP information in the database via http://{VSA IP Address or Hostname}/SystemTab/dlMaint.aspx using the "Import IP Records" button. (NINEFOURPT-662/APPF-2929)
    • Executive Summary reports are now properly aligned in the center. (NINEFOURPT-659/APPF-2500)
    • Policy deployment is now no longer dependent on licenses being valid. (NINEFOURPT-630/SDP-3051)
    • Live Connect logs will now properly display under Technician Logs > Live Connect after correctly reading agent GUIDs. (SDP-2994/NINEFOURPT-629)
    • Select All under System > Check-in Policy will now properly select all machine groups. (NINEFOURPT-627/APPF-2515)
    • SQL Schema Installs will now work on native foreign OSes including German, Russian, and French. (NINEFOURPT-625/APPF-2503)
    • The device rename dialog in Discover > Discovered Devices will now display text properly. (NINEFOURPT-622/DISMON-1712)
    • Application exclusions in Policy Management will now exclude properly. (NINEFOURPT-619/SDP-2080)
    • Deleting tickets under the Delete/Archive function will now properly delete. (NINEFOURPT-615/EXT-3223)
    • Running a send alert agent procedure across multiple machines will no longer result in alerts being created for incorrect machines. (NINEFOURPT-607/DISMON-1824)
    • An owner of a view can now properly see all users that have access and consequently revoke if needed. (NINEFOURPT-606/APPF-2427)
    • Upgrading from earlier versions of Discovery will no longer prevent the deletion of discovered devices. (NINEFOURPT-144/ DISMON-1269)
    • Corrected the behavior of rejecting an acceptable value when running a PUT in /system/orgs/orgId. (NINEFOURPT-611/APPF-2642)

    Software Management

    • Improved performance of Software Management scans by restructuring queries required when overrides are used. (NINEFOURPT-667/SDP-3718)
    • Improved performance of patch analysis results by reducing amount of cycles needed to report back to messaging queue. (NINEFOURPT-666/SDP-3709)
    • Improved performance of patch analysis by utilizing caching on SQL Server. (NINEFOURPT-666/SDP-3679)
    • Corrected an instance where daily imports from the Lumension Cloud Service would remove vulnerability overrides. (SDP-3810/NINEFOURPT-689)
    • Patches that are ready to be deployed will now appropriately display “Ready” instead of “Scheduled”. (NINEFOURPT-651/SDP-3619)
    • Failed third party patch deployments will now properly display an error icon. (NINEFOURPT-664/SDP-3671)

    Cloud Backup

    • QEMU-based machines will now be properly detected as virtual machines instead of physical machines. (NINEFOURPT-582/EXT-2448)
    • Cloud Backup now supports viewing data consumption per backup group. (NINEFOURPT-586/EXT-3062)
    • Cloud Backup now supports licensing by the total amount of storage used. Customers can use this method of licensing instead of the default method of licensing by the number of agent licenses used. Contact your Kaseya account representative for pricing information.
      • The Licensing dialog now displays licensing information by storage amounts, if this method of licensing is used.
      • New storage information columns have been added to the Backup Groups page to support storage licensing.
      • A new 'Storage License Limit Reach' alert type has been added to the Cloud Backup > Settings > Licensing Alerts page. If checked, an alert is triggered when the total amount of storage used exceeds your licensed amount. Acronis does not prevent backups if the storage limit is exceeded, but you may incur additional costs for going over your licensed storage limit. (NINEFOURPT-587/EXT-3064)
    • Depending on the Cloud Backup license subscribed, the licensing dialog will now show the storage limit or licenses remaining. (NINEFOURPT-588/EXT-3065)

    Software Deployment and Update

    • Running Service Desk reports no longer require the master role. (NINEFOURPT-656/APPF-2906)
    • Service Desk ticket counts will now be properly calculated in search results in the notification bar. (NINEFOURPT-620/APPF-2851)

    Live Connect

    • Live Connect will no longer improperly invalidate its token after a certain period of time requiring logging in frequently. (NINEFOURPT-576/AF-2920)
    • Remote control sessions will now properly relinquish keyboard control whenever a key is held down while switching window focus. (NINEFOURPT-642/AF-1883)
    • Subsequent remote control sessions will no longer preventing typing in text fields. (NINEFOURPT-614/AF-2700)
    • Caps lock may now be turned on and off when remotely connected to Mac-based machines. (NINEFOURPT-603/AF-2883)

    Anti-Malware (Classic)

    • Fixed an issue which caused Anti-Malware profile assignment to fail if a full scan scheduled date time was set to a day higher than the 12th of the month on environments with international date time settings. (NINEFOURPT-626/EXT-2615)
    • Reboot flags will no longer appear erroneously if KAM does not require a reboot. (NINEFOURPT-612/EXT-3045)

    Antivirus (Classic)

    • Excluding a trusted application will now also globally exclude network traffic settings. (NINEFOURPT-617/EXT-2190)
    • Adding global exclusions to a large deployment will no longer result in “Could not parse response from server” errors. (NINEFOURPT-610/EXT-2176)


    • Agent groups in the AuthAnvil module will now reflect manual agent name changes in Agent > Manage Agents. (NINEFOURPT-624/IAMV-5236)

    [edited by: Nicolas Ponce at 6:37 PM (GMT -7) on Oct 24, 2017]
  • Tried to patch our demo VSA and running reapply schema got stuck at 46% with this error: Fatal MessageSys Error: Monitoring/Constraints/DF_alertTemplateOverride_agentGuid.sql

  • Same here.  There are problems with DF_alertTemplateOverride_agentGuid.sql and dbo.PKAlertTemplateOverride.sql.

    DF_alertTemplateOverride_agentGuid.sql wants to put a constraint on a a field that already has a constraint, and dbo.PKAlertTemplateOverride.sql is trying to put a constraint on a non null field.

  • Support has been able to reproduce this internally and I got map.xml that fixed the problem. It had those problem rows commented out.

  • Hi All,

    Thank you for your reports on this issue.

    Patch has been pulled from production and we will be releasing patch to rectify this issue.

    I will update this thread when patch has been released along with a new thread for the documentation.

    Apologies for the inconvenience this may have caused.

  • ...and for people who installed it before it was pulled?

  •  Unzip the attached map.zip and place it in C:\Kaseya\DBInstall\Monitoring


    attachment link replacment
    [edited by: neuvoja at 10:08 AM (GMT -7) on Oct 25, 2017]
  •  Alternatively, If you don't want to apply the out of band fix provided above, you can wait until patch is released to correct the issue.

  • Or don't run reapply schema if you have done the patching using option 1 as mentioned in installation instructions: help.kaseya.com/.../RN

    I always run it manually because its best practice :)

  • Thanks...I did see your post   after installing but before running reapply schema so thank you especially for posting that so quickly! -- I just wasn;t sure if perhaps other issues were found that caused the update to be pulled.

    hit Post too quickly
    [edited by: karoded at 10:23 AM (GMT -7) on Oct 25, 2017]
  • A reapply schema should not be needed. If you're seeing functionality break after running a patch which necessitates running a reapply schema, please let us know why so we can look into this.

  • I think we are having this discussion after almost every patch. Support tells me that its best practice to run reapply schema after a patch and you are telling me its not. So maybe Kaseya should discuss this internally with support & product management teams and tells us customers what is the preferred way?

  • Absolutely. I'll PM you so we can discuss in detail.

  • we installed the and had no issues with it. only weird thing is (probably because of the pull back is)

    Version Number:

    Installed Patch Level:

    Available Patch Level:

  • Updated our demo VSA to .31 and no problems so far. Waiting for the rls notes and gonna patch prod. VSA next week if nothing major is reported over the  weekend.