Aaron, we are using Laserfiche 10 and currently replicate our virtual Laserfiche server at machine level using Double-Take.  We have run into similar situation where the Laserfiche licensing has a mis-match with the machine fingerprint onto which we've replicated the Laserfiche environment.  I would suggest that you are probably experiencing a similar situation.

What we have been working with Laserfiche to do is the best-practice to re-license the server and Laserfiche components in our DR environment.

Please see the links below for some information that may be helpful to you.  The first is our original post regarding the need to run a test DR environment using our replicated Laserfiche server.

https://answers.laserfiche.com/questions/99702/Will-DR-Server-License-changes-Mess-up-Production-License#repliesToMain

The second is the most recent pertaining to our use of DR licensing while keeping production running under our original licenses.

https://answers.laserfiche.com/questions/103103/Can-Production-server-and-DR-Server-run-in-parallel#repliesToMain

The third is one is helpful to describe the hardware fingerprint in DR

https://answers.laserfiche.com/questions/71848/Invalidating-the-Hardware-Finger-Print--Replication-and-Disaster-Recovery#repliesToMain

What we would ultimately like to obtain is a blueprint for handling Laserfiche in a virtual DR environment where the Laserfiche environment is fully replicated from production.  One that allows us to run at least two tests a year and to have a rock solid procedure to put into play during a real incident.