Mount Image Pro (MIP) is a powerful tool for mounting disk images, but its hardware-based licensing model can cause complications in virtualized environments. This article provides key recommendations and implementation guidance for effectively deploying MIP in virtual machine infrastructure.
It is important to understand how the virtualization environment manages Machine IDs. Specifically, whether the ID remains tied to the VM image or changes when a different host CPU assumes control. This is critical because MIP locks licenses to hardware IDs, which can create activation problems in VMs.
MIP has acknowledged that hardware ID-based licensing causes problems in virtualized settings. In network environments, MIP typically uses a licensing server with a pool of licenses. Machines poll this server for licenses when launching, facilitating license management.
For virtualized environments, using a centralized license server is recommended. This alleviates hardware ID issues and centralizes license management.
Venio suggest designating one of the distributed services servers as the dedicated MIP license manager to streamline licensing in your virtualized infrastructure.
Venio has tested and approved MIP v7.1.2 and v7.2.2 on all Venio 11.x versions. Application support professionals should ensure all distributed services servers run the same approved MIP version and can communicate with the license server.