Hello @ThompsG
Thanks for the reply.
So if EVC mode hasn't been changed on the cluster, vmotion has been performed successfully in the past month, and the 3 hosts have the same CPU and models (BL460c G9) what is the trigger? a powered on vmotion in isolation isn't enough to cause a change in CPUID as I've observed this happening without issue, but perhaps a cold vmotion is enough to trigger it? I will have to test in the lab.
We are working with the manufacturer to get a long term fix to this, but in short it collects multiple parameters such as CPUID, BIOS serial, Physical RAM and MAC address to generate a machine key that is provided to the manufacturer for activation. A very brutal process that doesn't work well at all in a virtual environment. The manufacturer says in their spec sheet that they support VMWare so this looks like a bug but I'd like to avoid triggering a license invalidation whilst the bug is resolved.