Windows Server TechCenter >
Windows Server Forums
>
Hyper-V
>
Hyper-v server 2008 r2 RC seems to be missing vmconnect.exe
Hyper-v server 2008 r2 RC seems to be missing vmconnect.exe
- hi,
on the r2 RC (resently released) version of Hyper-v after installation i'm unable to find vmconnect.exe anywhere on the server. Therefore when i create the VM, i can't connect to the console.
I'm not using any remote access methods, this is all done on the bare-metal, using codeplex hyper-v library to create the VM, then i want to connect to the console, but OOP's i can't.
is this something you've seen? am i missing something?
Answers
- Hyper-V Server does not include vmconnect.
(just like not being able to connect a VM console at the console of a XenServer host, or an ESX host)
Yes, this is the VM console connection application, however the windows shell framework is required - it is a component of the Management pack for Hyper-V which is available for Vista SP1 and above and Server 2008 and above.
(this also limits you to not being able ot use vmconnect on a Server Core with Hyper-V installation - Server Full is required)
Brian Ehlert (hopefully you have found this useful)- Marked As Answer byunixdaddy Friday, September 04, 2009 3:57 PM
- No, it would not be that simple.
The equal in XenServer would be installing VNC within the parent partition and then connecting to each VM's VNC console connection.
This requires the supporting components of full VNC within Dom0 - thus adding a bunch of weight for convenience.
Hyper-V is both similar and different - the Windows Shell is missing. And it provides the support framework for the remote desktop client which is what vmconnect uses to remote the console of the virtual machines. (yes, the RDP client 6.1 or higher is required for vmconnect.exe)
In the Hyper-V case the Dom0 is not Linux, but Windows. I think of it as a command line windows framework. It can run windows services, however there is no windows shell - Yes there is a command line shell, but not the shell framework that provides GUI.
This reduces the weight, supporting services, and thus makes the installation small, light and very low on the attack spectrum.
The theory of only add as you require. Very Unix like in the way of thinking.
The way around all of this is to use Server 2008 with the Hyper-V Role. This is a full Server 2008 installation in Dom0, with the management services layer, plus the Hyper-V hypervisor between it and the hardware.
This gives all the bells and whistles - and the trade-off is tons more patches.
Hwever, folks use this scenario all the time for demonstration boxes (laptop hypervisors with full desktop). And I recommend that you have at least one in your larger deployment just for the management console(S) - big S there, not little s.
I hope describing it all in this way helps.
Brian Ehlert (hopefully you have found this useful)- Marked As Answer byunixdaddy Friday, September 04, 2009 4:29 PM
- No, not a dumb question at all.
There is a high number of folks that just don't get that Hyper-V is a full blown hypervisor.
The high level architecture is actually similar (not identical) to XenServer, the concept of a Dom0 and child partitions. they way the vmbus layer works, etc.
However, implementation is totally different.
Hyper-V supports what XenServer refers to as HVM type virtual machines - not PV virtual machines.
Yes, it is paravirtualization architecture but then it diverges.
It is all based of the Remote Server Admin Tools
Win 7:
http://www.microsoft.com/downloads/details.aspx?FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d&displaylang=en
There is an equivalent for Vista SP1, and requires a Hyper-V patch and update if you are running R2.
Brian Ehlert (hopefully you have found this useful)- Marked As Answer byunixdaddy Friday, September 04, 2009 4:55 PM
All Replies
- Hyper-V Server does not include vmconnect.
(just like not being able to connect a VM console at the console of a XenServer host, or an ESX host)
Yes, this is the VM console connection application, however the windows shell framework is required - it is a component of the Management pack for Hyper-V which is available for Vista SP1 and above and Server 2008 and above.
(this also limits you to not being able ot use vmconnect on a Server Core with Hyper-V installation - Server Full is required)
Brian Ehlert (hopefully you have found this useful)- Marked As Answer byunixdaddy Friday, September 04, 2009 3:57 PM
- Hi Brian,
so you can use powershell to create VM's, get details on VM's on hyper-v server 2008 r2 RC. You can even use codeplex hyper-v library i.e. new-vm etc.. to simplify it even further, but you can't connect to the VM console on the system without the management pack (which only works on vista SP1/Server2008 and above). So interactive installations are out of the question without remote access from a vista/server2008? right.
Being from a unix (commandline background) i wanted to do everything on the server (no remote access), but you are right it probably doesn't make sense. I've used Xenserver and i general use the command line to create, but thinking about it i then use XenCenter to get to the console for interactive stuff anyway.
out of interest would it be as simple as copying vmconnect.exe onto the hyper-v server? would that work.
Thanks for your response. - No, it would not be that simple.
The equal in XenServer would be installing VNC within the parent partition and then connecting to each VM's VNC console connection.
This requires the supporting components of full VNC within Dom0 - thus adding a bunch of weight for convenience.
Hyper-V is both similar and different - the Windows Shell is missing. And it provides the support framework for the remote desktop client which is what vmconnect uses to remote the console of the virtual machines. (yes, the RDP client 6.1 or higher is required for vmconnect.exe)
In the Hyper-V case the Dom0 is not Linux, but Windows. I think of it as a command line windows framework. It can run windows services, however there is no windows shell - Yes there is a command line shell, but not the shell framework that provides GUI.
This reduces the weight, supporting services, and thus makes the installation small, light and very low on the attack spectrum.
The theory of only add as you require. Very Unix like in the way of thinking.
The way around all of this is to use Server 2008 with the Hyper-V Role. This is a full Server 2008 installation in Dom0, with the management services layer, plus the Hyper-V hypervisor between it and the hardware.
This gives all the bells and whistles - and the trade-off is tons more patches.
Hwever, folks use this scenario all the time for demonstration boxes (laptop hypervisors with full desktop). And I recommend that you have at least one in your larger deployment just for the management console(S) - big S there, not little s.
I hope describing it all in this way helps.
Brian Ehlert (hopefully you have found this useful)- Marked As Answer byunixdaddy Friday, September 04, 2009 4:29 PM
- hi brian,
that is a top answer to what (after your explanation) was a dumb question. Would a windows 7 client (instead of vista) work?
I've been fairly impressed with hyper-v so far, the only disappointment is the rather small number of guest OS's that it can run (or is supported, is that one and the same thing?). I'm off now to find a spare box/laptop to put vista (windows 7) on.
regards
- No, not a dumb question at all.
There is a high number of folks that just don't get that Hyper-V is a full blown hypervisor.
The high level architecture is actually similar (not identical) to XenServer, the concept of a Dom0 and child partitions. they way the vmbus layer works, etc.
However, implementation is totally different.
Hyper-V supports what XenServer refers to as HVM type virtual machines - not PV virtual machines.
Yes, it is paravirtualization architecture but then it diverges.
It is all based of the Remote Server Admin Tools
Win 7:
http://www.microsoft.com/downloads/details.aspx?FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d&displaylang=en
There is an equivalent for Vista SP1, and requires a Hyper-V patch and update if you are running R2.
Brian Ehlert (hopefully you have found this useful)- Marked As Answer byunixdaddy Friday, September 04, 2009 4:55 PM
- Searching with Bing using " Management Tools for Hyper-V " I find all kinds of links to Vista, the various updates for Service packs1 and 2, x86 vs. x64, etc.
I am checking on the level of R2 compatibility though..
I know a few things changed between 2008 and 2008 R2, but I don't think they affect the MMC as it uses WMI - but I am not positive.
Brian Ehlert (hopefully you have found this useful)
