Hexagon Geospatial
MENU

Licensing Knowledge Base

Easily license Hexagon Geospatial desktop products using the License Manager .
Showing results for 
Search instead for 
Do you mean 

Geospatial Licensing and Virtual Machines

by psmith on ‎03-06-2019 07:32 AM - edited a week ago (165 Views)

Virtural Machine Requirements

Hexagon Geospatial licensing is based on FlexNet licensing 11.14.0. Supported FlexNet VM (hypervisor) platforms can be found in the release notes for FlexNet Publisher 11.14.0. in the section titled System Requirements, Virtualization Support.  Hexagon Geospatial licensing officially supports only Windows operating systems.

 

Virtual Machines (VM's) must be a supported Windows operating system that offers a static ethernet (MAC) address to avoid breaking trusted storage. Be aware that some virtural hypervisor platforms such as Hyper-V, dynamically assign a different MAC after each reboot.  If using Hyper-V, the Hyper-V Manager (virtmgmt.msc) can be used to avoid a dynamic assignment by altering the settings of the network adapter to provide and use a user defined static physical (MAC) address.

 

Geospatial Licensing detects the presence of the virtual machine and *binds to a combination of elements from both the VM and the physical host which ensures that the license service is not copied in a functional way to a second VM / server. Ultimately this means that you can run a license service on a VM but the licensing trust is bound by both physical and VM elements. It is for this reason that VM high availability system configurations are not supported unless you split your license quantities between each VM.

*Note:  For more information on binding and trusted storage see also see also this article concerning How to Deactivate Activation IDs from Trusted Strorage.

 

Virtural Clones, Snapshots, Checkpoints and Rollbacks

Additionally licenses installed in trusted storage cannot participate in VM clones, snapshots, checkpoints or rollbacks; these VM image and backup actions are NOT supported. You cannot copy a working license service and expect it to work when restored; actions such as cloning or reverting to checkpoint will cause licenses in trusted storage to become untrusted. Prior to creating the clone, you must use Licensing Administrator's, License > Deactivate / Return to return the activation id. Then the same activation id can be used on another system (including a clone or check point) using Licensing Administrator's, License > Activate command.

 

Example workflow:
(a) Use Licensing Administrator's, License > Deactivate / Return to return Activation Id's
(b) Create VM backup / clone, image, etc.
(c) On target VM after restoring the image, use Licensing Administrator's, License > Activate command to reactivate the licenses.

Contributors