Managed Content Server upgrade

Created: March 25, 2021 | Updated: July 21, 2022

This document covers a best practice quick review of the steps to follow when upgrading your current on-site managed content server to our current version. As when you have been using Vault and want to upgrade to Concord Pro.

Solution Details

If you are upgrading to a different version (Vault or NEXUS to Concord Pro) use your dashboard to get the *.alf license files that you use for your Vault/NEXUS server (CALs too) so that you can use them if needed.  Then you can work with your account manager to get your Vault/NEXUS licenses converted to Concord Pro (or whatever the next version is) licenses.  This may take a day, but is not necessary if you are not upgrading to a differently named version.
 
Also save a copy of your production server's Vault.ini file to a safe place.  You can find it here:

C:\Program Files(x86)\Altium\[Altium Concord Pro]or[Altium NEXUS Server]or[Altium Vault]\LocalVault.ini
Generally it won't be needed, but it might just come in handy later for comparison.
 
Install the same version of your current managed content server that is running on your production server onto a new "Test" server. Next, run a backup of your production server with avbackup.exe and restore it onto your test server and make sure everything looks good. Here's a link with more information:
https://www.altium.com/documentation/altium-nexus/backing-up-and-restoring-your-altium-nexus-server
 
Install Concord Pro (or whatever the next version is) on the test computer. You can download our current version from here:
https://www.altium.com/products/downloads
 
The installation will recognize the current installation and perform an upgrade. You should then delete all the license files (CALs too) and install the current license files after you've had them converted by your account manager if necessary (see above.). Here's a link to the installation, licensing & Management documentation for Concord Pro (notice there are lots of other documents in the left pain (above and below) that may be of interest):
https://www.altium.com/documentation/altium-designer/altium-concord-pro-installation-licensing-management
 
Check out the new installation and if everything went smoothly, it should be safe to perform the upgrade on your production server. Get a backup first.

After updating Concord Pro you may experience some of these issues: The "500 Internal Server Error" error message. Component cannot be released. Health monitor may show index errors. Re-indexing likely will resolve these issues. This article tells you how:
https:/https://www.altium.com/documentation/knowledge-base/altium-concord-pro/concord-pro-issues-after-migration-re-index

Please note, You should be using the Altium Designer client with Concord Pro and later versions.  If you were using the  NEXUS client, you will need to download and install Altium Designer which you can do from here:
https://www.altium.com/products/downloads
Was this article helpful?
0
0
Found an issue with this document? Highlight the area, then use Ctrl+Enter to report it.

Contact Us

Contact our corporate or local offices directly.

We're sorry to hear the article wasn't helpful to you.
Could you take a moment to tell us why?
200 characters remaining
You are reporting an issue with the following selected text
and/or image within the active document: