When Hyper-V on Server Core actually sucks

14 thoughts on “When Hyper-V on Server Core actually sucks”

1. You need help! I have installed Hyper-V on core with great results. Try this link http://www.microsoft.com/downloads/details.aspx?FamilyID=518d870c-fa3e-4f6a-97f5-acaf31de6dce&DisplayLang=en

2. Vista SP1 plus the management pack download. I suppose if MMC was installable on server core you’d think it was less secure? The purpose of server core, as far as I understand it is to increase security rather than be just cool. From what I’ve seen on the blogs it looks like you can use WMI locally to manage hyper-v. Otherwise, just using Vista SP1 with MMC & hyper-v tools sounds like a good idea to me personally, and it will keep your server core installation nice and ‘thin’. 🙂

3. Yeah I know I can do it from a Vista PC, but I don’t want to have to use another machine to set it up. Perhaps a live CD would be a good idea.

4. Pingback: The things that are better left unspoken : Handling Server Core Roles and Features

5. Hyper-V would be nice if you could use the current System Center Virtual Machine Manager 2007 to control it. I mean wow Microsoft you out date a expensive piece of software in under a year.

6. Hyper-V installation and management SUCKS…big time.

7. Yes Hyper-v Core SUCKS, I recently installed hyper-v core, and after several hours of deployment download several patches, useless microsoft documentation (at first place those documentation said “go to http://www.microsoft.com/hyper-v and download the hyper-v Management console for Microsoft windows vista sp1, reboot and you can acces it” well that’s a compleate LIE), and reading the “virtual PC Guy’s” (http://blogs.msdn.com/virtual_pc_guy) and the Jhon Howard blog (http://blogs.technet.com/jhoward/archive/2008/03/28/part-1-hyper-v-remote-management-you-do-not-have-the-requested-permission-to-complete-this-task-contact-the-administrator-of-the-authorization-policy-for-the-computer-computername.aspx), and runned his script to allow remotelly administrate the Virtual Machines (that script rocks!, but useless at the end), and after redo all the procedure manually, I can certainly access to the Hyper-v MMC.

   Can create, modify and delete without problems but if i start a virtual machine, I cannot connet to it!, reviewed all the Documentation, event logs and no error/warning/info is reported.

   Cannot paste the image of the screen but thanks to the less usefull, windows vista trick
   I post the text version of this screen.

   [Window Title]
   Conexión a máquina virtual

   [Main Instruction]
   No se puede conectar a la máquina virtual. Vuelva a intentar la conexión. Si el problema persiste, póngase en contacto con el administrador del sistema.

   ¿Desea intentar conectar de nuevo?

   [Conectar] [Salir]

   (sorry it’s in spanish and says

   [Window Title]
   Connection to virtual machine

   [Main Instruction]
   Is not possible to connect to the virtual machine, if the problem persist, contact to your system administrator.

   Do you want to try again?

   [Connect] [Exit]
   ”

   Hyper-v Sucks

8. I think Hyper-V Server is awesome – been using it for months, there were some nic and video driver issues at first but no more. I have it running a desktop as a test but worked without issue so I moved it to production – maybe the best thing MS has done. I’m running the beta R2, it is also great. As far as managing goes, mcc does everything some hardware and there are countless sites with commandline info.

9. Similarly, hyper-v server is a un-usable product(or call it crap) out of the box. It requires you to search around and follow N-steps instructions (where N > 10) for how to configure and use it. My guess is that the team@Microsoft releases hyper-v server purely just for the release party. If there is a guy responsible for the usability of hyper-v server, he should be fired.

10. gosh but you guys can moan? get your head out your armpit,
    read up, study, before you start running software, and THEN give
    put some effort into it. you get paid the big bucks because the
    assumption is that you go to the trouble of learning the concepts,
    management tools, and functionality – as well as limitations of a
    package before trying to make it do what it wasn’t designed to
    do… or worse yet, trying to get it to do your job for you!!
    possibly – you should be fired. hyper-v rocks, google is my friend,
    and yeah – i’m not a paper mcitp.

11. hyper-v sucks regardless of whether its on core or not.
    never been able to import a vm from another hyper-v server.. so
    what’s the point of export then, if you cannot import… SCVMM is
    nice, unless you have perimeter networks, where every time you want
    to do something useful it says “can’t to that – it’s on a perimeter
    network”. SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE
    SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE
    SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE
    SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE
    SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE
    SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE
    SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE SHITE
    SHITE SHITE

12. Hyper-V is garbage. Guest support is garbage. Performance is garbage. Its a garbage product.

13. I went through all John Howard and Virtual Guy advice and got my Server 2008 Hyper-v core running fine but it did take a bunch of trial and error and when I wiped it to replace it with Server 2008 R2 Hyper-V core even with my notes it took some trial on error.

    The good news is the free 5Nine Hyper-V manager makes the above stuff unnecessary. You just install it on the host and you’ve got a nice gui for creating and modifying VM’s.

14. Good news! ESXi is free, easier to use, and doesn’t suck.

    If you take backup into consideration, ESX Essentials is freer than Hyper-V.

    Stop using a substandard product, there is absolutely no reason for it.

Comments are closed.