Comments on: Migrate Microsoft Virtual Server 2005 R2 VM to Windows Server 2008 Hyper-V

By: MrGroove

MrGroove — Tue, 05 Aug 2008 15:44:58 +0000

@Chuck - Great Tip! And, perfect timing! I just wrote 2 articles on this very subject - How-To Connect to and Manage a Hyper-V Server Remotely using Vista or from a Windows 2008 Server

By: Chuck vdL

Chuck vdL — Mon, 04 Aug 2008 21:53:42 +0000

One other tip is this. If you are remoting to your hyper-v server (for example if it’s in a server room) it’s a major PITA to setup a new VM over remote desktop because you won’t have access to the mouse etc untill the integration services are installed on the VM. And doing all the things you might need to do in order to get to that point, solely via the keyboard is just a wee bit tricky.. and even trickier in a remote desktop window where a lot of the shortcuts are different.

The trick to doing this my friends is to realize that the Hyper-V Manager can be run remotely! It will run on any VISTA sp1, or 2008 system. So what you can do is use remote desktop as needed to move files around etc, but then when it comes time to create the new virtual machine, close down remote desktop (or better yet logout of the remote session) and run Hyper-V Manager on your local box, connecting it to the Hyper-V server. You now have exactly the same control you would if using Hyper-V Manager locally on the virtualization server. So, this means that when you intially connect to the new VM, because you are not in a remote desktop session, you WILL have mouse controll and will be able to much easier take care of any configuration changes (like a HAL detection reboot) that are needed before you install the integration services.

By: MrGroove

MrGroove — Mon, 04 Aug 2008 19:35:48 +0000

@Chuck - Thanks for the detailed comment. I’ve not tried to migrate a Server 2008 so I appreciate the testing and FYI.

Thanks, and welcome to the site!

By: Chuck vdL

Chuck vdL — Mon, 04 Aug 2008 18:34:31 +0000

Just a note that when migrating a Server2008 virtual machine from Virtual-PC 7 (on vista) to Hyper-v on 2008 server, (without benefit of these instructions) I ran into some issues where
* the new network card was not seen,
* 2nd processor (allocated to the VM) was not seen
* the Integration bits would go through the motion of installing, but never fully install
* Integration services installation gave a message that it detected a existing installation of the integration services (happens on initial attempt to install them, and subsequent attempts)

I had removed the VM additions, optimized the drive, etc, shut down the system and moved the VHD to the new 2008 Hyper-V server. Fired up a new VM (using pretty much the steps above) and after it did all it’s hardware detection, had tried to install Integration services. But then got stuck with the issues bulletted above.

Doing steps 12-14, and forcing it to re-detect the HAL took care of all of the above after the reboot.

So if you are migrating a 2008 VM, try following the instructions above for Vista and it should work well for you.

By: imran

imran — Tue, 29 Jul 2008 08:39:32 +0000

By: MrGroove

MrGroove — Tue, 29 Jul 2008 04:52:50 +0000

@Noname - Thanks for the comment and yes. My recommendation would be to take a screen shot or write down the NIC settings before you migrate the VM from the original Virtual HOST to the new Hyper-V host. That way you can just delete uninstall and delete the NIC prior to migration.

By: MrGroove

MrGroove — Tue, 29 Jul 2008 04:51:09 +0000

@pc4Life - Never know…. VMWare just answered (today in fact) with their own FREE VMWare Server Hyper-Visor called ESXi - http://www.vmware.com/products/esxi/. Will need to download that.

By: MrGroove

MrGroove — Tue, 29 Jul 2008 04:38:35 +0000

@Efi Lami - Your Welcome! I’m glad it worked out for you!

By: 2K8 - Hyper-V Gast Fragen - MCSEboard.de MCSE Forum

2K8 - Hyper-V Gast Fragen - MCSEboard.de MCSE Forum — Sun, 27 Jul 2008 12:50:32 +0000

[...] eigentlich nur noch an den alten Additions/Treibern/Hal liegen. Schau hier mal den Punkt 14 an: Migrate Microsoft Virtual Server 2005 R2 VM to Windows Server 2008 Hyper-V :: groovyPost.com Gr

By: noname

noname — Fri, 25 Jul 2008 08:01:05 +0000

Dont Forget about NIC cards, since Hyper-V is using different NIC, you will need to delete hidden not present NIC, before moving your IP to new network card!