Upgrading from VSA 9 to VSA 10

Before starting the upgrade process, ensure you have completed the necessary preparations. As follows are a few key steps:

• Review the release notes. Take the time to carefully read the current and previous release notes for VSA 10. Release notes will provide you with important information about new features, known issues, and any specific requirements for the upgrade process. Refer to VSA 10 release notes.
• Check system requirements (on-premises only). Ensure your current system meets the minimum requirements for VSA 10. These include hardware, software, and operating system specifications. If necessary, plan to upgrade any components that fall short of the requirements.
  For on-premises installation instructions, refer to VSA 10 on-premises guide.

NOTE  Kaseya executes provisioning for SaaS/cloud-based customers.

• Prepare your team. Inform all VSA users of the upcoming upgrade. We recommend they review the fundamentals course available in Kaseya University as part of your subscription. You can provide access to the course via the admin console in KaseyaOne. Refer to Assign courses to a user in the KaseyaOne Online Help.

Log in via the link in your email inbox

An activation email from the VSA 10 team will contain a link that allows you to log in to your VSA 10 tenant. Once your account is initially created, you will be presented with the VSA 9 Upgrade Wizard.

Run the VSA 9 Upgrade Wizard

Watch a demo of the VSA 9 Upgrade Wizard.

NOTE  Certain configurations, including Software Management, Monitoring, Policies, Info Center, and Discovery, will currently require recreation in VSA 10 using our provided sample configuration.

What is brought over when upgrading from VSA9 to VSA10? 

• Organizations and Machine Groups
  • VSA 9 organizations will become organizations in VSA 10.
  • VSA 9 sub-organizations will become sites in VSA 10.

    NOTE  If no sub-organization exists in VSA 9, then the upgrade wizard will create a default site for the migrated organization in VSA 10.

  • VSA 9 machine groups will become agent groups in VSA 10.
• Machines
  • For Windows agents, existing VSA 9 agents will automatically deploy the VSA 10 agent.
  • For macOS and Linux agents, existing VSA 9 Agents will automatically prepare each device with specific information about the upgrade. Next, the VSA 10 agent will need to be installed manually. When the agent is deployed, based on the local system information from the VSA 9 Agent, the VSA 10 agent will register itself with the proper VSA 10 agent record
• Users
  • User passwords will not be upgraded. Instead, a secure invite will be sent to the email address found in VSA 9 for each user account.
  • If there is no email address for a given user account, you must provide one during the upgrade process for the user to be upgraded.
  • When migrating users, you must select a Team for each user.

  NOTE  While users will migrate, security levels will not. Security levels will need to be recreated as closely as possible in VSA 10 as Teams before running the upgrade wizard so they can be selected during the upgrade process. By default, there is an Administrators team in VSA 10. For more information on configuring teams in VSA 10, refer to User functions and permissions.

• Custom Fields

  • VSA 9 Managed Variables will upgrade to Custom Fields in VSA 10, and aligned with the relevant Organization, Site, or Group.

• Agent Notes
• Network records and discovered devices.
• Agent Procedures
  • Agent Procedure Steps and Conditions will automatically get translated to their Workflow counterparts.
  • Any Agent Procedure not executed withing 30 days will by default be excluded. This option can be changed.
  • All Workflows translated will be set to Inactive, giving you the opportunity to activate and schedule.
  • All Agent Procedures can be selected during the upgrade, but any step or condition not yet supported will be displayed in red once created. A 0-100% score will indicate the compatibility during the Upgrade Wizard process.
  • Workflows with any not yet supported actions or conditions can not be activated until manually edited.
  • Agent Procedures already translated into Workflows will not be included when re-visiting the Upgrade Wizard.

  NOTE  Agent Procedure imports are “as is” and are not guaranteed to work for all agent procedures being imported (for example: agent procedures with managed variables or managed files will need to be edited after importing to work). We will not modify or edit procedures after importing.

What impact is there to end users? 

This is a side-by-side upgrade, meaning the VSA 10 agent will be installed alongside the VSA9 agent. End users should not experience any disruption due to the migration.

Congratulations on successfully upgrading to VSA 10! As follows are a few additional considerations to keep in mind:

• Set a date to decommission VSA 9. Once you have completed the initial Upgrade Wizard process and have taken a few weeks to get VSA 10 ready for production, please notify our team of a date to decommission your VSA 9 instance.
• Uninstall the VSA 9 Agent. We recommend you perform this step in VSA 9, but the uninstallation functionality is also available in VSA 10.