Somehow or other, when I built our Windows Server 2008 lab Hyper-V server last year, both of the onboard NIC’s ended up with identical names. I found a fix but it’s messy and I really didn’t want to risk the lab machine – it’s used quite a bit and downtime is bad.
This issue cause a problem for VMM 2008. When it would do a refresh the VMM service would crash. I logged this with PSS but their solution was to rebuild the host. Eek!
I’ve just deployed an agent from my new lab server which is running VMM 2008 R2 on Windows Server 2008 R2 with Hyper-V. It detects and notifies me about the NIC issue but it doesn’t crash. I’m now using the VMM 2008 R2 instance to migrate the VM’s over to the new lab Hyper-V server.
Note: they’re running different versions of Windows Server/Hyper-V so the VM must be powered down to migrate it. So no quick storage migration here.