MDT - drivers - duplicates - which gets used?

[James]

Hello,

MDT 2008 Update 1

when importing drivers into the workbench (out of box drivers) and selecting
to allow duplicates, and duplicates do occur, which one is used?

for example I see drivers with '_(1)' appended to name because the driver
filename and version ect are the same, but one is for 2k3 and one is for
2k8? is MDT supposed to select the right one in that scenario?

what about between platforms (x86/x64)?

I'm having issues in that I need to support both 32bit and 64bit versions of
server 2003 and server 2008... especially with HP hpcisss2.sys driver which
if for several smart array raid cards. Also, to make things worse, my images
can not have any service packs in them so when using latest drivers I run
into issues on non service packed machines... service packs are installed
but its done post image deployment as part of task sequence.

I've got a great system worked as far as automation and expanding features
of MDT but now that I'm using on various hardware the driver issue is
causing me great pain.

[unknown]

In MDT 2008 Update 1 you can tag the driver with correct platform
(assuming you do import them as duplicates)...

I do prefer to manually deal with storage drivers in sysprep.inf...
works every time...

Regards

Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deployvista.com

Post by James
Hello,
MDT 2008 Update 1
when importing drivers into the workbench (out of box drivers) and selecting
to allow duplicates, and duplicates do occur, which one is used?
for example I see drivers with '_(1)' appended to name because the driver
filename and version ect are the same, but one is for 2k3 and one is for
2k8? is MDT supposed to select the right one in that scenario?
what about between platforms (x86/x64)?
I'm having issues in that I need to support both 32bit and 64bit versions of
server 2003 and server 2008... especially with HP hpcisss2.sys driver which
if for several smart array raid cards. Also, to make things worse, my images
can not have any service packs in them so when using latest drivers I run
into issues on non service packed machines... service packs are installed
but its done post image deployment as part of task sequence.
I've got a great system worked as far as automation and expanding features
of MDT but now that I'm using on various hardware the driver issue is
causing me great pain.