I was recently testing a replica failover with re-IP scenario and discovered that the replica had booted in DHCP mode. Also noticed on first logon that the server was installing a new hardware device. It seems that the re-IP occurred correctly (per the registry) but the now active network adapter is a "new" one with a new MAC and no networking configuration applied.
This seems to be discussed here: https://www.veeam.com/blog/mac-address- ... apter.html
And a workaround was mentionned for Veeam v5.
This is no small issue, how have others dealt with this situation?
It also has applicable concerns with certain software that uses the MAC address as an identifier for product licensing. Looking at my replicas only the NICs with manual MAC addresses have carried over, all the others have been renumbered. It was my understanding that replicas kept all characteristics of their source VM.