Customer has Laserfiche 9 RIO & wants to host the server on Vmware V-motion. What do we need to take care to avoid any licensing issues
When performing VMWare V-Motion, the actual Virtual Machine being moved doesn't see any hardware changes. All of the virtual hardware presented to it retain the same identity. Since the LF Hardware Fingerprint is based off of these hardware identities, you shouldn't have any problem migrating a virtual server over V-Motion. The only time that you would need to worry about your license would be if the hardware visible to the server machine changes.
Is this the reason that after move, the Host Fingerprint (shown under DB properties of License Manager) are different then the Hardware Fingerprints (gathered using show hardware fingerprints utility) BUT the license Manager is working all fine and none of the servers registered to this LF LM are complaining?
Does this make sense?
Edit: Added a screenshot.
Also, we have now moved the blade into a newer blade chassis (so new backplane) and now has 2 additional mezz NIC cards to split the VM/LAN/iSCSI traffic apart. So this has of-course changed the Hardware Fingerprints for the VM and it is obviously still different from the 'Host Fingerprint' as mentioned in LF LM. But all seems working fine as well.
The Laserfiche Server was restarted after the above exercise and we can't see any errors in Event Logs for LF LM SErver and LF App Server.
Any idea as what's really happening?
Further findings, the MAC address for the Windows is hardcoded and I believe this is the reason LF LM is not complaining as the MAC address never changes, even after the move.
Is that correct?
The algorithm was intended to accommodate one or two small changes to allow for minor hardware upgrades without invalidating your license. If you make additional hardware changes, you will likely run into issues at some point and need to deactivate and reactivate.