Since it sounds like you are referring to a Rio system here, there's a couple of approaches that may work --- you are correct that the HWFP is likely to cause issues on failover if you don't take steps to handle it.
There are several options here:
- If you know in advance which machine will be used for failover set up licensing in advance so that changing machines is easily scripted or handled by our clustering capabilities
- Manually re-license the system in the event of a failover
- Contact your regional manager for alternative licensing options designed to handle VMs with changing fingerprints
Some details on the first two options (which can be combined)
1. Set up licenses in advance
LFDS has a failover clustering feature. The Advanced Directory Server Administration class has some information on how this works and there are detailed steps in KB 1013718.
For other LF applications, you can leverage the unlimited Laserfiche Server and Forms Server installations on Rio --- as long as you don't have any limited assets assigned to your applications (e.g., 1 Forms portal only or named users assigned to repository users).
Essentially, you could license the VM hosted on both Machine A and Machine B, then use a script to move the correct license into place on failover. Both Machine A and Machine B should stay licensed in LFDS.
2. Manual relicensing:
To manually relicense LFDS 10.4, you should be able to renew the master license from within LFDS by clicking "renew", or script the renewal using the activation tool then upload the new license.
You can then edit the application instances, enter/retrieve the new fingerprint for LFS and Forms, then save and download the new licenses.
If you are on version 10.4, LFDS 10.4 can be configured to send messages to Forms 10.4 and LFS 10.4 to relicense themselves instead of downloading and moving the new license files. This message is triggered on master license renew or by clicking on a link in LFDS.