The referenced link states the reason for this behavior is "VMs are tracked by their unique IDs and migrating VMs within a cluster allows to preserve those ID's. However registering a VM on a standalone host assigns a new ID to it."
I ran some tests with two Server 2012 R2 hosts to test this and it appeared to me that the IDs were not changing. There were 3 things I checked before and after the live migration.
1. Name of the machine's configuration XML file. This is in the format of <GUID>.xml. The file name did not change after the move.
2. The contents of the machine's configuration XML file from each host before and after the move. The only GUIDs I found that changed were "HostResource" and "SwitchName".
3. The ID produced from the PowerShell script available at http://stealthpuppy.com/retrieving-a-vm ... m-hyper-v/
. The ID returned by the script was the same before and after the move.
Perhaps older versions of Hyper-V did change the ID when migrated between standalone hosts and that has since been fixed. (I do not have hosts running older versions of Windows to test with.) To me it looks like it is technically possible for Veeam to track moved VMs between standalone hosts, at least with Server 2012 R2.