Patch Release Process & VSA Patch Installation instructions

Installing Patch Releases - On-Premise

  1. Rerun Kaseya Server Setup. On the system hosting your Kaseya Server, click Start > All Programs > Kaseya > Kinstall.
  2. Accept the License Agreement, and proceed through the System Check (fixing issues as needed). 
  3. Choose “Install add-ons only.  Do not upgrade VSA.” and click Next:
    mceclip1.png
  4. On the Addon Installation wizard page, select the Kaseya Patch Process addon.
  5. Complete the steps of the installation wizard.
  6. Un-check all add-ons that 
    1. You do not want to install -or-
    2. Are already up-to-date -or-
    3. Are not available
  7. Make sure that “Kaseya Patch Process” is checked, and click Nextmceclip2.png
  8. Confirm that “Kaseya Patch Process” is set to update and click Next:
    mceclip3.png
  9. Note: Rerunning the installation will restart Kaseya Services. Your VSA will be offline for several minutes, depending on the speed of your host environment. 
  10. When the patch installation is complete, KInstall will disappear from your screen.
  11. Log into your Kaseya Server as a Master Admin and navigate to  System > Server Management > Configure. 
  12. Verify the updated version number in the “Installed Patch Level”… this should match the version of “Kaseya Patch Process” that you just installed:
    mceclip6.png

 

Installing Patch Releases On SaaS

  1. Patches and updates to our SaaS infrastructure are deployed by the Kaseya VSA Operations team during regular maintenance windows. 
  2. Details are listed in the Cloud Operations Status Dashboard (https://status.kaseya.net/).

Latest Release Notes

You may review the release notes for specific patches on the following page: https://helpdesk.kaseya.com/hc/en-gb/sections/360001193517-Release-Notes

Make sure to follow the section, so you can be notified via email when we post a new patch release note!

Have more questions?

Contact us

Was this article helpful?
5 out of 5 found this helpful

Provide feedback for the Documentation team!

Browse this section