Remote Management of Virtual Machines in SCVMM 2008
I installed SCVMM on a machine that already had Hyper-V running and about 10 VM created on it. I then installed SCVMM and added the local machine as a host. This allowed SCVMM to find the machines that were already installed on the server.
I then installed the SCVMM management console on a WinXP SP2 machine on the network. When I tried to connect from the WinXP machine I get the error:
"Virtual Machine Manager fialed to connect to the virtual machine because the host name () could not be resolved by the Domain Name System"
The virtual machine I'm trying to connect to is connected to a private network, so it's not directly accessible to the external network.
Does a virtual machine need to be connected to an external virtual network to support remote management?
Thanks!
Tom
Answers
Hi Tom,
When connecting to a Hyper-V virtual machine, the vm does not need to be connected to a network if CredSSP is available on the client OS where you are running the administrative console. In your case, with XP SP2, CredSSP is not available. If you upgrade to XP SP3 and enable CredSSP (and then reboot your client ) then it will connect without issue. After you install XP SP3, to enable CredSSP refer to this document http://support.microsoft.com/kb/951608.
On the high level, the way this works for hyper-v vms is: if your client that is running the administrative console is
Vista SP1+,
Windows 2008
XP SP3+
then CredSSp is available and you can connect to the VM directly through the Host, and there is no requirement that the VM be fully booted up, or on the network or any of that.
If your client is running.
Vista without SP1,
Xp SP2 or lower.
Windows 2003
Then it is not possible to connect to hyper-v via the host, and VMM falls back to using a traditional Remote Desktop connection directly to the guest vm os. In this scenario it requires that.
1) The guest vm OS has integration components installed ( to get the machine name to connect to )
2) The guest vm OS is connected to a network that the client is connected to.
3) The guest vm OS is booted up
4) Remote Desktop is enabled in the guest OS.
In your case upgrading to XP SP3 and enabling CredSSP will definitely be the easiest. Alternatively you can use another client that is CredSSP capable.
-James
All Replies
Hi Tom,
When connecting to a Hyper-V virtual machine, the vm does not need to be connected to a network if CredSSP is available on the client OS where you are running the administrative console. In your case, with XP SP2, CredSSP is not available. If you upgrade to XP SP3 and enable CredSSP (and then reboot your client ) then it will connect without issue. After you install XP SP3, to enable CredSSP refer to this document http://support.microsoft.com/kb/951608.
On the high level, the way this works for hyper-v vms is: if your client that is running the administrative console is
Vista SP1+,
Windows 2008
XP SP3+
then CredSSp is available and you can connect to the VM directly through the Host, and there is no requirement that the VM be fully booted up, or on the network or any of that.
If your client is running.
Vista without SP1,
Xp SP2 or lower.
Windows 2003
Then it is not possible to connect to hyper-v via the host, and VMM falls back to using a traditional Remote Desktop connection directly to the guest vm os. In this scenario it requires that.
1) The guest vm OS has integration components installed ( to get the machine name to connect to )
2) The guest vm OS is connected to a network that the client is connected to.
3) The guest vm OS is booted up
4) Remote Desktop is enabled in the guest OS.
In your case upgrading to XP SP3 and enabling CredSSP will definitely be the easiest. Alternatively you can use another client that is CredSSP capable.
-James
Hi James,
Thank you very much! That was a quick response and a definitive one as well.
Looks like you've provided me with a compelling reason to install XP SP3
Thanks!
Tom
