Introduction
Transferring an SL (software-based) license key for an Intella product may become necessary for several reasons. Common
scenarios include upgrading to a new machine with improved hardware,
moving from an on-premise environment to a cloud-based setup, or
transitioning from a trial installation to a dedicated production
server. Ensuring a smooth license transfer process is essential to
maintain uninterrupted access to your Intella products and to safeguard
your case data. This article outlines the steps required to successfully
transfer your SL key, helping you avoid common pitfalls and ensuring
your system remains fully operational throughout the migration.
Prerequisites
Before transferring your SL (software-based) license key, ensure the following prerequisites are met:
- Administrative Rights: You have administrator privileges on both systems to perform the license transfer and software installation.
- Access to Both Machines: You have administrative access to both the current machine (where the SL key is installed) and the new machine (where the SL key will be transferred).
- Compatible Operating System: The new machine meets the minimum system requirements and is running an actively supported version of Windows or Windows Server.
- Intella Software Installed: Your Intella product is installed on the new machine. You can download the latest installer from the Vound Software Downloads page. Information on installing and migrating the software can be found in the user manual of your product.
- License Transfer Tool: The haspupdate.exe tool (located in the bin folder of your Intella installation directory) is available on both machines.
-
Valid License Key: Ensure your SL license key is valid and not disabled or cloned. Although you may be able to transfer the license, the license will remain disabled or cloned after the transfer.
- On the current machine, open a web browser and navigate to http://localhost:1947/int/devices.html. Check the “Key Type” column for your SL key. If you see “Cloned” or “Disabled,” the license has been invalidated and will not work when transferred.- Alternatively, visit http://localhost:1947/int/features.html and check the “Restrictions” column for any red text indicating license issues. - Back Up Important Data: Back up all important case data, configuration files, and license information on the current machine to prevent data loss. Data loss isn’t anticipated, but maintaining backups is always a wise precaution. Though, please note that once you begin the instructions in Steps to transfer the SL key, these instructions must be followed exactly, as the SL key can be lost during the transfer process.
- Deactivate/Unshare Cases: On the original machine, un-share any cases you wish to migrate to avoid data corruption during the transfer.
Steps to transfer the SL key
For a smoother transition, it is recommended that the machine(s) hosting Intella are configured to reference both the old and new license servers in http://localhost:1947/int/config_to.html
prior to migrating the SL keys. This way, the "active" license will
be detected automatically when the license becomes available on the new VM. Refer to the user manual on the "Network licenses" section for up to date prerequisites and steps how to do this.
1. Ensure you meet the prerequisites above.
2. On the machine that will receive the license, open haspupdate.exe (located in the 'bin' folder of the Intella installation directory), and click "Transfer License".
3. In the "Step 1" panel, enter a file name in the "Save recipient information to" field.
4. Click Collect and Save Information. This will generate a fingerprint of this target machine, to which the SL key will be bound.
5. Move this .id file to the machine that currently holds the SL key.
6.
On that machine, open haspupdate.exe > Transfer License.
7.
In the "Step 2" panel, select the SL key that you want to migrate.
8.
In the "Read the recipient information file from" field, enter the path of the ID file that was transferred here in step 4.
9.
In the "Generate license transfer file to" field, enter the name of a .h2h file that is to be generated.
10.
Click the Generate License Transfer File button.
WARNING: doing so will immediately remove the SL key from this machine. Furthermore, loss of the generated .h2h file will result in an inability to restore the SL key to the target machine. Create a back-up of this file as soon as you can.
11.
Move the generated .h2h key to the target machine.
12.
Open haspupdate.exe > Apply License File on the target machine.
13.
Select the .h2h file and click Apply Update.
The selected SL key will now be present on the target machine.