You have multiple Package licenses files that you need to combine to into a single (combined) license file for use with LMTOOLS.
There are several documents on combining licenses:
Combining Autodesk® license files
Combining network license files
Combing Network (Floating) Licenses
Package license files for prior version licensing
There is lots of good info in those documents, but I thought it would be good to pull the info from those documents into a single area for combining AutoCAD/Revit license files.
Notes (from TS65928):
* Newer Autodesk product licenses often require a newer version of FLEXlm. See related solutions for details on upgrading the FLEXlm version for your newest Autodesk product.
* When adding additional licenses for the same Autodesk product to your license file, you must obtain a new license file for the total number of licenses with that feature code, not just the new ones. For example, do not combine two different AutoCAD® 2006 license files into one file. Obtain one new license file that contains the required total number of AutoCAD 2006 licenses.
* If the server has more than one network adapter installed, all of the Autodesk products must be bound to the same adapter.
* Always combine all increments included in all license files, including PLIST increments. FlexLM will automatically determine which PLIST is the most current and use that increment accordingly. If you fail to include PLIST increments, certain Autodesk products may not be able to acquire a network license.
Notes specific for Package licenses relating to combining licenses (from TS1085008):
* Do not combine package license files with non-package license files for product versions contained in the package. Doing so will disable the older license INCREMENT for the product and only the package license count will be available. For example, do not combine an AutoCAD 2009 package license file with a regular license file for AutoCAD 2008, 2007 or 2006.
* Both the PACKAGE and INCREMENT sections of this license file are required for licensing to work correctly. When you combine license files, be sure to include both of these sections along with any PLIST INCREMENTs.
Package license have the following sections:
SERVER servername 123456789012
VENDOR adskflex port=2080
Instructions for combining licenses (from TS1072886):
1. Using Microsoft Notepad, open each of the relevant license files. They will be in either the LIC or DAT file format.
Note: You should only open network license files with Notepad. Other applications, such as Microsoft® Word, may interfere with the ASCII file format, possibly adding unwanted formatting information and thus corrupting your license.
2. Select the most recent file and save this file under a new name. You will use this file as the master file, adding the contents from each of the other license files into it.
3. In each of the license files, copy the license text from the below the "VENDOR" section to the end of the file and paste each the copied data into the main file. (This is a slight modification from the TS doc above, it has you include the Vendor line when copying, but it isn't needed.)
4. Once you have copied all of the license data into the main file, save the new license file to the License folder on the FLEXlm server (by default, C:\Program Files\Autodesk\Network License Manager\License).
Note: Make sure that your network license file was not saved as a TXT file. Network license files must have either an .lic or a .dat file extension.
After going through these instructions you should have something that looks like this:
SERVER servername 123456789012
PACKAGE (First license)
PACKAGE (Second license)
PACKAGE (Third license)
Autodesk Support Specialist
Revit Product Support
SERVER servername 123456789012
INCREMENT (adskflex license)
INCREMENT (sgiawd license)
So it's impossible to combine licenses created on different dates (e.g. ISSUED=27-Nov-2010 and ISSUED=02-Jun-2011, in my case)?
All liceses are on subscription, there are ten 64300ACD_F and six 64900CIV3D_F licenses issued earlier and then next five 64900CIV3D_F.
Two separate services?
Your AutoCAD files are fine because they are a different product release, however you will need to regenerate both of your 64900CIV3D_F Civil 3D licenses files together on the same day before combining them. This should not be a problem.
hope that this could be done quickly. I wonder what could happen in similar situation, except for some licenses being under expired subscription....
The Subscription license would likely supersede a non-subscription license of the same product. You cannot combine the two without also creating a license for the Subscription product without the PACKAGE feature... essentially creating a non-Subscription license.
Is there any particular order to the license file in terms of adding package and increment for suites and regular product, so that the functionality of regular product licenses get used first, and then if available licenses are depleted, it'll start doling out the suite version of licenses. Could swear that I saw a post about the fact there was a preferred order, but can't find it again... I have a 50-50 chance of getting right or wrong... my guess is to have the regular licenses come first, then put the suites below it in the license file... just a guess.
I have following situation:
A user has one NLM Maya 2012 with subscription and one NLM Maya 2011 without subscription. Can these two increments be combined into one license file? Accoriding to this forum thread it cannot. Probably because you cannot know for certain which productlicense is acquired when booting Maya 2011, without subscription. Which license will it acquire, subscription or non-susbscription? If it will acquire the subscription license first, an other user will not be able to start Maya 2012 on a subscription license.
Is the information mentioned above correct? If so, is it possible and allowed(!) to work with a combined license file and an option file to ensure the proper license with the proper product?
I hope you have an answer to, or a link to a paper explaining, this issue.
Thank you in advance.
With kind regards,
At a customer site (I work for an Autodesk VAR), I've seen a similar situation, and this is how I believe it goes down. The customer removed a block of AutoCAD licenses from their network license pool. For this example, we'll say they had 50 AutoCADs on subscription, then dropped 10 of those AutoCADs, where the AutoCAD version was 2011 at the time of this contract change. From Autodesk Registrations and Activation, they were able to get a network license file for 40 AutoCADs still on subscription (thus could run the current version of AutoCAD and up to 3 prior versions for up to 40 users) but they were also issued a 10-seat network license file for the 10 AutoCAD 2011 license peeled off of subscription. The 10-seat license group only allows the specific software version at the time it was removed from subscription (2011).
The 40-seat network license was obtained automatically on the registrations site, but to get a license for the non-subscription network pool of 10 seats required manual intervention with a Autodesk registrations operator. Both license files were added to the master license file, both license groups become recognized in the FlexLM license manager. In this example, if everyone used AutoCAD 2011, they still effectively had 50 seats. When the customer starts using AutoCAD 2012, they can only run 40 AutoCAD 2012, but still be able to run 10 AutoCAD 2011 versions.
I welcome any corrections or further insight in how this works.