Logon on to a virtual Machine and insert integration service setup disk.
If you do not have a virtual machine up and running you can mount %windir%system32vmguest.iso
Extract the drivers by performing an admin install on the msi packages.
msiexec /a d:supportamd64Windows5.x-HyperVIntegrationServices-x64.msi TARGETDIR=C:AIPx64
msiexec /a d:supportx86Windows5.x-HyperVIntegrationServices-x86.msi TARGETDIR=C:AIPx86
rename C:AIPx64Hyper-V Integration Services C:AIPx86 Hyper-V_x64
rename C:AIPx86Hyper-V Integration Services C:AIPx86Hyper-V_x86
Copy Hyper-V_x64 and Hyper-V_x64 to your driver folder and you should end up with the following drivers and folder structure:
Hyper-V drivers directory
Disk Virtual Machine Bus Acceleration Filter Driver
Hyper-V Heartbeat
Microsoft Emulated S3 Device Cap
Microsoft Virtual Machine Bus Input Device Miniport
Microsoft Virtual Machine Bus Network Adapter Net
Microsoft Virtual Machine Bus Video Device
Storage miniport driver SCSI Adapter
Virtual Machine Bus
2 Comments
Dillon Boyer · February 6, 2010 at 11:12 pm
Can you extract the SCSI driver for W2K3? I know you can’t boot from a SCSI disk in a Hyper-V guest, but I have many disks I’d like to keep connected while I do a WHS server reinstall.
Since there is a limit of 4 IDE devices, I’d like to attach some of the disks as SCSI.
I need to build a floppy image with the drivers so I can pass the “F6 test” during the text-mode portion of the WHS install.
Tone · February 12, 2010 at 2:00 am
You can add IDE and SCSI devices to guest but you would need to boot from IDE into OS before SCSI becomes available, so you wont be able to use F6 to add drivers as SCSI will not be available until OS is running.
http://blogs.technet.com/jhoward/archive/2007/10/04/boot-from-scsi-in-virtual-server-vs-boot-from-ide-in-windows-server-virtualization.aspx
Not sure how this would affect WHS as I have never used it.