PLEASE READ CAREFULLY BEFORE RESPONDING!
I have a bunch of Windows 2008 R2 (with SP1) virtual machines on VMWare VSphere 5 hosts. These VMs were originally created with E1000 virtual NICs, and later changed to VMXNET3 NICs.
When I clone one of these VMs
- The Windows OS sees the NIC as a new adapter, even though the virtual hardware is identitical. So I have to set the TCP/IP config.
- After I set the TCP/IP config, networking is working (e.g. I can PING www.google.com
- When I restart the computer (or just disable/enabled the network adapter), several wierd things happen:
- Networking stops working
- IPCONFIG shows the network adapater has an autoconfig address (169....).
- The GUI for setting TCP/IP settings shows the expected IP and netmask, but the gateway is blank.
- Trying to correct the gateway in the GUI seems to have no effect.
- I find I can then get networking going againg using the NETSH INT IP SET command instead of the GUI...but when I disable/enable (or restart), the config is lost again.
The same thing happens if I simply try to change the network adapter (remove the VMXNET3 adapter, add an E1000 adapter) of a VM without cloning.
The same thing happens if I try running Sysprep before cloning.
I have found many articles describing similar problems. Some people seem to have been able to resolve this by fiddling with registry entries. I have tried NETSH INT IP RESET, which is supposed to clear our the IP config completely. That does not help.
Having to reset the IP config on the VMXNET3 adapter after cloning is not a big issue in itself. This is actually documented in http://support.microsoft.com/kb/2526142
. There is supposed to be a hotfix
, but when I try to apply that I get "not applicable". I assume the hotfix was superceded by SP1 for Win2008 R2.
I have spend DAYS on this. Anybody know that is going on??