P2V Conversion of an SBS 2003 Server–Part Three

Part Three – First Run Tweaking the Server VM

This is Part Three of a Five part series about my experience doing a P2V conversion of my SBS 2003 server to Hyper-V. 

Here are links to the other parts:

 Part One – Creating the VHD

 Part Two – Creating the VM

 Part Four – Second Run Tweaking the Server VM

 Part Five – Last Tweaks and We’re Running

First Run – Starting the New VM

Click the Start button to start the VM.


The Virtual Machine powers on.


Windows Starts to Load


The GUI Starts…


“Preparing network connections”. This takes quite a while since there aren’t any functioning network adapters present at this time.


At least one service or driver failed during startup. Not at all unexpected considering the machine just moved to all new virtual hardware and windows hasn’t detected all the new virtual hardware yet. Click the OK button to clear the warning.


Now the Virtual Machine is booted up and ready to login.


First Login

Press the ctrl-alt-del button or press ctrl-alt-end on the keyboard. Enter the administrator password.


We see the shutdown event tracker. This is expected since the VHD was captured when the machine was running. Enter a comment and click the OK button.


The first thing that comes up is a Windows Product Activation warning. “Since Windows was first activated on this computer, the hardware on the computer has changed significantly.” This is also expected. Click the No button. We need to make a number of changes before we will be able to activate the machine online.


Once the desktop loads, one of the first things that will come up is the new hardware found wizard. Click the Cancel Button. Then, go into “add remove programs” from the Windows control panel.


Any drivers or programs that were specific to the physical hardware the server used to run on need to be removed.


If any of the Hardware drivers or programs requests a restart, click “No”. Continue until we have removed everything that was related to the components of the physical server motherboard and add-on cards.


When the physical hardware drivers have been removed, we can start to configure the server O/S for the virtual environment. On the Virtual Machine Connection Window, click Action, Insert Integration Services Setup Disk.


The Hyper-V Integration Services will be installed which includes drivers for the virtual hardware that is part of the Hyper-V environment. The O/S will detect the new virtual hardware and install the drivers.


When the integration services have been successfully installed, click on the Yes button to reboot.


Windows will shut down and restart.


In Part Four, I’ll cover the Second Run at tweaking the server O/S to run in Hyper-V.

Explore posts in the same categories: Computers and Internet

Tags: , , ,

Both comments and pings are currently closed.

%d bloggers like this: