Custom License File

[tahdesign1]

I have pulled down a new license file and upgraded my LmTools to run the 2019 product. All of my products are perpetual networked and I have a few that actually belong to other groups in the company. All of my ADSK product are using a single license server.

With the 2017 product upgrade (our first to a networked licensing system from standalone), I ran into some issues where lower softwares like plain AutoCAD were taking licenses of higher softwares like Inventor. I was told at that time that it would require a custom license file in order to prevent that from happening. However, since putting the 2019 license file in place and upgrading the LMTools something seems different. When I run a report I can see that the AutoCAD seats are taking their proper licenses.

So my questions:

1) Has something changed that will not require me to make a custom license file to prevent this?

2) Without a custom license file when I run plain AutoCAD from an Inventor suite will it take the Inventor License as it should?

3) If I will require a custom license file I would like some guidance in how to format it correctly. I assume I start with a copy of the license file I pulled from ADSK and edit that. From what I remember I would have to be specifying the PC names that are allowed to run a specific flavor of software.

[Mark.Lancaster]

@tahdesign1 

There's a pecking (cascading) order https://knowledge.autodesk.com/customer-service/network-license-administration/managing-network-lice... for product and the order of the license file isn't relevant (even back in 2017).  Not sure what you were seeing back for your 2017 product line without reviewing the debug log file at that time.  Most products except a couple (like Inventor) will always pull the lowest license it can fine based on the cascading order.

However there's been some flukes here and there and the license manager doesn't always work as intended for everybody or every time.  Although you don't have to worry about it but when you start mixing term with perpetual, it adds another level of cascading and when you start mixing collections, well another layer is added.

At this point the order is not going to matter or that you need to create a custom license file.  If you end up with an issue the debug log file needs to be reviewed to see what's going on and then you can troubleshoot from there.