Palisade Knowledge Base

HomeMore on NetworksServers (5.x)Moving 5.x Concurrent Network to a New Server

4.10. Moving 5.x Concurrent Network to a New Server

Disponible en español: Como transferir una licencia Concurrente de Red 5.x a un nuevo servidor
Disponível em português: Transferindo o Software Simultâneo em Rede Versão 5.x da Palisade para um Novo Servidor

Applies to: Palisade release 5.x Concurrent Network licenses without Server Manager
(If you're using Palisade Server Manager to manage your licenses, see Moving 6.x Concurrent Network to a New Server or Moving 7.x Concurrent Network to a New Server.)

I have a Concurrent Network installed for Palisade software release 5.x. How can I change servers?

The answer varies slightly, depending on whether you have an activatable license (also called "trusted storage") or a certificate license. It also depends on whether you want a transitional period when both old and new servers are on line, or you want to perform the transfer as quickly as possible. Certificate license files are usually named in the pattern SN5nnnnnn-yyyymmdd.lic. If you're not sure of your license type, query Palisade Technical Support and include your serial number.

Before you begin any of these methods, you need:

Activatable ("Trusted Storage") Licenses — Transfer with Transitional Period:

If you have an activatable license and you want a faster method, or if you don't have a current maintenance contract, please see "Faster Method of Transfer", below.

A. Use your original installer to install the software on the new server. (See Server Step 1 in the Readme file.)

B. Contact Palisade Technical Support with your serial number and request a transitional license. Please do this when you're actually ready to start transitioning the clients, so that the license doesn't run out before you've finished the transition.

C. Edit that temporary Activation ID into the TransferLicenses.bat and Request.bat files, and perform Server Steps 2–5 in the Readme file. This will activate the transitional license on the new server.

D. Redirect the client (workstation) computers to look to the new server for licensing. You could reinstall all the clients from the Client Installer folder in the new server, but it is much easier simply to edit the System Registry. Please see details in Redirecting a 5.x/4.x/1.x Concurrent Client to a New Server.

E. You do not need a new permanent license. Deactivate the licenses on your old server, according to the procedure in Deactivating (Returning) 5.x Network Licenses. Edit the old permanent Activation ID into TransferLicenses.bat and Request.bat on the new server, and perform Server Steps 2 and 3 to activate the permanent license on the new server. In LMTools, on the Start/Stop/Reread tab, click Re-read license.

Activatable ("Trusted Storage") Licenses — Faster Method of Transfer:

The fewer end users you have, the faster you'll be able to redirect them to the new server, and the more attractive this alternative becomes.

A. Deactivate the licenses on your old server, according to the procedure in Deactivating (Returning) 5.x Network Licenses.

B. You do not need a new permanent license. Use your original installer, and the Activation ID you just deactivated on the old server, to install and activate the software on the new server. (See Server Steps 1–5 in the Readme file.)

C. Redirect the client (workstation) computers to look to the new server for licensing. You could reinstall all the clients from the Client Installer folder in the new server, but it is much easier simply to edit the System Registry. Please see details in Redirecting a 5.x/4.x/1.x Concurrent Client to a New Server.

Certificate Licenses — Transfer Procedure:

A. Follow Server Steps 1–4 in your Readme file. This will install the license process with a 30-day transitional or test license.

B. Redirect the client (workstation) computers to look to the new server for licensing. You could reinstall all the clients from the Client Installer folder in the new server, but it is much easier simply to edit the System Registry. Please see details in Redirecting a 5.x/4.x/1.x Concurrent Client to a New Server.

C. After you verify that everything is working, contact Palisade Technical Support for a production license certificate on the new server.

With certificate licenses, there is no special procedure for decommissioning the old server. You will want to stop the license process (Start/Stop/Reread tab in LMTools), but if you're planning to wipe the old server then even that's not necessary.

Last edited: 2016-02-25

This page was: Helpful | Not Helpful