Roughly two months ago I transitioned to building and testing my deployments via Window 8's Hyper-V client. Everything worked great the clients booted to PXE, downloaded my litetouch wim just fine. Networking worked A-OK. I spent a month booting hyper-v clients testing software installs, capturing images etc.
However last week I updated my deployment share to include some new drivers for a laptop in our inventory, this wasn't the first time I've updated my share since switching to Hyper-v, but this time it seemed to break the hyper-v clients from finding the right NIC driver. The client boots, hits dhcp, passes off to PXE, downloads the WIM, process the rules and then errors out stating:
A connection to the deployment share (\\SERVER-NAME\DeploymentShare$) could not be made. The following networking device did not have a driver installed. PCI\VEN_1011&DEV_0009&SUBSYS_21140A00&REV_20
Fine, simple enough a driver is missing. I do a quick google for the hardware ID and don't turn up much. So here is the steps I've taken:
- Completely regenerated boot images.
- Extracted drivers from hyper-v integration services. Imported into MDT rebuilding boot images, of course importing the new boot images to WDS.
- Added drivers for my local machines NIC.
- Booted a working Hyper-v client found the NIC with matching hardware ID, manually extracted .sys and .inf file and imported them into MDT.
- Used dism.exe to import and commit drivers to litetouch wim.
- Uninstalled WAIK, nuked everything in .\DeploymentShare\Boot, reinstalled waik and regenerated boot images.
- Built a selection profile that excluded the drivers I added just prior to this issue and regenerated boot images.
- Verified with coworker also running windows 8 hyper-v client that he gets the same error when he tries to reach mdt from his clients. We're on completely different hardware.
- Rebuilt my network switch in Hyper-V, Added new machines in hyper-v.
- Googled a whole lot.
- Some mild cursing.
Anybody have any bright ideas? Any ideas on where I can check in logs to see if the driver is actually being installed? I am sort of at a loss. I feel like this is probably something simple but just skimming over it. I appreciate any help you guys could offer.