Hyper-V with Server Core - too hard for VMware to use?

  • Article

There was an video posted recently showing the difference between setting up Hyper-V with Windows Server Core, and setting up ESX3i.  Mike DiPetrillo posted an interesting comment to the effect that the commands that were entered were net new for Windows Server 2008 Core.

 

I watched the first video and counted one net new command line for Windows Server 2008 (let alone core).  The command sequence is something like:
netdom (around since Windows NT 4.0)
shutdown (around since Windows NT 4.0)
netsh (around since Windows 2003)
netdom (see above)
netsh (see above)
ocsetup (Only net new command)

The second video shows setting up the ISCSI storage and I counted no net new command line tools there:
iscsicli (has been available as part of the ISCSI initiator for a while now - it's available for 2K, XP, 2003 - this is first time the iscsi initiator is in the OS) - it is probably fair to say that it's not the most intuitive command line in the world, but it is well documented.
diskpart (been around since Windows XP)

So far from being all net new command lines, we have one net new command line tools, and a bunch that have been around for a while (over ten years in some cases).  Guess you'll need to update that MCSE to the new Windows 2008 certification Mike? :)

The great thing about having all this command line stuff available is that it works on both Windows Server Core & Windows Server Full installs, and you can use all this stuff to automate your server builds (or even better, use System Center Configuration Manager to deploy your Windows Server with image based deployment and task sequences).

My question to Mike is this:  once I have my host up and running, what extra steps do I have to do to do things like copy my ISO files on there, or copy my gold images on there? 

With Windows I browse to my file share and copy them on.  It's the Windows you know and love.

What do I have to do to do this on ESX3i?  Usually it's getting a SCP tool and copying files on there, then when I want to provision it means logging on to the console (command line) and copying my images around.  It's the *nix you might not know or love.

Either that or I deploy System Center Virtual Machine Manager and use that to manage my Hyper-V & VMware environments, and use that to do all my provisioning.