I am currently investigating on running hyper-v server on my development machine. The main reason is the low footprint. However, as it turns out, it is not possible to ‘connect’ to the VM’s hosted on the hyper-v server from the core box itself, as the terminal services component (aka remote desktop) is missing from the Server Core.

According to Jason Hutt’s post at http://jasonhuitt.com/blog/post/Server-Core-2008-No-Built-In-MSTSC.aspx you can add the TS functionality to a Server Core box by copying the following files from a Windows Server 2008 or Vista SP1 machine

I have not tested this yet, but will update this post as soon as I do.

Whenever you create a new Virtual Machine for an existing (previously configured) VHD (either by copying the VHD or using differencing disks), the networking configuration of the VM is reset.

This is because when creating a new VM, the Network Adapter(s) you assign receive a new Guid and are treated by the OS as new hardware.

The following post explains this behavior in detail:

http://blogs.technet.com/jhoward/archive/2008/07/22/hyper-v-why-is-networking-reset-in-my-vm-when-i-copy-a-vhd.aspx

I recently installed a Windows Server 2008 with Hyper-V to host my Virtual Machines. As overall performance seemed to be better than on Virtual Server 2005, I ran into very poor performance when copying files between the Guest and Host using a file share.

I tried several solutions I’ve found on the net, but in the end, I found that one should NOT use the ‘Legacy Network Adapter’ in Hyper-V but use the ‘Network Adapter’ when adding a network card to the VM.

When copying a 4GB (iso) from the VM to a (shared) USB drive attached to the Server, the speed went from barely 2MB/s to a reasonable 17MB/s.

When you copy a VPC, only copy the VHD images and do no copy and reuse the VMC file. When a VMC is created, VPC generates a MAC address for the virtual ethernet adapter(s), and stores this in the VMC file. If you copy the VMC file, and used networking with your VPC, you will end up with duplicate MAC address within your network.