LMS 4 Migration from Evaluation Mode

Question

Hi Team
I have a LMS 4.2, The Server is running in Evaluation mode right now... So I´m going to Instal the new Licenses file on it.
The correct procedure that I have is:
To update to a new license from the Licensing page:
Step 1 Select Admin > System > License Management.
The License Information page displays the license name, license version,  status of the license, and the expiration date of the license.
Step 2 Click Update.
Step 3 Enter the path to the new license file in the License field, or click Browse to locate the new file.
Step 4 Click OK.
The system verifies whether the license file is valid, and updates the  license. The updated licensing information appears in the License  Information page. Otherwise, an error message is displayed.
To return to the License Information page, click Cancel.
I need to known if before upload the new Licenses File, should I uninstall the Evaluation Licenses, someone told me that I need to clear out all the *.lic files ?  That´s correct if yes please let me known the procedure.
Cheers
Bruno Rangel

Answer 1

I've gotten the advice both ways from the TAC. I can confirm that I have a working LMS 4.2 installation with permanent licenses that did not clear out the evaluation licenses first. So I'm taking my second TAC answer as more authoritative.
If you need to remove old licenses, it's a bit complex - you need to go into the shell, navigate to the license directory, stop the LicenseServer daemon, remove or move the .lic file and put the new ones and and then restart the daemon.
The GUI should allow you to avoid all of that and it is not necessary to remove the old lic file(s).
You do need to ensure that the permanent licenses you are given are properly generated. The licensing team tool has had some issues with properly creating LMS licenses. If you open your permanent license in a text editor, make sure it specifies "LMS cisco 4.1 permanent" in the body (and NOT "LMS cisco 1.0 permanent"). The latter will be accepted by the GUI but not result in proper registration with the daemon.