Problems with SW license in virtualized servers with Citect 2018

Hi Ana ,

Can you share a little more details about your Virtualization infrastructure? Are you running on VMWare ESXi or Hyper-V? What version?

There have been some changes within the FLM software since Citect 7.40 to now. These changes have included security fixes as well as making it more difficult to defeat license protection in virtualized environments. Unfortunately this has made the license more limited and restrictive in how you can manage your VMs.

The more recent versions of FLM have added protection, where several unique machine numbers (UMN) are bound to the license. If any of these UMN changes within the VM, the license becomes untrusted.

The three UMNs are:
UMN2 is derived directly from the MAC address
UMN3 VMWare: uuid.bios as defined in vmx file
UMN5 is derived from Microsoft Generation ID

Actions that will cause the Microsoft Generation ID (UMN5) to change include:
The virtual machine starts from a checkpoint.
The same checkpoint is applied multiple times.
The virtual machine is restored from a backup.
The virtual machine is migrated by using System Center 2012 - VMM (Export and Import).
The virtual machine is imported.

Actions that will not cause the Generation ID (UMN5) to change include:
The virtual machine is live-migrated.
The virtual machine is paused or resumed.
The virtual machine is restarted.
The Hyper-V host is restarted

Have a look at this whitepaper from Flexera for further details and scenarios:
https://community.flexera.com/xtqzp85664/attachments/xtqzp85664/FNP-Knowledge/375/1/FNP_WP%20Virtualization.pdf

I recommend you get in contact with AVEVA Support to go through the details of your exact scenario. There may be some solution they can share with you.

Kind regards
Olivier

Hi Ana ,

Can you share a little more details about your Virtualization infrastructure? Are you running on VMWare ESXi or Hyper-V? What version?

There have been some changes within the FLM software since Citect 7.40 to now. These changes have included security fixes as well as making it more difficult to defeat license protection in virtualized environments. Unfortunately this has made the license more limited and restrictive in how you can manage your VMs.

The more recent versions of FLM have added protection, where several unique machine numbers (UMN) are bound to the license. If any of these UMN changes within the VM, the license becomes untrusted.

The three UMNs are:
UMN2 is derived directly from the MAC address
UMN3 VMWare: uuid.bios as defined in vmx file
UMN5 is derived from Microsoft Generation ID

Actions that will cause the Microsoft Generation ID (UMN5) to change include:
The virtual machine starts from a checkpoint.
The same checkpoint is applied multiple times.
The virtual machine is restored from a backup.
The virtual machine is migrated by using System Center 2012 - VMM (Export and Import).
The virtual machine is imported.

Actions that will not cause the Generation ID (UMN5) to change include:
The virtual machine is live-migrated.
The virtual machine is paused or resumed.
The virtual machine is restarted.
The Hyper-V host is restarted

Have a look at this whitepaper from Flexera for further details and scenarios:
https://community.flexera.com/xtqzp85664/attachments/xtqzp85664/FNP-Knowledge/375/1/FNP_WP%20Virtualization.pdf

I recommend you get in contact with AVEVA Support to go through the details of your exact scenario. There may be some solution they can share with you.

Kind regards
Olivier