Migrating Virtual Server 2005 R2 VM’s to Hyper-V…

Due to the fact, that I do work as an IT Pro, finally I got a chance to implement my first Hyper-V Servers on our IBM BladeCenter servers.  Please, take this documentation as is, but I have narrow down the steps to move all my Virtual Servers 2005 virtual machines into my new Hyper-V Server without much problems.  Its natural that there’s always a learning curve but at the end its a straight process.

Virtual Server environment:

Currently, we have an IBM BladeCenter with 4 blade server connecting an IBM TotalStorage DS4700 SAN drive with 2TB total space. Two of the blades servers has Windows Server 2003 Enterprise 32bit Editions and the other has Windows Servers 2008 Enterprise 64bit Editions. On the Windows Server 2003 I have Virtual Server 2005 R2 and on the Windows Server 2008 I’m using Hyper-V RTM.

VM’s migration to Hyper-V

Things I found during my Virtual Server 2005 vm’s migration to Hyper-V:

Before you move your VS2005R2 VM, and to be done the last time you are on VS2005R, make sure to:

1. On your Local Admin account:

a. No screen savers to pop out.

b. Remove any Server Manager screen to pop out.

c. Remove “Virtual Machine Additions”

2. Then, do a shutdown (do not restart).

3. Ready to move your VM files.

There’s no need for other migration tools because you are going to end up doing more manual changes before your VM becomes fully operational under Hyper-V RTM.

Hyper-V Server Setup

Before you turned on you VM, make sure the following Hyper-V settings are in place:

1. Under “Server”

a. Provide a location for all your “Virtual Hard Disks”. All you VM’s Disk will be stored here:

    example “E:\HyperV_Server1\VirtualDISKs”

b. Provide a general folder where you’re going to store VM individually: example “E:\HyperV_Server1\”. Your VM config files will be stored on separately on each servername folder. This folder name will be create when you create a new virtual machine and attached your Virtual Disk to it. This way you will have the following folder structure: “E:\HyperV_Server1\NewServerName” for the VM you just created.

Hyper-V Virtual Machine Setup

To be done before you start the VM under Hyper-V:

1. Copy your VS2005r2 VM to your Hyper-V “Virtual Hard Disks” folder.

2. Run the “New Virtual Machine Wizard”:

a. Choose a name for your server

b. Assign memory

c. Configure Network – leave it “Not Connected”

d. Connect Virtual Hard Disk – here’s you attached you copied VHD’s

e. Completing new VM Wizard – make sure don’t check to “start VM” when finished.

Completing your Virtual Machine Settings

Here’s where you can adjust other devices settings before you start your virtual machine. Now, because your VHD’s comes from a Virtual Server, there’s one thing we need to set before we can continue:

1. Right click on your VM, select “Settings”:

a. Then, under “Hardware”:

       i. Add Hardware, Select “Legacy Network Adapter”

Please, notice that you are only adding a hardware and it will not connect to the network unless you enable it. At this time, don’t connect to the “Legacy Network Adapter” yet. This way we are going to see the adapter that was currently using on the other Virtual Server application. Following these steps you should be able to get to your old network adapter so you can decide to:

1. Keep the old network card with its IP addresses configurations, or

2. Give you the ability to remove the old adapter and use the Hyper-V Virtual Network Adapter

It’s your choice but failure to do this step will cause you not to see the adapter that your VM was using prior to Hyper-V. The old network adapter will be hidden from your hardware components and it will remain active when you start the server.

Starting your Hyper-V Virtual Machine

Here’s where you are going to spend more minutes (not hours) to finally make your VS2005 VM to work on your Hyper-V Server. As soon as the server becomes operational and previous steps has been completed. You are ready to install the Hyper-V “Integration Services” component. To Start your new Hyper-V virtual machine:

1. Right-Click on your VM, and select “Connect” or just Double-Click on the name.

2. Login using your Local Administrator ID (remember, server remains not connected to the network).

The following steps involves installing “Integration Services” but only using the keyboard. And, you might restart the server at least two times.

1. After your login, you need to cancel the “New Hardware Wizard”.

2. go to your “Virtual Machine Connection” pull-down menu:

a. Click on Action

b. Select “Insert Integration Services Setup Disk”

c. Wait for the prompt to start the installation

d. Then, reboots at the end.

3. When After, the server starts again you should have completed your initial migration. Now, you go back to check on your Legacy adapter before you go back to your server settings option and change it to connect.

This process took me less than 15min when I finally got my migration steps in place.

TIP: Did you know?

1. You can start your Virtual Machine without connecting your adapter, make changes to the server and then, while the server is running, change it back to “Connect”. This way you don’t have to restart the server until you are ready to connect back to the network.

2. Using the “Legacy Network Adapter” get you 100mb vs “Virtual Network Adapter” 10mb connection speed.

3. Increase you physical drive partition because you will need up to *32GB per virtual machine running on Hyper-V. This additional space doesn’t exist in Virtual Server 2005.

4. You don’t need the virtual machine configuration (*.vmc) file. You only need to move your VHD’s files to their new location.

5. These steps also apply to Virtual PC 2007 files.

6. If you feel you are getting stuck during the “Integration Services” installation. Just click on the “Ctrl-Alt-Delete” button in you Hyper-V VM Console. Then, use the keyboard “tab key” to select “Shutdown”. Then, you can continue with the installation.

7. Be ready to re-register/activate your Windows Server again.

*Note: This may vary depending on how you built your virtual machine. I’ve seen between 16GB up to 32GB.

Advertisements

About maxt2posh

I’m from Puerto Rico, have been working with computers since 1979. Throughout many years, I have worked with SQL Server Technologies, provided support to Windows Servers/Client machines, Microsoft Virtualization Technologies, and build some Visual Studio solutions. I’m a Microsoft PowerShell MVP since 2009 and MVP SAPIEN Technologies since 2010. I speak in most of the SQLSaturday, IT Pro and .NET camps events around the Florida’s State. Also founder of the Florida PowerShell User Group which meeting every 3rd Tuesday evening of the month.
This entry was posted in Microsoft Virtualization 2008. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s