Installing and Configuring the Flexera FLEXnet® License Administrator
In addition to the Autodesk Network License Manager, Autodesk products can be configured to use the 3rd party Flexera FLEXnet License Administrator service to manage licenses for the Autodesk network applications. Other vendors may also use the FLEXnet service. Therefore, it is important to recognize that if other vendors are using the FlexLM (LMTOOLS) then you should not run the web-interface FLEXnet in conjunction with it. Only one license manager type should be used for all products.
For new installations of FLEXnet, please use the following procedure:
Optional: To modify the startup behavior of the service, see the Startup type under Windows Services in Administrative Tools (services.msc)
You should now be able to access the FLEXnet License Administrator via the web browser and using the credentials created in Administration.
At the time of this post, the latestion version is 22.214.171.124. Special thanks to Darin.Green for requesting that I write an installation and configuration guide for this license manager.
The necessary adskflex.exe 32-bit version is attached to this post for your convenience. Good Luck!
Solved! Go to Solution.
Great Post! Thanks for the shout-out.
The following are known issues with the FLEXnet License Administrator:
1. The FLEXnet is available only in 32-bit versions. It will be installed as a 32-bit web application on 64-bit servers. Therefore it is only necessary to use the 32-bit version of the adskflex.exe vendor daemon
2. There does not appear to be any logging of currently borrowed licenses. The Dashboard will show the hosts that have licenses checked out, but there does not appear to be any notification (linger) as in the Autodesk Network License Manager (LMTOOLS)
3. One user has made claims that the license count for a Suite of products is being incorrectly identified. I have not reproduced this issue.
4. The status of the Vendor Daemon screen does not appear to update unless you refresh or navigate away and come back. I have made note of this in my installation steps above.
5. This license manager is not approved for use by Autodesk and will not be supported in production environments. It is suggested that this be used for testing purposes only. Please use at your own discretion.
For information on the Autodesk Network License Manager (LMTOOLS) please see my original signature post here:
Hopefully you should see from the attached file that the license count for the 2010 products doubles the available licenses I think it could be a bug?
Okay, for an update on the conversation between us off record, I have determined that the issue of license doubling is simply a graphical anomoly.
I have run the actual LIC file thru the license parser and it came back with the correct amount of seats.
When I ran the BDSPRM in the FLEXnet, however, it did show 2x licensing for the same 2010 products as in your screen capture. As it turns out, this is only a graphical error as the working of the license manager are still as expected. When I reserved a seat of ARCHDESK_2010, it doubled the reservations as well. Once I reached the maximum amount of seats owned, the licenses were exhausted by error in the Alert field, as expected. I was unable to reserve more than the maximum amount of seats owned regardless of the number shown on the Dashboard. Combining your 5 seat and 1 seat yielded 12 seats for 2010 but only 6 work total. This tells me that there is a interpretation issue with your PACKAGE Feature Code and not the INCREMENT line. See image below:
When I tested an identical BDSPRM 4 seat license file from another client, I received the expected (4) seats and no doubling whatsoever (see image below.) Therefore, this issue does not exist within the product code and is not reproducible. There is simply an issue with your particular LIC file, but the integrity of the file itself is not problematic. I see no reason to regenerate this file if you plan on using the FLEXnet Administrator.
Thanks for pointing this issue out. There's definitely a minor bug, but it doesn't seem to affect the integrity of network licensing. Again, this license manager is not yet supported by Autodesk but I suspect at some point Flexera will be moving away from the old daemon and into this one.