Cant login to newly cloned HyperV server

Solution 1:

1. If you exported the VM, why didn't you just import it? The exported VM will include the configuration file with all of the VM settings. Exporting the VM and then attaching the virtual hard drive to a new VM kind of defeats the purpose of exporting it.

2. Make sure the new VM is connected to an external virtual switch and that the external virtual switch is connected to the physical network.

3. Of course the VM has the same computer name. It's an export of the original VM. Exporting the VM doesn't change the identity of the VM. If you want to change the identity of the VM then you need to sysprep it before exporting it or rename the computer after importing the VM.

4. The fact that the VM is getting an APIPA address tells me that it has no access to a DHCP server or that you don't have a DHCP server.

5. Try disconnecting or removing the virtual NIC for the VM and see if you can log on. So long as Windows detects a network connection you won't be able to log on with cached credentials. Disconnecting the VM from the network should resolve that and allow you to then log onto the VM.