Bare Metal restore - client ID Conflict

[KarmaKuma]

When doing a Bare Metal restore to different hardware, machine/client ID conflicts in Veeam seem to arise since Veeam uses the BIOS uuid as its internal client ID. How do you guys handle Bare Metal restore scenarios to different machines/hardware (with inherent BIOS uuid change) in general, and to make things a little more complex, with AD joined workstations/PCs?

My focus is not about differing drivers etc., purely about the BIOS uuid and Veeam client ID challenges...

We do not want to lose Backup-points/history of the original machine, optimally the machine keeps the same machine/AD-name...

In really "worst case scenarios", "machine z" has been in Veeam at a certain point in time and was then put to stock when not used anymore. Now it is being pulled from stock as Bare Metal restore target for backup of "machine y". This is kind of a really bad situation with Veeam...

[edh]

I have done hundreds of Bare Metal recovery in the last years , multi vendor and never got a BIOS UUID problem. Will be transpared, just an example. Your motherboard could be broken, HP/Dell guy come and change, UUIDs are new but servers boots. Anyway after a full baremetal restore, next backup will be full due hardware layer change. If you dont wanna loose old points my recomendation is create a new policy with the new machine and disable the old one. If you delete policy and backups are managed by VBR, backups of this machine will be moved to Backups -> Disk (Orhpaned) , meaning backups stored without policy.