You can create a Windows environment variable called ADSKFLEX_LICENSE_FILE and the value of that variable can point to the server name or IP address.įormatting is simple. I’m certainly not alone in this, this is the preferred method of identifying license servers for many users. Combine that with having either or both of the lic path and the server name makes this method one to avoid. I’m not a fan of poking around the registry when I really don’t need to. The value in this key can either be the licpath.lic file or a server name.
In the Windows registry under look for the ADSKFLEX_LICENSE_FILE key. In what feels like a very antiquated way to store data, there also is a registry key you can update. Autodesk License Server Registry Setting – DEFINITELY Not My Favorite Pretty easy, but tracking down the licpath.lic file for each piece of Autodesk software installed on your PC can be a time sink. So updating it is just a matter of changing “LICENSE-SERVER-NAME” to the name of the new server. When you open it up it looks like this: SERVER LICENSE-SERVER-NAME 000000000000 The licpath.lic file is just a text file that sits either in the program folder, or in one or more subfolders under C:\ProgramData\Autodesk\CLM\LGS.
I’m going to quickly run through the places it can be kept, and then let you know my favorite way to tell a PC where to find a license server and why. Once you know where to look, it’s not bad, but there are a couple of places that old server name could be stored.
That server name gets baked into some files on the PC, and there isn’t always a straightforward way to point to the new server. And if you tell it to use a network license, you then have to tell the software what the computer name or IP address of the license server is. Typically when you install an application like Revit or AutoCAD, you tell the software what kind of license it uses. But a question often comes up: how do the end user PCs find the new license server now? Where a PC Keeps Its License Server Information Reinstalling the license software on a new server is about just as easy as it was on the first server. A small application sits on a server and end users PCs point to that license server to “check out” licenses as they need them.īut, as we all know, sometimes a server dies or it’s time to upgrade it. It’s pretty painless to set up, easy to leverage and can be a smart move for groups of users. Many large organizations use Network Licensing to manage their pools of software licenses.
0 kommentar(er)
