Moving ELM-Virtual Server Edition to new Hardware - VLM

Issue

You find it necessary to move Enterprise License Manager - Virtual Server Edition to a new Virtual server, you need to host the Virtual Image on a new HOST server, or you need to put the LMBIND utility on a different machine.

Solution

There's are three different 'moves' and each is handled a bit differently:

Moving ELM to a new VIRTUAL server

• Instruct all users to return ALL borrowed licenses. Activation codes CANNOT be returned if ANY licenses are borrowed against our vendor daemon (oncenter.exe).
• Once all users have returned all borrowed licenses, use the Activation Utility to return ALL license codes (remember, you need to return EACH license code separately - see Related articles).
• Install LMAdmin and the Activation Utility on the new Virtual Server.
• Set a System Environmental Variable to point to the LMBIND machine.
• Activate your code(s) (your Host ID will not change).
• Start up the license manager, reread license files.
• Instruct users to activate to the new server (name or IP).

Moving a VIRTUAL IMAGE to a new HOST Server

• If you installed LMBIND on the original Host server, you will have to install LMBind on the new Host Server (or choose any physical machine on your network to act as the "Binding" machine).
• If you need to switch from Hyper-V to VMWare ESX or ESXi or vice versa, you just use the appropriate LMBind files (see the ELM-Virtual Server Edition User Guide for more information)
• Extract and note the new Host server's HOST ID
• You will need to RETURN ALL license codes on the original Virtual Server (which means all users have to return ALL borrowed licenses).
• You can then move the Virtual image to a new Host Server.
• Update the Environmental Variable to reflect the new LMBind machine name/port.
• Once you have your new Host ID (from LMBIND machine), you will re-Activate your license codes (your Host ID WILL be different).
• Re-read license files to enable them for users.

Moving LMBind to a new Physical Machine

• You will need to return all license codes on the Virtual Server (which means all users have to return ALL borrowed licenses).
• Follow the instructions in Related articles to pick the correct LMBIND pack and follow the instructions for installing/configuring.
• Extract and note the new LMBIND machine's HOST ID
• Update the Environmental Variable to reflect the new machine name/port where LMBIND is running.
• Once you have your new Host ID (from the LMBIND machine), you will re-Activate your license codes using that new Host ID.
• Re-read license files to enable them for users.