BDD 2007, WDS, Vista 32bit, Different Hardware

[JP Briggs]

I just don't get it. I thought with BDD and WDS I could have ONE OS WIM
image, and apply it to vastly different hardwares. Well I've got a test
Vista image pushed to a Latitude D830, Precision M4400 and an Optiplex 755.
I've imported drivers for all of them into BDD. Vista now installs on all 3
of them (with OS packages and application installs) with 0 errors and 0
warnings. Hooray! But not one of them have the correct graphics driver.
They all use the 'standard' VGA adapter, even though I have the nVidia, ATI,
and Intel drivers imported.

And on the M4400, the "Dell 1510 Wireless WLAN mini-N" card is installed
correctly, but I CANNOT enable it. Windows says "Enabling", then "Enabled"
but Network Connections continue to say "Disabled".

I called Dell. They told me to build a reference image from the M4400, and
keep it separate from the others...

But the whole point of BDD was that you don't need to do that anymore! What
am I missing?!?

And what do people do about proprietary apps (like Dell's WLAN manager
software...)

SO FRUSTRATING!

[Dave Guenthner [MSFT]]

MDT should be using PNPENUM tool to generate a list of all plug and and
play ID's in PE phase. Based on that information, MDT attempts to search
the drivers stored in distribution share for matches, then update unattend
as needed. When you go into properties of workbench, check the box for
system class drivers and recompile Litetouch wim. Once trick for OEM
installations which really require a full installation package is leverage
the WMI capability within MDT. For a given task sequence, if Make and
model = Dell 600 then install an application containing the installer
package with silent switches. In the case of WiFI, the adapter may not be
detected in PE, therefore the drivers are not being copied down.

You can obtain all the variables from the beginning of the bdd.log

Dave Guenthner [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.