We are trying to P2V a server (w2k3). The P2V works fine and the server gets created however when we turn off the physical server the VM doesn't seem to take over the network.
We tried to switch the servers but the VM didn't seem to get connected to the network. We end up removing all the virtual NICs and we created a new one which was able to get a network connection, however once we configured TCP/IP and tried to logon to the network we got a message saying that the server couldn't logon to the domain. DNS and connection to the DCs were sucessfully verified.
We are now trying to repeat the same process since the previous attemp was a failure.
We have done some reaserch and we have found that the Physical Server had teaming setup and that has to be removed on the VM side. We have removed the teaming on the P2Ved server once the server has been rebooted the reboot has cleared the Virtual teamed NIC and has left the a single virtual NIC with the correct IP configured.
Also the VMWare tools have been installed.
I haven't been able to switch the servers yet (phyisical/virtual) since I haven't get a window yet but I would like to know if someone has any other suggestions in regards the network connections?
Once these setting is done power on the machine and login with local admin and password. If there is any NIC teaming exist then break the team. The reason for this is NIC driver get migrated as part of P2V and if we uninstall driver without breaking this team than it may land up in additional troubleshooting.
These NIC driver are hidden when it is P2Ved. To do this go to a CMD prompt and type SET DEVMGR_SHOW_NONPRESENT_DEVICES=1 and then DEVMGMT.MSC and then select Show Hidden Devices. Delete any old grayed out hardware.