Restrict License Allocation on Specific Client - FlexNet Publisher

Question

question

Joaquín MSV asked Feb 13, '25 Joaquín MSV commented Feb 26, '25

Restrict License Allocation on Specific Client - FlexNet Publisher

Hello all,

I have a license in a server in my company that is configured like the general manual explans (lmadmin). That license can be used concurrently with whatever PC that is in the same VLAN or have access to the virtual server (via firewall rules). So far we have worked like this, with the inconvenience that whoever that has configured the server address in their FlexSim installation, can get the license as long as he's the first opening the program on a given moment.

My question is if in the tool suggested by FlexSim to allocate licenses (lmadmin, FlexNet Publisher), is there a way of tracking who connects, creating a list of validated users, etc. I don't see anything in the documentation or playing around with the UI of FlexNet.

We are planning to add more concurrent licenses and a proper control is needed within the company.

Thanks in advance for your help.

Software Version:

FlexSim 25.0.2

licensing server client flexnet

· 1

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Joerg Vogel commented · Feb 14 at 02:04 PM

@Joaquín MSV, I had work with LM_PROJECT. It is an attribute inside an opt license file to manage, grant or restrict access to concurrent licenses on a server. Each client create a user variable in windows system calling LM_PROJECT. The value must match with the value in option file.

File name: flexsim.opt

INCLUDEALL PROJECT WISE20112 #grant all features

# grant only some features

INCLUDE dragdropconnect:VERSION=5.1 PROJECT WISE20112
INCLUDE expertfit:VERSION=5.1 PROJECT WISE20112
INCLUDE compile:VERSION=5.1 PROJECT WISE20112

the value is in this example "WISE20112".

VERSION parameter is optional

https://answers.flexsim.com/articles/49019/license-model-client-activatable-aka-standalone.html This link leads you to an article, which includes a link to flexera FlexNet manual.

0 ·

Answer 1 · 2025-02-14T15:04:19Z

Ben Wilson answered Feb 14, '25 Joaquín MSV commented Feb 26, '25

Hi @Joaquín MSV,

As Joerg suggests, an Options file can do what you specify in your title: restrict license allocation by client PC.

If you search this community for "options file" you will find several Q&As that could suggest ideas how to use the options file to accomplish your goal. Here is a good one:

Using the options file on a license server - FlexSim Community

Not every bit of syntax in every Q&A will be good, so cross reference against the actual documentation found at chapter 13. Managing the Options File in the FlexNet Publisher License Administration Guide.

· 7

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Joaquín MSV commented · Feb 25 at 04:10 PM

Hello @Ben Wilson and @Joerg Vogel,

Many thanks for the guidance. Finally following the manual for option file I've been able to use the following structure:

GROUP flexsim_users John Anthony William

INCLUDE_BORROW flexsimlicensecode25.0 GROUP flexsimusers

With this I can set which users can take the license, excluding all others. I still have to investigate on how to use the option MAX_BORROW_HOURS to limit the use of it by user. Do you have any example regarding this? Thanks in advance.

0 ·

Joerg Vogel Joaquín MSV commented · Feb 26 at 07:45 AM

@Joaquín MSV, Borrowing is a feature for a transfer of a license for some time. It is like an installation as a standalone license. The server license must allow such a feature.

You control on a concurrent server the hearbeat (timeout maximum 1 hour). It is a time interval which grants a license. And it must be updated within this interval to be granted further on.

1 ·

Joaquín MSV Joerg Vogel commented · Feb 26 at 08:51 AM

Hello @Joerg Vogel,

I tried the option of only INCLUDE instead of INCLUDE_BORROW, but didn't work. Also I didn't find any info regarding the timeout you coment in the documentation (INCLUDE_BORROW).

I have a concurrent license, which would we the proper way to proceed then? Considering my goal is to have the same concurrent behavior than before (no options applied) but restricting the users.

Thanks in advance.

0 ·

Show more comments

question