P2V Windows Server - Issues with the NICs
Hi,
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_DEV
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_DEV
Another thing, make sure VMware tools are installed on your new guest VM. Once they are I would recommend changing NIC type to vmxnet3, and reconfigure networking. Last thing - Make sure the system time is set correctly on both your vmware host machine and on your guest machine. Active Directory doesn't tolerate much drift before it will deny login to a domain.
Good Luck
Good Luck
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Great list BestWay - mind if I use it?
Hi
Of course not friend
I thinking right a article here in EE with all my P2V issues, but unfortunately i did have the time yet. I found many issue, for different types of SO(Windows) and create some tasks to corrected. Even for Linux RH
Jail
Of course not friend
I thinking right a article here in EE with all my P2V issues, but unfortunately i did have the time yet. I found many issue, for different types of SO(Windows) and create some tasks to corrected. Even for Linux RH
Jail
An article would be a great addition. My P2V stuff is not done often, my preferred approach is to just build a new VM and reinstall all the applications - my thought is that should be cleaner than bringing along any "issues" from the physical environment. Of courst that is not always possible, someone has something running something that we no longer can find the install materials for (yet it is so important we can't do without it) - you know what I mean. That is where P2V comes in for me.
ASKER
Hi Jail,
Thanks for your recommendations. I think I understand everything so far however do you mind sharing some tips on how to do point 8?
8º In safe mode, remove all phantom hardware(i have a script for this), and uninstall all Software for Hardware Management(like RAID, Storage agents etc)
Thank you!
Thanks for your recommendations. I think I understand everything so far however do you mind sharing some tips on how to do point 8?
8º In safe mode, remove all phantom hardware(i have a script for this), and uninstall all Software for Hardware Management(like RAID, Storage agents etc)
Thank you!
ASKER
Also have you ever experienced that even though the NIC has network connectivity the P2V VM can't log on to the domain?
I have found that difficulty logging on to the domain often comes become the guest's time is out of whack with the domain time. Check both the host esx and the guest for the correct time.
I have also experienced where I had to remove the machine from the domain then re-add it...make sure you know the local adminsitrator password before doing that!
I have also experienced where I had to remove the machine from the domain then re-add it...make sure you know the local adminsitrator password before doing that!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi
For that login problem, logon with local account, fix the profile and try again
In all the Windows servers thatIi have P2V I did not need to remove, and re-add it to the domain. If P2V is than with the right way we dont not need to do this
Jail
For that login problem, logon with local account, fix the profile and try again
In all the Windows servers thatIi have P2V I did not need to remove, and re-add it to the domain. If P2V is than with the right way we dont not need to do this
Jail
Hi
@llarava did you correct your problem?
Jail
@llarava did you correct your problem?
Jail
ASKER
Yes, I did. This time I remove the teaming once the server was P2V then rebooted the VM and everything worked as expected.
Thanks for you help.
Thanks for you help.
Hi
OK glade to help
JailBreak
OK glade to help
JailBreak
VMware I'd imagine is much the same. Create a new VM on the host and play with that to ensure you can connect to the LAN and play with settings on that before virtualizing anything in production. OS install should take < 1 hour and it's easier to break a test system ;)