Showing results for 
Show  only  | Search instead for 
Did you mean: 
Level 2

What Hostid should I use for Node-Locked uncounted Licenses on Windows Workstations running Virtual (VM)


We are currently using "FlexNet Publisher 2022 R1 (11.19.0) in our Windows based product (win32) and daemon and I have read the White paper  "Understanding Virtualization Features in FlexNet Publisher" which discusses a lot of options for floating license, but spends very little time on uncounted node locked licenses.  it seems the only relatively secure option for node locked is a Flexid USB dongle which can be passed through the VM. 

A  node-locked uncounted license file using the physical Mac address (lmhostid -ether) will also work, however it is my understanding that most VM software can easily duplicate a virtual mac address such that a license file can be copied and used on many VM installations which effectively defeats the licensing.   

I was hoping TPM or genid which is available on most recent Windows PCs could be used in a node-locked license file, but it seems these options are only available  with counted floating license server software. 

It seems VMUUID is also not an option for Node-locked licenses on Windows . 

Most of our customers don't use VM workstations so we could restrict node-locked licenses to just physical machines and use PHY_ETHER as a hostid.  It would just need to detect whether VM was running and reject the feature request when VM is running and work the same as a MAC address on Windows when VM is not running.   The lmcrypt won’t even encrypt it.

The crypt utility won’t encrypt the file is PHY_ETHER is used on a feature line.   Future license file format

E.g.         The TPM license feature will encrypt, but the software built with 11.19.0 will give a bad format/inconsistent license file format error message .
                Maybe there’s a build setting we’re missing to enable this one.

FEATURE FD vendor 30.1 03-dec-2025 uncounted 122940EB9F5D \

The following feature won’t even encrypt.  Lmcrypt utility gives a - Future license file format error.

FEATURE FA vendor 30.1 03-dec-2025 uncounted 2CA39B3425C4 \
                HOSTID=b88584b1081f SIGN=26B5F42ABF24

FEATURE FB vendor 30.1 03-dec-2025 uncounted 4EB1B94423F8 \
                HOSTID=PHY_ETHER=b88584b1081f  SIGN=2E1FF784EEF8

FEATURE FC vendor 30.1 03-dec-2025 uncounted 4EB1B94423F8 \
                PHY_ETHER=b88584b1081f  SIGN=2E1FF784EEF8

FEATURE FE vendor 30.1 03-dec-2025 uncounted 122940EB9F5D \
                HOSTID=VM_UUID=CDA82842-9F3E-0C4D-DF9E-7B8D6B537883  SIGN=B2FBABAA9DBE

FEATURE FF vendor 30.1 03-dec-2025 uncounted 122940EB9F5D \
                VM_UUID=CDA82842-9F3E-0C4D-DF9E-7B8D6B537883    SIGN=B2FBABAA9DBE

Am I missing something?  Is there some hostid that can be used for node-locked licenses that is relatively secure against VM replication besides the Flexid USB dongles?

I would appreciate any suggestions or additional insight.

0 Kudos
1 Reply
Revenera Moderator Revenera Moderator
Revenera Moderator

Hi @MikeFlexQ  ,

Certificate based licensing comes with it's own limitations. Yes , VM MAC ID can be easily replicated so below are your options :

1. Use Trusted storage based licensing 

2. In license file based you can go for composite hostid (A composite hostid combines hostids together to provide a more secure hostid.)

3. You can consider vendor defined hostid as well .

0 Kudos