Issue: network adapter can't ping in Win2012 VM when ESXi5.1 change Hardware
Description:
Win2012 can't be Ping when ESXi5.1 host hardware changed
Environment:
1 Host: ESXi 5.1.0 build in 1483097
2 VM: windows 2012R2 evaluation version with Hyper-v feature
3 Host hardware changed because hardware issue, motherboard and CPU changed, include network adapter in Motherboard (non professional server)
program:
network adapter changed or ESXi version updated, the VM Win2012R2 can't be visited in RDP.
Solution:
1 visit vm win2012R2 in VSphere Client 5.1, Remote Desktop can't be visited because network lost function.
2 remove Win2012R2 Hyper-V feature, restart, network resume.
Note:
Hyper-V in a VM just test operation and configuration, can't be run to support a real VM.
Other test Win2012R2 VM without Hyper-v are well.
Win2012 can't be Ping when ESXi5.1 host hardware changed
Environment:
1 Host: ESXi 5.1.0 build in 1483097
2 VM: windows 2012R2 evaluation version with Hyper-v feature
3 Host hardware changed because hardware issue, motherboard and CPU changed, include network adapter in Motherboard (non professional server)
program:
network adapter changed or ESXi version updated, the VM Win2012R2 can't be visited in RDP.
Solution:
1 visit vm win2012R2 in VSphere Client 5.1, Remote Desktop can't be visited because network lost function.
2 remove Win2012R2 Hyper-V feature, restart, network resume.
Note:
Hyper-V in a VM just test operation and configuration, can't be run to support a real VM.
Other test Win2012R2 VM without Hyper-v are well.
