Transferring Network Licensing

Created by Steve Hill, Modified on Thu, 25 Jul at 8:17 AM by Steve Hill

Please note that migration of network licensing requires three parts, New Server setup of LMTOOLs and Vendor Daemon, Client computers setup of app installation / Client environment variable pointing to the new server, and shutting down the old server.


Part 1A - New Network Server License File

Send the new server information to licensing@redtransitconsultants.com to obtain your new server license file. Once received, you can proceed. We need the Server Name and Mac address to issue the license.


IMPORTANT: If you subscribe to multiple products and use Network Licensing, you will need a merged license file of all products to use on the server. From the portal below, once logged into your account, use the Download Merged License button to generate the merged license file(s) for all products with the same computer names, license types, and expiration dates available on the account.



Part 1B -  New Network Server

You may need to review the following Solution pages to assist you. Note that in the license file I have specified specific port of 27010 for the LMGRD to execute my vendor on and a specific Vendor Port of 2081. You can change these as you wish but be sure to make sure they are not set to 27000-27009, or 2080 as that’s what Autodesk uses, and be sure they are unblocked in Firewall.


Network / Floating License Instructions


Troubleshooting Network Licensing


Common Flexera Error Codes


Part 2 - Client Computers

Client computers will need to be pointed to the new server. This can be done through Environment Variables or manually pointing users to the server using the Flexera License Manager dialog.


Environment Variable Method

This can be done via Environment variable if that's how it was initially setup. This can be pushed out from the server via a Group policy. More information on pushing out Environment variables can be found at the following link. You'll just want to be sure you edit a previous Group Policy if that's how it's being pushed out.


If you prefer to manually adjust, you can find the Environment Variable on each computer and manually change to the new server using the same "Port@ServerName;Port@IPAddress" format to locate the server.


Client Environment Variable


Flexera License Manager Dialog Method

To force the dialog to reappear, you'll need to clear out the registry saved location on the client computer(s). Or, you may adjust the registry value to the new server using the same "Port@ServerName;Port@IPAddress" format to locate the server.

  1. Go to Registry Editor.
  2. Browse to: Computer\HKEY_CURRENT_USER\Software\FLEXlm License Manager
  3. Check for key: “FLEXRTC_LICENSE_FILE”
  4. If it exists, Edit the key and clear out the value.

If you clear out the path, then in Civil 3D, locate the app on the ribbon and execute the a tool. The Flexera Dialog should appear and you can choose Network license and then enter in the same "Port@ServerName;Port@IPAddress" format to locate the server.


Verification

If desired, verification the client computer is pointed to the new server can be done with LMTOOLs on the new server. From the Status tab, perform a Status Inquiry and look for their username - or if you look through the debug log, you should also find their username for check out / check in of licenses.


Part 3 -  Old Network Server

Once all client computers are pointed to the new server, then you may use LMTOOLs on the old server and stop the service from the Start/Stop/Reread tab. Once that is done, use the Config Services tab and remove the service. This will delete the service, but not the license files and LMTOOLs. That would need to be done separately.






Let me know if you have any questions or issues migrating..

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article