Using vCenter 5.1.0 Build 947673, source ESX host was 4.1.0 build 721871. Hot cloning a Windows 2008 R2 VM with vmware tools
When I select an existing VM (domain joined Windows 2008 R2 box) and hot clone it using vCenter the clone boots up with the singular network adapter not "connected" and not "connect at power on". When the VM is powered on the network interface is still not connected, that is to be expected.
I'm seeing that somewhere when the customization starts (seen via message in tasks and events) that vCenter is connecting the network interface before sysprep has started and before the first reboot of the VM. So what is happening is that the new VM is on the network with the same name as the original VM. The new VM can register itself with DNS and that is screwing up my production VM. After it registers in DNS the VM will reboot and go through the sysprep process as expected.
Anybody seeing this?
Ben