Here again your favorite Random Dude.

Today's topic is about something something that can be in occasions a bit challenging. In my previous post showed you how to create tailored KBEs that are needed specially with OEMs like Lenovo that don't provide (please correct me if I am wrong) a generalized WinPE driver pack as Dell does.

Quest KACE Support have this KB article that does help but I wanted to make it a lot more visual.

First we need to get the folder structure so that during the deployment the drivers can be utilized. To do so, we need to get the driver_feed_discovery_tool.vbs. This tool can be found at \\SDA_hostname\drivers_postinstall .

Now we just need to run it from the machine that we want to capture and we would get something like this:

With this information we just need to create the actual folder.

This example is valid for basically all other OEM. I will now list their current sites so you can grab their drivers.

Dell

https://www.dell.com/support/kbdoc/en-us/000124139/dell-command-deploy-driver-packs-for-enterprise-client-os-deployment

HP 

https://hpia.hpcloud.hp.com/downloads/driverpackcatalog/HP_Driverpack_Matrix_x64.html

Lenovo

https://support.lenovo.com/us/en/solutions/ht074984-microsoft-system-center-configuration-manager-sccm-and-microsoft-deployment-toolkit-mdt-package-index

Microsoft

https://support.microsoft.com/en-us/help/4023482/surface-download-drivers-and-firmware

(how to extract the Microsoft drivers MSIs: msiexec /a c:\SurfacePro_Win10_15063_1704007_0.msi /qb targetdir=c:\surface )

Samsung (trusted provider)

https://drive.google.com/drive/folders/0B_636cnOwn0jelIwcTFSdXBYaVE

You can also use the driver feed builder, can be found here (I don't recommend it as it have provided me mixed results). Just one tip, copy the actual .exe to the actual machine and if you select to save the drivers locally (best way to do it) they will be saved in the desktop.

Let me know in the comments if you have questions!