Edit Lic.dat
Mirtha Hinrichs
While Autodesk has mostly switched to managing software access via Autodesk end-user credentials (see this article), there is still the occasional need to utilize the Autodesk Network License Manager.
Configuring the Autodesk Network License Manager does not have to be an intimidating effort. These simple steps should allow you to quickly and easily configure a working NLM on your network. This guide assumes that you have installed the Autodesk Network License Manager into the default install location using the media provided by Autodesk or from the direct download online.
STEP 2: Verify that the license .LIC file you obtained from Autodesk matches the hostname and Ethernet MAC address on the System Settings tab. If you have not obtained your .LIC file yet, you can obtain one by contacting Hagerman & Company support. Please have your serial number, company name, server hostname, and Ethernet MAC address.
The data provided here should match the license .LIC file. Note: You cannot edit the .LIC file if there is a typo or if the data does not match. If you need a new .LIC file, contact Hagerman & Company to obtain the correct file for your server.
Congratulations! You have successfully configured the Autodesk Network License Manager. You can now install your Autodesk network licensed products on your clients and point them to the hostname of this server.
Configuring the Autodesk Network License Manager does not have to be confusing or intimidating. If you have a redundant or distributed server, then the process is identical amongst multiple servers. If you have questions or need additional troubleshooting, please contact Hagerman & Company support and our experts will be happy to assist you. Keep an eye out for additional quick tips from me.
-First I have this Error: "ERROR (ORCOMMN-12005) Unable to launch Orcad Capture. A valid license wasn found at the 5280@hostname license server. Update the license server configuration to include OrCAD Capture licenses."
If you want help, asking in the wrong forum (this is the "Feedback, Suggestions and Questions" forum, which is for issues with the forums, not for technical questions) is not the right way to go about it. I'll move this to something more appropriate.
Can you upload your debug.log from C:\Cadence\LicenseManager folder? This should give a clue as to the actual issue? For the CDS_LIC_FILE you may not have enough IT user privileges to edit this so either you or IT go to Control Panel - System - Advanced System Settings - Environment Variables, look for CDS_LIC_FILE and make sure the value is set to 5280@name of PC where license is (which could be your computer name).
The padding added at the bottom of the LIC.DAT file seems to be intended to increase size to a multiplier of bluray disc sectors and to protect the laser lens because otherway it is too tiny and so stressing for the laser.
There is a special type of PS3 game disc that contains several EBOOT.BIN with several LIC.DAT files. These LIC.DAT files are a bit special because contains the TITLE_ID of all the EBOOT.BIN files of the disc. Some examples of games using this multiboot disc structure are: Metal Gear Solid The Legacy Collection, Disc 1 (BLJM-91001 on PS3_DISC.SFB), and Fighting edition (BLES-02129 on PS3_DISC.SFB).
Yes, you'll need to use the "download without installing" option in the installer app to download all the files to a Mac, then repackage it for deployment with the key, license, and edited installer_input.txt file (this file is in the downloaded files from Mathworks). I do this and make it a Self Service policy. These are the main steps I take when I'm packaging any new version.
I use the Packages app to repackage the Matlab software. If you use something else your workflow will be a little different, but the end result should be the same. I can give more detail about how I do it in Packages though if that helps. The main thing is to put the license file in the right file path and to place those downloaded files somewhere on the Mac and then trigger the install from that directory. I use Packages to do this because it creates a temporary directory for those files and I don't have to worry about it.
More details about doing this in Packages,
In the Payload tab of Packages, I add the folders where the app will be installed. The license.dat file needs to be in /Applications/MATLAB_R2020.app/licenses/, so I create that location and place the file there. Then, I put all those files that were downloaded (that are currently in the downloads folder) and drag them into the Additional Resources section of the Scripts tab in the Packages. Then I use a postflight script to set the directory and install matlab using those files (those commands are below, I can't share the whole script because of other customizations we do).
@winterboer Not for the file names or the postflight, you should be able to keep it as is. What error are you seeing? The only things you'd need to modify with this workflow would be the contents of the installer_input.txt file and the license file unless you have other modifications to make.
@jchen1225 Yes, it should work as is for the workflow using the Packages app or as long as the postflight script is in the same directory as the installer_input.txt file and the other Matlab installer files.
Jamf's purpose is to simplify work by helping organizations manage and secure an Apple experience that end users love and organizations trust. Jamf is the only company in the world that provides a complete management and security solution for an Apple-first environment that is enterprise secure, consumer simple and protects personal privacy. Learn about Jamf.
This site contains User Content submitted by Jamf Nation community members. Jamf does not review User Content submitted by members or other third parties before it is posted. All content on Jamf Nation is for informational purposes only. Information and posts may be out of date when you view them. Jamf is not responsible for, nor assumes any liability for any User Content or other third-party content appearing on Jamf Nation.
At first i thought the community edition will be sufficient for my private use, but I really would like to edit files from my android phone so I bought a home license.
I copied the license.lic file to /var/www/onlyoffice/Data
Could not check for JavaScript support via any of your trusted_domains nor overwrite.cli.url. This may be the result of a server-side DNS mismatch or outbound firewall rule. Please check manually if your webserver serves .mjs files using the JavaScript MIME type. To allow this check to run you have to make sure that your webserver can connect to itself. Therefor it must be able to resolve and connect to at least one its trusted_domains or the overwrite.cli.url.
Some headers are not set correctly on your instance - The X-Robots-Tag HTTP header is not set to noindex,nofollow. This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly. - The X-Frame-Options HTTP header is not set to sameorigin. This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly. - The X-Permitted-Cross-Domain-Policies HTTP header is not set to none. This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly. - The X-XSS-Protection HTTP header does not contain 1; mode=block. This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly. - The Referrer-Policy HTTP header is not set to no-referrer, no-referrer-when-downgrade, strict-origin, strict-origin-when-cross-origin or same-origin. This can leak referer information. See the [W3C Recommendation] .
Could not check for WOFF2 loading support. Please check manually if your webserver serves .woff2 files. To allow this check to run you have to make sure that your webserver can connect to itself. Therefor it must be able to resolve and connect to at least one its trusted_domains or the overwrite.cli.url. For more details see the [documentation ] .
Hi @ovski,
The guide you linked offers to install the Community Edition version of Docs. It does not have mobile editing and cannot read license files. If you have a license, you need to remove the CE and install Enterprise Edition following the guide:
-enterprise-install-ubuntu.aspx
After some days when it was not possible to generate license file for Questa Starter it is finally possible to do it. But unfortunately the license file that is sent over the email does not allow running Questa Starter.
After trying to run Questa there is an error message saying:"Unable to checkout a license. Make sure your license file environment variable (e.g., LM_LICENSE_FILE)
is set correctly and then run 'lmutil lmdiag' to diagnose the problem."
For Questa software, you must set an environment variable the location of license. you need to specify location of the license file using the LM_LICENSE_FILE system variable (click/checkout the Use LM_LICENSE_FILE variable). You need to set your LM_LICENSE_FILE environment variable to point to the license that Intel provides. c:\intel\license.dat or something similar.
2. Looked all over how to downoad the file... Finally after one hour, I realized that pressing "Generate License" it actually sends the file to my email (!), the notification " blah blah blah blah license was sent to your email" was too fast to read first place.
5. Hit Win, Search, "System Variables", window labeled "System Properties" opened, clicked "Environmental Variables", I set up a New one labelled "INTEL_LICENSE_FILE" pointing to the dat file, pressed ok.
Why should you Intel have done all these SO much complicated? I m almost going to uninstall everything, install previous version with Modelsim and forget all about that. These lost hours should be productive, not the opposite.
I confirm that with the help of the employees, my case was solved. I was instructed to the correct System Variable name:
"LM_LICENSE_FILE" which points to the dat file I was sent from Intel by email (I was using a wrong variable name).