More then once I have run into the problem of not knowing on witch physical server a Hyper-V hosted server is running. Getting RDP access to a clients system and then needing help from SAN or Network teams, there first question: "What physical machine is the host running on?". Without access to the physical servers or System Manager it's hard to know. You could probably figure it out from assigned IP-addresses but there is a quicker way if the Hyper-V Integration Services are installed.
This registry key: HKLM\SOFTWARE\Microsoft\Virtual Machine\Guest\Parameters
It contains the following information:
- And also additional info about server version etc.
You can also run this from the CMD:
reg query "HKLM\SOFTWARE\Microsoft\Virtual Machine\Guest\Parameters" /v PhysicalHostName
If you have remote access:
reg query "\\<machine>\HKLM\SOFTWARE\Microsoft\Virtual Machine\Guest\Parameters" /v PhysicalHostName
Ofcourse you can replace the "PhysicalHostName" with any of the above values!
Received this error when I was working with my Hyper-V servers. It's easy to solve but the hos machine has to be rebooted and therefore all the VM machines will be unavailable for a while during the reboot.
Cannot connect to the virtual machine because the authentication certificate is expired or invalid. Would you like to try connecting again?
This error is due to the VMMS certificate expiring. So just run the KB fix and the issue will be gone!
More info: http://support.microsoft.com/kb/967902
Direct download of the fix: http://www.microsoft.com/downloads/details.aspx?FamilyID=289c831c-9142-4c00-bacd-6c1924ff0ecc