Have an old server with license server for version 2.2, need to move license

Hi Jay,

I am a bit confused by your description but if you revoke a license, a new license key should be saved in a file and you can install that new license key in a different server.

I hope I am remembering this correctly because V2.2 is very old and we have changed our licensing methods several times between then and our current version.

Actually, there may be a problem if you are installing 16 digit auth codes instead of license files (PA keys that are files with an .mflic extension). When you revoke an auth code it may try to reach an old Micro Focus license server that is no longer in commission. You would have to contact your local sales or support office to get new codes. If you have .mflic files then you can uninstall the license on the old machine and then install the license using the .mflic file on the new machine.

You will know that they are PA licenses if they have (PA) next to the serial number in the installed licenses window of the license administrator tool.

in the past, the infrastructure team installed a license server. The production runtime refers to this license server to get the license key. i wanted to revoke the license key on the license server, and install that locally on the runtime server, skipping that step.

The files that i see don’t show any information in them. this is the program on the license server. The runtime server points to this server, to get the license information.

What is shown on the Licenses tab of this tool? This is where the installed licenses appear.

The licenses are kept in C:\PrograData\Micro Focus\lservrc.net as shown in your screenshot.

serial number removed. 3 lines in lservrc.net

under revoke i think we select the license to revoke, and then record the authoriztion code it gives, to apply to the new server.

Yes, but I am not sure if the auth code technique works anymore because i think it wants to contact an old microfocus.com server that went out of commission quite a while ago. If it does and you get an error, you will have to contact sales or 1st line support who handles licensing.