You could slipstream them, if you want. This is a line from my script that installs it into a mounted VHDX: Add-WindowsPackage -PackagePath $IntegrationServicesCabPath -Path ($DriveLetter ":")

Eric,
How do you pre-install the integration services. I just tried on Win7x64 and it told me I could not install them until the machine was VM’d. Are you suggesting to slipstream them into the VHD after it has been created with Disk2VHD?

I was able to bring over a great number of Windows Server 2003 hosts that were using SCSI and RAID successfully, although not without pain. If you can take a good backup first, I would pre-install the integration services and see if a straight Disk2VHD works.
If it breaks on you, this procedure might work: https://etechgoodness.wordpress.com/2011/03/10/problems-with-p-v-of-oem-windows-server-2003/.

Just one issue I have I believe:

I am trying to virtualise some of my older legacy workstations. I keep these in order to remain familiar with different operating systems, versions of Office etc. so that I can best support my clients.

The two oldest of these a running Adaptec SCSI and Windows XP.

From what I gather, this requires Hyper-V generation 2 for SCSI to be possible but that does not support Windows XP vms which require generation 1.

Is there anything I can do to get around this?

Thanks

David

I’m not entirely certain what’s going on here. I would start by loading Integration Services in the original system before running Disk2VHD. After that, it’s probably going to come down to editing the boot.ini file on the small partition.

I have a Windows Server 2003 sp2 server that is mirrored. When I run disk2vhd, the program creates 2 vhd files:

data-0.vhd
data-1.vhd

The first one (data-0.vhd) is only 6MB
The second one (data-1.vhd) is 19GB

I don’t know why 2 files are created. The second vhd file (data-1.vhd) matches the size of the data on the disk, but the first vhd file is a mystery.

When I move these files into a Hyper-v environment (running on Windows Server 2008 r2) and create a virtual machine using them I get the following error message when I start up the VM:

A disk read error occurred
Press Ctrl Alt Del to restart

The error message occurs no matter which of the files (data-0.vhd or data-1.vhd) I use as the boot vhd.

Any help is appreciated.

Thank you!

James

It is somewhat common for it to choke on translating the old storage drivers and configuration into the new system. I don’t know of any great ways to fix this. I usually start with the typical system repair techniques I’d use if a physical system did it.

Works great with all Windows but running into problem with 2012 R2..

When I bring over the VHD files and start up the machine, all I get is the blinking underscore..

Server is a physical server running on Intel 6 core with 16 gb ram and mirrored 146 gb hd..

Windows 2008 r2 works fine on same machine.

I thought maybe Win 2008 r2 hyper v doesn’t support Windows 2012 r2 so change that and installed Win 12 r2 with Hyper v and tried to bring over the Win 12 r2 vhd file.. Doesn’t work.

Then tried VHDX. That didn’t work
Tried creating VHD and VHDX disk with and w/o volume shadow copy. That didn’t work either.

Any suggestions? Thanks.

Not without access to a Win2k ISO, no, I’m not sure where else you’d get it.
Before doing the Disk2VHD again, try running system file checker to see if it corrects that problem.