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

By: MrGroove

MrGroove — Tue, 25 Nov 2008 20:34:07 +0000

Comments Closed for this Tutorial.

Please post all further Questions or Comments in our Free Tech Support Community Forum

Thanks, -MrGroove

By: MrGroove

MrGroove — Wed, 22 Oct 2008 21:51:05 +0000

@Matthijs – Thanks for the FYI. I’ve not had a chance to try your new app. I’ll give it a shot and let ya know how it goes.

@RonC – Actually yes. I have done it before. The first time I migrated a machine from Virtual Server 2005, I booted up the guest system in the Hyper-V environment and had to use the keyboard (mouse doesnt work well nor does RDP until you have the new Hyper-V Guest Apps installed) at the HOST system (Console) to navigate through the guest and uninstall the old VM Additions.

If you need help, please start up a new Topic in our Forum – http://www.groovypost.com/forum/ There you can post screenshots and we won’t make the comments here ALL messy. Registration takes just 2 minutes and it’s a simple forum to navigate.

Thnx,

-MrGroove

By: RonC

RonC — Wed, 22 Oct 2008 21:18:59 +0000

Have you had any luch with uninstalling virtual machine additions from Windows Server 2008? I cannot for the life of me get it to work and therefore cannot migrate to Hyper-V.

Any suggestions?

By: Matthijs

Matthijs — Thu, 18 Sep 2008 05:47:43 +0000

Good description of the migration process. However, the physical properties of the Virtual PC / Virtual Server VM can now easily be imported. See blog post.
http://blogs.technet.com/matthts/archive/2008/09/12/vmc-to-hyper-v-import-tool-available.aspx

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.