Let me start by explaining my rather unusual situation. We have a lot of clients that have anywhere between 10 and 20 PC's and servers (ranging from server2012 back to windows XP). As we would like to keep a virtual copy of avery clients installation we placed a small hyper-V cluster running Server 2012 and when visiting clients we capture their systems with disk2vhd and put those on the Hyper-V server.
In order to be able to recreate some hardware specific scenario's for clients we converted these VHD's to WIM files using imagex. After adding them to the WDS server, we can deploy them to physical hardware just fine. However, the problem is that I created a drivergroup containing all drivers of the physical machine for that type of OS. When deploying the installation it successfully installs and reboots the machine, and for Server 2008 and windows 7 it has installed all the drivers. However, for Windows XP the drivers will just not install. Please note that I did not sysprep the VHD files, because I want to recreate the scenario from the customer as much as possible.
When I login to Windows XP, it prompts me for chipset, NIC and video drivers, but they are all present on the WDS server. I also tried adding all the drivers to the boot image, but this was also unsuccesful. Can anyone shed some light on how I can get the client to install the drivers present in the WDS drivergroups during installation?
I am using Server 2012 with WDS and HyperV roles installed.