topic Re: opt file using wildcard in Installation & Licensing Forum

opt file using wildcard

Anonymous — Thu, 31 Mar 2016 07:08:20 GMT

Hi,

If got a question regarding wildcards in opt-files (adskflex.opt).

I found some websites telling that wildcards are possible for subnet IP like 192.168.0.* but is this also working for computer names e.g. PC12* ?

Does anyone have experience using wildcards in opt-files?

Best regards,

Rene

Re: opt file using wildcard

Mark.Lancaster — Thu, 31 Mar 2016 11:01:50 GMT

ReneHoefer

Its been a while but I'm thinking the wild card is only possible on IP Address.. But not 100% sure.. I'm tagging @Darin.Green and @TravisNave who have more experience with option files... Hopefully they can give you a solid answer.

Re: opt file using wildcard

TravisNave — Thu, 31 Mar 2016 12:23:36 GMT

Unfortunately no. Wildcards only work for the IP address. I can understand the pain of having to add a bunch of items to a group. But you can probably export your computer list from the AD server and just copy all of the PC12* you need that way. That's what I'd do.

Re: opt file using wildcard

Darin.Green — Thu, 31 Mar 2016 13:54:03 GMT

@Anonymous Welcome to the community!

A better solution would be to use the LM_PROJECT system variable also known as project association. Use the following link as a guide for implimenting:

Defining Project Association

With this solution, you'll only need to create the LM_PROJECT system variable and provide a name for this project. Once this is done on everyone's machine, you need to add the following to your Options file:

Example:

GROUPCASEINSENSITIVE ON

RESERVE 5 85788BDSADV_F:SIGN=SIGN="0CC2 E5D3 B44B 325D 9045 \
769B 7529 7D1C E2E5 96D6 3061 F6FC 5BFD FFAA BB60 058D 9A4E \
A235 EC00 599C 154F 15E1 3D35 B806 836C 008E 9F8B E0F7 CAF3 \
6165" PROJECT ProjectValue

Re: opt file using wildcard

Anonymous — Thu, 31 Mar 2016 19:12:19 GMT

Thank you all for your sugestions and fast responses.

Cheers,

Rene

Re: opt file using wildcard

rkmcswain — Wed, 18 Aug 2021 19:05:26 GMT

@TravisNave wrote:
Unfortunately no. Wildcards only work for the IP address.

Hey @TravisNave - so to confirm, if you were doing something like setting the MAX_BORROW_HOURS, you'd need a separate line for each product code....

MAX_BORROW_HOURS 87224ACD_2020_0F 336

MAX_BORROW_HOURS 87084ACD_2019_0F 336

MAX_BORROW_HOURS 86830ACD_2018_0F 336

and so on?

MAX_BORROW_HOURS * 336

Will not work, right?

Re: opt file using wildcard

TravisNave — Wed, 18 Aug 2021 19:15:17 GMT

Correct. The options file will not recognize a wildcard for this -- it has to be a matching feature code. And if there are duplicate values for the same feature, the last one will supersede the others. Once implemented and reread in, the debug log file should verify that the option has been activated.

Re: opt file using wildcard

rkmcswain — Wed, 18 Aug 2021 19:44:48 GMT

Thanks @TravisNave - 18 more months and we won't have to worry about all this madness any longer! LMTOOLS has been such a hassle for the past 3 decades....

Re: opt file using wildcard

TravisNave — Wed, 18 Aug 2021 19:52:41 GMT

Hahaha! I am such an expert in it though, what am I supposed to do now? 😅

Re: opt file using wildcard

rkmcswain — Wed, 18 Aug 2021 19:55:33 GMT

Doesn't ESRI and several others still use it?

Re: opt file using wildcard

TravisNave — Wed, 18 Aug 2021 19:59:00 GMT

Yes, many other clients still do. So I guess I will be fine.