We have had a number of customers asking us whether Intella can run in a Hyper-V virtual machine environment. The short answer is yes, Intella can be run in Hyper-V, but there are some limitations with Hyper-V, which require additional configurations for Intella to work with Hyper-V.
Intella is not as straight forward to get up and running in Hyper-V as it is with other virtual machines such as VMware or VirtualBox. The issue is with the hypervisor not being able to access the USB dongle which we use to license our products. Other virtual machines such as VMware and VirtualBox, have native USB pass-through which allows the client machine (running Intella) to access the license dongle which is plugged into the host machine. Unlike VMware and VirtualBox, Hyper-V cannot pass-through non-disk USB devices. Therefore, the Hyper-V client (running Intella) cannot access the license dongle connected to the host system. If the dongle cannot be accessed, Intella will run in trial mode, or you will get a message saying that a dongle/license cannot be found.
If you are interested, there is some information regarding the reason Hyper-V cannot pass-through non-disk USB devices discussed at this post:
https://www.altaro.com/hyper-v/hyper-v-usb/
Because Hyper-V cannot pass-through non-disk USB devices, the client cannot see or access the dongle. To allow the license dongle to be seen by the Hyper-V client system, the dongle needs to be redirected to the client system. This can be done by purchasing a software solution (e.g., a USB network gate). This allows the dongle, which is plugged into the host system, to be redirected to the client system. To the Hyper-V client, the dongle is connected directly to itself, and Intella can obtain a license from the dongle. More information on USB network gates can be found at these links:
https://www.eltima.com/article/hyper-v-usb-passthrough/
http://www.net-usb.com/hyper-v-usb/
There are also hardware solutions available to help with USB pass-through in Hyper-V. The hardware solutions would presumably be more expensive than software solutions. Note that Thales (the current agent for hasp dongles at this writing) only recommends one device which they have tested. More information regarding this device is at the link below.
Note: Vound cannot support any devices that are not recommended by the hasp dongle agent.
There is also the ability to use RDP to gain access to a dongle connected to a host system. These methods or solutions are discussed in the first link above. You will need to check whether these methods suit your environment, and they will need to be implemented and supported by your IT team. Vound has no experience with the hardware and RDP solutions discussed in the post. You will need to conduct your own research and testing to determine whether these will suit your environment, and work as expected.
Disclaimers
Updated April 2023