Activation failure after MAC address change

One of our users has a virtual network interface which has a random local MAC address created upon reboot. This user also started reporting failures in activation whenever they reboot, and this symptom only started to appear after the virtual interface was added.

Is it fair to assume that this false-negative in license detection is caused by the fingerprinting which has been referred to in other forum posts? Will this particular situation be addressed in v4.0?

Thanks!

"Will this particular situation be addressed in v4.0?"

Yes, presuming they have a real network adapter that does not change. If that VM adapter is the primary network adapter, and it's being randomly generated, then the solution now (and forever) is to use TurboFloat. That's one of the things TurboFloat was designed to handle: Virtual Machines with "shifting" or ever-changing hardware.

See: http://wyday.com/limelm/help/vm-hypervisor-licensing/