This issue remains under investigation by the Veeam R&D team, and this KB article will be updated as further information becomes available. If you are experiencing this issue, we welcome you to create a support case and mention this KB.
At this time, the following workarounds have been developed:
To work around the hardware changes that occur and cause the generated UUID to change, the Management Agent can be forced to use a specific value using the following registry setting. While the UUID that the Management Agent is forced to use could theoretically be set to any value, Veeam recommends that you use the VM's BIOS UUID.
wmic path win32_computersystemproduct get uuid
An alternate way to prevent this mistracking issue is to manage the VMs through a protection group in Veeam Backup & Replication. Then, add that Veeam Backup & Replication server to Veeam Service Provider Console. This option works because, unlike the VSPC Management Agent that generates a tracking UUID based on various hardware identifiers within the VM, Veeam Backup & Replication only tracks the Veeam Agent for Microsoft Windows deployments based on the VM's BIOS UUID.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case