Network settings after migrating from VMware to Hyper-V and AHV to VMware

[NK100251]

Moderator split from post432680.html#p432680

I am doing server migration from VMware to Hyper-V and Nutanix AHV to VMware. Where I found challenge in restoring the network settings which are configured at OS level. Every time we migrate a VM, it doesn’t restore OS level network settings and it is not joined to domain controller causing authentication issues. Every time we need local administrator or cached credentials for login and setting up Network at server level.

It is time consuming.


Is there any alternate way to solve this?

[HannesK]

Hello,
which operating system are we talking about? It sounds like you talk about Windows because of "administrator". But just to be sure.

And which network settings (static IP addresses, anything else)? How many network cards do your VMs have?

Best regards,
Hannes

[NK100251]

Hello HannesK ,

Yes, I am talking about Windows Operating system here and Network settings such as static IP addresses, default gateway, subnet mask and DNS servers.

How many network cards do your VMs have --> Usually we have single NIC attached to each VM

[lienkristian]

Are you sure that the hypervisor understand the card and ID? in vmware is it vmxnet3 card but in hyperV it is virtual adapter? How can the OS know that it sould map the static ip from the vmxnet3 card to the virtual Hyper-V adapter?

[NK100251]

I agree and that is why it is a challenge for us to assign a static IP address & other network settings at OS level.

Is it possible to create a script which during conversion/migration from VMware to Hyper-V & based on VLAN we are selecting assign static IP & other network settings? It will reduce the effort as migrating and assigning network settings for multiple VMs (specially when we are moving our infra to other hypervisor) to a lot.