When a VM gets cloned: detecting duplicate activations in node-locked licensing

A machine fingerprint identifies a machine — and a cloned VM is, by construction, the same machine twice. Snapshot-restore, golden images and autoscaled instances all reproduce the exact hardware and OS attributes a node-lock hashes, so two running copies present one identical fingerprint and node-locking cannot tell them apart. The fix is not a better fingerprint; it is activation identity the server owns plus a per-run instance nonce the client cannot clone meaningfully, so two copies of one activation reveal themselves the moment they both phone home. This post reads the SDK and the server policy for exactly that: why the fingerprint is defeated, how an activation record and a runtime instance id separate a legitimate migration from a live clone, and how Keyright decides newest-wins versus flag-and-hold without locking out a customer who simply moved.