The three things we need as mentioned in the video are the following: The existing license key The old IP address of the database server that hosts the Administration database
Simply copying the licenses from the old system, or not doing anything after a virtual machine is moved, will render the existing licenses invalid. Without valid licenses the SLM server cannot launch, and as result products trying to use this sever will throw errors like:
This is for an initial VM 5.2 install. 1. Install Version Manager WIN 95 5.2 and the Licenses on the NT Server from the PVCS Admin's WIN 95 WorkStation.
The data volume's files can be changed without signoffs as long as the user has the appropriate LAN permissions into the directory and the file. Here are the source files, configuration and initialization files, license assignments and on-line back-ups.
Continue following Licensing steps. When a key is generated at Step 5, you must move it to the license server machine - either by saving it to a text file that can be accessed from the network or through FTP (allowing you to do a clipboard copy on the server), or by making a hardcopy print so it can be manually entered. Enter or paste the key into the box in the Merant License Manager on the license server.
Setting a SYSTEM variable to reference the islv.ini or moving it back to the windir on the server would fix this problem. This is noted in section 2.5.x of the Tracker 6.0 readme file.
Option A Obtain a new license key from Serena support for the new IP address the new install of Mover will reside on. Log into the existing install of Mover, using the Administration option.
