Legacy network adapter - run as vm #05227996
I have a partner who is testing Run a VM and its success. however, when he uses run as VM on the same host where the VM were there the network adaptor would be normal, however, when he uses run as VM on a different host the network adaptor would be on a legacy network adapter could anyone please suggest if this is normal behavior?
I have checked the case query in MM training ground chat, I was suggested to check here.
Partner quote " Hi there, We did a test restore this weekend for a customer - username is "nvsbuadmin" - 3 virtual machines to a different hyper-v host. Same OS - Windows Server 2019. When we do run as vm on the original host, it creates the vm, with a normal network adapter. When we do run as vm on a different host (Agent installed obviously) it creates the vm but with a legacy network adapter This limits the connection to 100mbs and requires that the vm be reconfigured by deleting the legacy network adapter and adding a new normal hyper-v network adapter. "