Upgrading from 4.6.10 or earlier


Upgrading K2 from 4.6.10 or Earlier to Latest: Your Roadmap

Starting from K2 4.6.10 or earlier requires a two-step upgrade process:

Step 1: Upgrade to K2 4.7

  1. Upgrade path:

    • You cannot directly migrate K2 4.6.10 or earlier to Windows Server 2016 or later due to .NET Framework 4.5 limitations.
    • You must upgrade in-place on your current Windows 2008 R2 or Windows 2012 R2 server.
  2. Backup options:

    • Take a VM snapshot and database backup of your current server.
    • Alternatively, stand up a dedicated Windows 2008 R2/2012 R2 server for the upgrade.
  3. Upgrade sequence:

    • K2 4.6.10 or earlier (Windows 2008 R2/2012 R2, .NET 4.5)
      • Backup (VM snapshot & database)
      • In-place upgrade to K2 4.7

Step 2: Upgrade to the Latest K2 Version (e.g., K2 5.6)

  1. Migration options:
    • From Windows 2008 R2/2012 R2 with K2 4.7:
      • Migrate K2 4.7 to your new Windows Server 2016+ and SQL Server environment.
    • From dedicated upgrade server (optional):
      • Migrate K2 4.7 from the temporary server to your new environment.

Remember:

  • Choose the backup option that best suits your needs.
  • Adapt the upgrade path to your specific K2 and Windows versions.

Additional Notes:

  • Consult the official K2 documentation for detailed upgrade instructions and compatibility information.
  • Consider seeking professional assistance for complex upgrades or environments.

Comments

Popular posts from this blog

Blocking Error during K2 5.6 Server migration

Client Credentials flow with K2 Cloud with Odata, Workflow REST or SCIM

Blocking error RegisterServiceInstanceObjects when upgrading to K2 5.6/5.7