Hardware Replacement with VEEAM on Domain

[fred3]

I'm wondering what is the best procedure in this situation. I should be able to figure this out but there are too many moving parts!
- We are using VEEAM to back up entire OS hard drives on some critical domain-joined computers.
- If only the hard drive fails, we seem to be able to replace it and return operation using the VEEAM image. However, if the computer (e.g. mainboard) dies then it's more complicated.
- The local Administrator account is normally disabled.
- The computers all have static/manually-entered network settings.
- We are using LAPS for the local Administrator password.
Initially, my advice was:
- Get the new computer running.
- Install VEEAM.
- Create a new VEEAM boot medium.
- Boot with the new VEEAM boot medium.
- Restore the OS drive from the original VEEAM image.
I had anticipated that this might cause a trust issue but wasn't sure how to best proceed.
So, I'm looking for a better approach.
Any suggestions would be greatly appreciated!

[HannesK]

Hello,
just to clarify... are you using Veeam Backup & Replication for management, or are you using the standalone Windows agent?

However, if the computer (e.g. mainboard) dies then it's more complicated.

Could we get more details on why it's more complicated? Is it about missing drivers, or what is the challenge?

I had anticipated that this might cause a trust issue

theoretically it can happen, depending when the computer password was changed last time. it seems to be a rare case, though. In worst case, once can just re-join the domain.

Best regards,
Hannes