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 be set to any value, Veeam recommends that you use the VM's BIOS UUID.
- Determine the current BIOS UUID of the VM where Veeam Agent is installed.
Run the following PowerShell command from within the VM:
wmic path win32_computersystemproduct get uuid
- Create the following Registry Value on that same VM
Key Location: HKLM\SOFTWARE\Veeam\VAC\Agent\
Value Name: UUID
Value Type: String Value (REG_SZ)
Value Data: <current_bios_uuid>
Option 2: Manage the VMs through aVeeam Backup & Replication server
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 the Veeam Service Provider Console. This option works because, unlike the VSPC Management Agent, which generates a tracking UUID based on various hardware identifiers within the VM, Veeam Backup & Replication only tracks the Veeam Agent deployments based on the BIOS UUID.