Upgrade path for legacy N-central versions

To stay up-to-date with the latest features and security enhancements, it’s crucial to upgrade your system from legacy versions to the most recent Generally Available (GA) release. Our upgrades not only bring in new functionalities but also include performance optimizations and bug fixes introduced since your version.

Depending on your version, you may need to perform the upgrade in stages rather than directly to the latest GA release. Upgrading incrementally ensures that all intermediate updates are properly applied, maintaining system stability and compatibility. Each step in the process will address specific version requirements and prerequisites, helping you avoid potential issues.

For a smooth transition to the latest GA version with minimal disruption and maximum benefit from our updated capabilities, please refer to our step-by-step upgrade guides. They will help you determine the necessary stages for upgrading your specific legacy version.

In this topic, we will review the four-stage process of upgrading from versions 2020.1.0.202/2020.2.0.167 to the latest GA release, which can also be applied to any intermediate versions.

Remember, it’s important to follow each stage in sequence to maintain system stability and compatibility.

Version Release Notes

Visit our N-central Release Notes Summary for all Release Notes up to version 2023.9.1.30. For Release Notes for 2024.1 and later go to N-central Release Notes.

Parallel Upgrade for Virtual Servers

If your N-central server is hosted virtually, you have the option to perform a parallel upgrade. This process is detailed in our Parallel Upgrade of N-able N-central article.

System Requirements

No matter the version of N-central you’re currently using, it’s essential that your deployment’s hardware either meets or surpasses the System requirements for the GA release you are upgrading to.

Upgrade Paths

For additional information on the upgrade paths for a specific release, please refer to its Release Notes.

  • Upgrading 2020.1.0.202/2020.2.0.167+ to version 2021.2.0.146

  • Upgrading 2021.1+ to version 2022.7.1.44

  • Upgrading 2022.8 and 2023.3 to 2023.4.0.32 (optional)

  • Upgrading 2022.7.1.44/2023.4.0.32 to 2023.9.1.30

  • Upgrading 2022.7.1.44+/2023.4.0.32 to latest GA Release

While it is possible to upgrade directly from version 2023.4 to the latest GA release, we recommend first upgrading to version 2023.9, and then proceeding to the GA release.

Upgrade to intermediate version

The following upgrade steps cover:

  1. Check Azure Deployment: If your N-central server is hosted in Azure, confirm that you are using the Managed Disk deployment. How to Identify a Legacy Azure N-central Instance.

  2. Upgrade OS: Upgrade the OS on your Report Manager/Helpdesk Manager/On-Premise PSA solution to ensure they’re no longer running on 2012 R2. This prevents communication breakdown as N-central is unable to communicate with third-party applications hosted on Windows Server 2012 R2 and older, after the upgrade to N-central 2022.5. This step is only required if upgrading 2021.2.0.146+ to version 2022.7.1.44.

  3. Backup N-central Server: Perform a backup of your N-central server and save the backup set to an FTP server or another safe location. Refer to N-central Backup and N-central backup best practices.

  4. Prepare for Disaster Recovery: In the event of a disaster recovery scenario, consider capturing a snapshot/checkpoint while the N-central server is shut down. For details review Can I Take a VM Snapshot Of My Server?

  5. Disable Agent and Probe Upgrades: During the upgrade process, it’s recommended that you deactivate the Agent and Probe upgrades by following our ‘Upgrade Plan’. Once the upgrade to the latest GA release is complete, you can reactivate these upgrades.

  6. Download N-central File:

    While it is possible to upgrade directly from version 2023.4 to the latest GA release, we recommend first upgrading to version 2023.9, and then proceeding to the GA release.

  7. Confirm SHA256 Value: Verify the SHA256 value of the downloaded file using tools such as Hashcalc.

  8. Disable Outbound Communication: Ensure that outbound communication is disabled on your server.

  9. Reboot N-central Server: Perform a reboot of your N-central server.

  10. Upgrade N-central: Follow the steps outlined in our guide to upgrade N-central.

  11. Post-Upgrade Wait Time: Once the upgrade completes successfully, please allow at least one hour before proceeding to the stage 2 of the upgrade process.

Repeat this procedure to upgrade your current version to a version that supports the final upgrade to the latest GA release.

Upgrade to the GA Release

Once you’ve upgraded to a version that supports the final upgrade to the latest GA release, proceed by following the previously outlined procedure up to and including Step 5.

  1. Review Checklist: Go through our upgrade checklist, which includes deploying the “N-central Agent SSL Communication Check” Service Templates.

  2. Download NSP: Assuming all checklist items pass, review the upgrade path and download the GA release NSP from N-ableMe (login required).

  3. Confirm SHA256 Value: Verify the SHA256 value of the downloaded file using tools such as Hashcalc.

  4. Disable Outbound Communication: Ensure that outbound communication is disabled on your server.

  5. Upgrade N-central: Follow the steps outlined in our guide to upgrade N-central.

  6. Re-enable Outbound Communication: Once the upgrade completes, re-enable outbound communication on your server.

  7. Run Probe Upgrade Script: Execute the probe upgrade script.

  8. Upgrade Probes: Start by upgrading your probes, which will help distribute the load for agent upgrades.

  9. Upgrade Agents: Follow the steps to upgrade your agents.