06-06-2019 05:56 AM
I would prefer to use the simpler Flexnet license server method rather than the VLM for managing floating licenses.
However, I need to package the NI software up to ease distribution from a shared network folder.
Is it possible to use the Volume License installer part of the VLM without having to have the license manager setup and instead get the installations to point to the flexlm server?
This is required as there are different departments with their own administrator who need to deploy their own custom installations to labs and office machines.
We don't have direct access to the license servers.
06-07-2019
03:47 AM
- last edited on
07-17-2024
06:12 PM
by
Content Cleaner
I found this: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YH80CAG&l=en-US
It usefully states that NI VLM can be installed on a machine that is not the VLM however it insists on an agreement file valid on the computer I'm running it on before I can go any further (v3,2). I need to get at the "Create Volume License Installer" part.
06-11-2019
02:21 AM
- last edited on
07-17-2024
06:12 PM
by
Content Cleaner
Hi Andygav,
Is it possible to use the Volume License installer part of the VLM without
having to have the license manager setup and instead get the installations to
point to the flexlm server?
The answer to this question is simply no.
The only option is to use a custom type of license file that is written specifically for FlexLM. You can get custom license files for FlexLM by contacting Agreements@ni.com as stated in step 1 in Getting Started with FlexNet Publisher Configuration.
I hope this was helpful.
Best regards,
Marcus Bengths, TSE
06-19-2019
02:44 AM
- last edited on
07-17-2024
06:13 PM
by
Content Cleaner
I think I'm getting the hang of this...
I've set up a license server using the FlexLM daemons and with a flexlm formatted license file. That works. Whilst configuring the services using lmtools another NILM service sneaks in. I deleted that but I need to know why this appears. The link from KnowedgeBase 489FTAXT: Why Does "NILM License Manager" Show Up in LMTOOLS? doesn't work.
Anyway, in order to use the VLM I had an agreement file created on the PC that I'm going to run it on (i.e. the 'technicians' PC) but when creating the Volume License Installer, I get it to point to the server running the NI FlexLM. I don't start the volume license server on the technicians PC.
The license file is unmanaged concurrent. We don't want to use groups, so I deselected the installer to request permission to join groups. It all starts up without asking the user difficult questions. Jobs jobbed!
I might have a play with using specfiles and avoid using the VLM altogether.