WDS/WDT deployment weird driver issue..

[Beavermatic]

If anyone could point me in the right direction on a akward anomaly that seems to be occurring, would greatly appreciate:

So I start with my base image, then I kick off Litetouch VBS, and it captures and syspreps the image, and reboots and creates a WIM perfectly. I've done this numerous times before without issue.

However in this instance, upon deploying the WIM to a identical machine, I get a "ipf63x64.sys corrupt or missing" after imaging completes and windows begins to boot on fresh machine for the first time.

Here's the problem... the base image does not contain "ipf63x64.sys", nor does the mounted wim file from that image under WDT (I checked in 7zip). There are no "Out of Box drivers" either. I checked registry for any entry, and windows\system32\drivers of both original image and the WIM clone of that image. That driver isn't there at all.

It seems that either the WinPE environment (the ADK which is win8.1) or the base OS that I use to create the task to capture the image (Windows 7 Enterprise OEM disc 64bit) is somehow forcing these drivers into image after deploying it, just prior to imaging completion (right around the time it does the last step with the unattend.xml and just prior to reboot from image completion). That's my *guess*.

I noticed that if I use a Linux live USB thumb drive, on the newly image machine that wont boot to windows because of that error, I can boot to that thumb drive, browse to the windows\system 32\drivers folder and magically it added the ifp63x64.sys and ifm60x64.sys files (both of which cause the windows boot halt) that were not in the WIM file nor on the original image I created that WIM from. If I remove both of these files.... boom. Windows starts and finishes first time setup no issue.

Only problem is... I have to deploy this image to 60 Lenovo m93 tiny desktops. I don't want to have to image, then use the Linux live disk to boot to each and remove those two erroneous drivers that are somehow being added in post-wim creation, during the imaging process.

Can anyone recommend why this might be happening, how to stop it from adding these two drivers, or a what to edit to manuall script the removal of these two drivers before imaging completes?


If there's a way to have unattend.xml "remove" these two files from windows\system32\drivers directory, since I would assume they would have to be added just prior to that in the imaging process, that should also work I'd think.
Many thanks and much appreciated for any help that may be provided.

 

[terpsy]

May be something in your baseimage before the litetouch.

go back through add/remove programs, run a disk cleanup and recapture the image

 

[Bubbaleone]

It appears that both of those drivers originate from Intel: IFP63X64.SYS_Intel Ethernet FCoE SAN Stack for Windows* OS Related Intel driver files are linked at the bottom of that page.

.

 

[Mushkins]

How are you deploying these images, exactly?

You should look at the driver packages, properties for each WIM file, etc configured in WDS. There could be special permissions, an unattended install script, or a conflict. WDS can deploy extra drivers via driver packages that are not included in the base image, sounds like you're pushing a driver package to these installs that's not supposed to be there. This feature lets you create one base image and still deploy to dissimilar hardware without slipstreaming a billion drivers into the image, but can lead to issues like what you describe if misconfigured.

 

[Beavermatic]

How are you deploying these images, exactly?

You should look at the driver packages, properties for each WIM file, etc configured in WDS. There could be special permissions, an unattended install script, or a conflict. WDS can deploy extra drivers via driver packages that are not included in the base image, sounds like you're pushing a driver package to these installs that's not supposed to be there. This feature lets you create one base image and still deploy to dissimilar hardware without slipstreaming a billion drivers into the image, but can lead to issues like what you describe if misconfigured.

Pretty sure you just solved it.

Made me realize I had a driver group full of ethernet drivers from various vendors in WDS that I was using for other deployment shares.

What I didn't realize is that WDS injects the driver not only into the winPE, but also into the imaging process entirely when booting and imaging from that PE. I thought it would only install and inject the drivers listed in "out of box drivers" within WDT into the image, not in WDS, as I thought WDS driver packages were WINPE only.

Kudos to you, and many thanks!