Home7.x Network GuideFAQsMoving 7.x Concurrent Network to a New Server

3.14. Moving 7.x Concurrent Network to a New Server

Applies to:
Palisade 6.x/7.x Concurrent Network licenses
Palisade 5.x licenses managed with Palisade Server Manager

How do I move a Concurrent Network to a new server?

The answer varies slightly, depending on whether you have an activatable license (also called "trusted storage") or a certificate license. (Server Manager displays the license type in the lower window of the main screen. If the window is too narrow, hover your mouse over an entry or expand the window.) If your license is the activatable type, you can choose between a 30-day transitional period when both old and new servers are on line, or just finishing the transfer as quickly as possible.

Activatable Licenses, Method 1 – Transfer with Transitional Period

This method affords zero downtime, but there are extra steps to obtain and activate a 30-day temporary license.

  1. Contact Palisade Technical Support with your serial number and request the Server Manager installer, the client installer, and a temporary 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.

  2. On the new server, install Server Manager, activate the temporary license, and post the client installer and the Palisade_NetworkClient.ini file. See Server Setup Procedure.

  3. Redirect the existing clients (end user computers) to the new server for licensing. See How do I change port numbers or server names on existing Concurrent Network clients?

    Exception: If you're upgrading the Palisade software version at this time, skip the redirection step and install the new software right over the old, using the Palisade_NetworkClient.ini file from the new server; see Client Setup Procedure. You can use the same installer on new clients as well.

  4. On the old server, run Server Manager, write down the Activation ID and number of concurrencies, and deactivate the license; see Activating and Deactivating Licenses. Uninstall Server Manager or not, as you choose.

  5. You don't need a new permanent license. On the new server, run Server Manager and activate the license you just deactivated on the old server. You can then deactivate the temporary license to tidy up your Server Manager display, if you wish.

Activatable Licenses, Method 2 – Faster 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.

  1. Contact Palisade Technical Support with your serial number and request the Server Manager and client installers. You don't need a new license.

  2. On the old server, run Server Manager, write down the Activation ID and number of concurrencies, and deactivate the license; see Activating and Deactivating Licenses. Uninstall Server Manager or not, as you choose.

  3. On the new server, install Server Manager, activate the permanent license that you just deactivated, and post the client installer and the Palisade_NetworkClient.ini file. See Server Setup Procedure.

  4. Redirect the existing clients (end user computers) to the new server for licensing. See How do I change port numbers or server names on existing Concurrent Network clients?

    Exception: If you're upgrading the Palisade software version at this time, skip the redirection step and install the new software right over the old, using the Palisade_NetworkClient.ini file from the new server; see Client Setup Procedure. You can use the same installer on new clients as well.

Certificate Licenses – Transfer Procedure

With certificate licenses, the first certificate on a new server is always for a maximum of 30 days, ensuring zero downtime during the transition.

  1. Contact Palisade Technical Support with your serial number and request the Server Manager and client installers.

  2. On the new server, install Server Manager.

  3. Send Palisade Technical Support the needed host information about the new server; see Server Steps 1–3. Tech Support will respond with a 30-day temporary certificate license file. (Your old certificate license will not work on a different server.)

  4. Install the certificate and post the client installer and the Palisade_NetworkClient.ini file. See Server Steps 3–5.

  5. Redirect one existing client (end user computer) to the new server for licensing; see How do I change port numbers or server names on existing Concurrent Network clients? Or, just install on a new client machine.

    Exception: If you're upgrading the Palisade software version at this time, skip the redirection step and install the new software right over the old, using the Palisade_NetworkClient.ini file from the new server; see Client Setup Procedure. You can use the same installer on new clients as well.

  6. When you have verified that a client is able to get a license from the new server, send the Server.lic file from the new server to Palisade Technical Support and request a production license file. You can easily find the file by clicking Open .LIC Folder in Server Manager on the new server.

  7. Install the production license, following the instructions you'll receive from Tech Support.

  8. Redirect the other existing clients (end user computers) to the new server for licensing, or install the software upgrade.

  9. On the old server, run Server Manager and click Stop Service. You can then uninstall Server Manager or not, as you choose.

Last edited: 2015-04-10

This page was: Helpful | Not Helpful